Dos

Hello couldn't you use binding porfiles in DCS instead?

Hello Mike you got me thinking I do spend a bit of time launching all these programs individually in support of DCS a batch file would is not be a bad idea. That said on Monday I got on it and found that it would be better to use powershell. Since Multiple Com Port is a cmd file its script is different then normal .exe files maybe why you are having issues. Let me add if one of those .exe files need higher authority then that script will be slightly different from the .exe files also. In power shell this is what my launch-multiple-com-ports.ps1 file looked like. I made it into an icon that when clicked it launch the program and I intergrated it into streamdeck as a push button: # Path to your CMD file $cmdPath = "C:\Users\jpav2\Saved games\DCS\Scripts\Programs\multiple-com-ports.cmd" # Working directory for the CMD file $workingDir = Split-Path -Path $cmdPath # Launch in classic Command Prompt, keep window open Start-Process -FilePath "cmd.exe" ` -ArgumentList "/k `"$cmdPath`"" ` -WorkingDirectory $workingDir If the cmd program hangs instead of searching {alt\tab} for that window then mouse to click close and then look for and relaunch program and finally back to the game. I created another script to close the crashed cmd window which allows me to relaunch it again. Both are desktop icon and on stream so now the process is press a button, thats it. To close here is the powershell script - close-multiple-com-ports.ps1: Get-Process -Name OpenConsole -ErrorAction SilentlyContinue | ForEach-Object { try { $_.Kill() } catch { Write-Host "Failed to kill OpenConsole process: $_" } } Notice I had to use OpenConsole to close the Multiple Com Port window. Powershell had issue closing the crashed cmd window initially and my understanding is it is looking to close the cmd window. I guess when it crashes it is no longer functioning as a cmd file so the work around was close any OpenConsole which is what it becomes after it crashes. Control Alt delete task manager reveals that. I created the close one because I get a bit of socat crashes on that Multiple Com Port program because Elgato streamdeck and BIOS stuff, for example Tex Creation IFEI do not play nice together, at least I can not figure it out on my pit : ) Hit me up if you need help Cheers J

I recently revisited my setting since I could not AAR. Althought I did ask Chatgpt and for my winwing Super Libre on a F-18 which is how I noticed the viper needs a negative curve. I had a higher curve setting prior to asking chat and it really did not work well for me with AAR, but I lowered it to 6 from 20 and now connect everytime I try. IMO you should follow rob10 advice, leave as is unless the viper is your module and it is a must to go negative on curve - idk. Oh yeah I read if that stick has FFB then you do not use these setting. Cheers Below I asked chat for your flight stick setting enjoy: What would be the best axis tuning setting in DCS for my winwing viperace? ChatGPT said: For your WinWing Viperace HOTAS in DCS, achieving optimal axis tuning is essential for precise control, especially when flying aircraft like the F-16 Viper. Given the force-sensing nature of the Viperace, specific adjustments can enhance your flying experience.reddit.com+4reddit.com+4reddit.com+4reddit.com Recommended Axis Tuning Settings for the F-16 Viper 1. Deadzone: Pitch & Roll Axes: Set the deadzone to 0%. This eliminates any unintended input near the center, providing a more responsive feel. However, some users have found that setting a minimal deadzone (e.g., 1%) can help with autopilot functionality. reddit.com+2reddit.com+2reddit.com+2reddit.comreddit.com 2. Curvature: Pitch & Roll Axes: Apply a negative curve between -4 to -15. This adjustment compensates for the Viper's hardcoded force-sensing curve, offering smoother and more precise control, particularly in the center zone. reddit.com+4reddit.com+4reddit.com+4 3. Saturation X & Y: Pitch & Roll Axes: Set the saturation X & Y to 100%. This ensures the full range of your stick movement is utilized, maintaining consistent control throughout the stick's travel.reddit.comforum.dcs.world+3reddit.com+3reddit.com+3 4. Throttle Axis Configuration: Throttle: Configure the throttle as a slider in DCS. Set the "axis begin" value to match the physical idle position of your throttle. For instance, if your throttle reaches idle at 22%, set the axis begin to 22%. This setup ensures that the throttle behaves linearly and accurately reflects your physical movements. reddit.com+1reddit.com+1 Additional Tips Force-Sensing Stick Settings: DCS now allows users to disable the Viper's built-in force-sensing and deadzone features. It's recommended to turn off these settings in the Special Options menu to prevent conflicts with your hardware's capabilities. reddit.com+1reddit.com+1reddit.com Testing and Adjustment: After applying these settings, spend time in a test mission to fine-tune your controls. Adjust the curvature and deadzone as needed to match your flying style and preferences.reddit.com+1reddit.com+1 By implementing these settings, you should experience improved control and responsiveness in the F-16 Viper within DCS. Remember, personal preference plays a significant role, so feel free to adjust these values to suit your comfort and flying style.reddit.com+1reddit.com+1 *And you could ask specifics: In DCS, Saturation X and Saturation Y serve different purposes: Saturation X: Controls the input range (from your physical device) that gets mapped to the in-game axis range. Saturation Y: Controls the output range (how much of the input is sent to the game). Recommended Setting for Saturation X with WinWing Viperace: Set Saturation X to 100% Why 100% for Saturation X? Since the WinWing Viperace is a force-sensing stick with no traditional movement range, limiting the X input range (i.e., anything under 100%) would artificially shorten the usable input area. That can: Reduce fidelity Create unexpected nonlinear behavior Lead to early "peaking" in control response By keeping it at 100%, you're telling DCS to read the full range of input from the stick exactly as it is — which is important for maintaining the precision intended by the Viperace. Summary for Pitch & Roll Axis: Setting Value Deadzone 0–1 Saturation X 100% Saturation Y 100% Curvature -5 to -15 (test to taste) Let me know if you’re flying anything besides the F-16 and want axis tuning suggestions tailored for that!

Nice

Make sense - TY

I am no expert on the art of lua but I did notice the ifei does change from white to green when switched from day to anything else - perhaps looking at that lua may help??? Thanks considering it.

@CapnCoke Hello and thank you for all the work that has been put into this MOD. I was doing a night mission and switched the mode switch from "Day" to "Nite" and wanted to ask if their is a lua line that would tell the DDI's to go from white line displayed currently back to the green ones (vanilla)? All the other colors are great in Day, Nite, and NVG. Basically white lines only in "Day" mode. I am guessing the DDI's do not have a different display profile for each of the three position Day-NVG-Nite. Kindly, J

and the base of the center stick!

LOL. Details matter.

LOL fair enough, I meant AF.

A Colonel flying the Hornet kills the realism! They had a MOD that worked perfectly but that got broken in an update. IMHO being able to select branch of service as pilot should have been built into the game years ago. A Colonel flying a Hornet - come on.

Balloon maybe?

Gears break too easy.

Hello did you ever figure this out?