Tshark Posted September 23, 2025 Posted September 23, 2025 My throttle settings will not save from one DCS session to the next with the MiG-29. I tune the axis by checking the "slider" box and adjust a saturation to 84 to match the AB to my detents. For the rest of the flying session the settings are saved. When I shut down DCS and restart it the only the throttle "slider" and saturation settings are lost. This is the only module that does this. Any suggestions or is this a bug? 9800X3D (5.21GHz Turbo), RTX 5090 OC 24GB, ASUS ROG Strix X870E-E GAMING Motherboard, G. Skill Trident Z5 DDR5 RAM 96GB (2x48GB), Crucial P3 Plus 4TB PCIe Gen4 3D NAND NVMe M.2 SSD, Virpil Alpha Joystick with FFBeast FFB base, T-50CM3 Throttle, MFG Xwind rudder pedals, Pimax Crystal Super VR.
falconzx Posted September 25, 2025 Posted September 25, 2025 same bug for me. I set up user curves to align physical detents to the military power value when i restart dcs, all is back to default.
Sano Posted September 25, 2025 Posted September 25, 2025 (edited) Same here. Initially had left and right engine axes mapped to a split throttle, but the custom curves kept on resetting the next day. After switching to the single thrust axis (and clearing the other two), the settings on that axis persist after restarts Edited September 25, 2025 by Sano
Volator Posted September 25, 2025 Posted September 25, 2025 (edited) Same. Quite annoying bug. Edited September 25, 2025 by Volator 1./JG71 "Richthofen" - Seven Eleven
Volator Posted September 26, 2025 Posted September 26, 2025 I just found out that the F-5E (FF) is also affected by this... I configured my Virpil dual throttles as sliders in-game and added a -10 curve to make the physical detent match the in-game AB detend, but whenever I restart DCS, these settings are gone. 1./JG71 "Richthofen" - Seven Eleven
Tshark Posted September 26, 2025 Author Posted September 26, 2025 (edited) I got the throttle settings to save for me. My past attempts were made while in VR. Immediately after the latest patch, I started up DCS in 2D and made the changes. Since then they have not changed. Don't know if this was just a unicorn or a way around the bug, but thought I would share. Edited September 26, 2025 by Tshark 1 9800X3D (5.21GHz Turbo), RTX 5090 OC 24GB, ASUS ROG Strix X870E-E GAMING Motherboard, G. Skill Trident Z5 DDR5 RAM 96GB (2x48GB), Crucial P3 Plus 4TB PCIe Gen4 3D NAND NVMe M.2 SSD, Virpil Alpha Joystick with FFBeast FFB base, T-50CM3 Throttle, MFG Xwind rudder pedals, Pimax Crystal Super VR.
Volator Posted September 27, 2025 Posted September 27, 2025 I am also a non-VR User, and yet it doesn't save. 1./JG71 "Richthofen" - Seven Eleven
ED Team BIGNEWY Posted September 29, 2025 ED Team Posted September 29, 2025 Hi all, sorry but we have not been able to reproduce this issue, can you retry and attach your dcs logs from the session thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Renko Posted September 30, 2025 Posted September 30, 2025 On 9/23/2025 at 2:56 PM, Tshark said: My throttle settings will not save from one DCS session to the next with the MiG-29. I tune the axis by checking the "slider" box and adjust a saturation to 84 to match the AB to my detents. For the rest of the flying session the settings are saved. When I shut down DCS and restart it the only the throttle "slider" and saturation settings are lost. This is the only module that does this. Any suggestions or is this a bug? I see you too have the Virpil T-50CM3 Throttle I think there are some unresolved issues with that hardware in DCS. In the Changelog from https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.20.15010/ There is a fix for the same hardware on the F16 : "Fixed: Duplicating Thrust axes on the VPC Throttle MT-50CM3 joystick." And I had reported an issue with it in the Apache forum last May with the T-50CM3 Throttle, but got no answer from ED. Curious that my issue is that the controls are reverting to default when i shutdown and restart DCS, in certain conditions.
Volator Posted October 1, 2025 Posted October 1, 2025 (edited) @BIGNEWY Here are some further test results: These are the settings that I set for my throttle axis for the Virpil CM3 throttle: After setting these values in an instant action mission, I did the same with the F-5E in an instant action and set these values to hit the physical AB detent. See how these values are basically inverted to those I set for the MiG-29: Next, I check the MiG-29 settings again in another instant action mission - and they have been overwritten to the values that I just had set for the F-5E?! Then, after restarting the game, I see these settings for the MiG-29... ... and for the F-5E - they are all gone again. Here's my log file as requested: I also see several .crash files in the logs folder, even though I quit DCS the correct way, there was no crash. Not sure if that means anything? dcs.log Edited October 1, 2025 by Volator 1 1./JG71 "Richthofen" - Seven Eleven
ED Team BIGNEWY Posted October 1, 2025 ED Team Posted October 1, 2025 thank you, we will try to reproduce 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Sano Posted October 4, 2025 Posted October 4, 2025 On my end, seems there is a difference between setting controls "in a mission" vs "in the main menu". In the main menu, my controls were saved/persisted correctly after a game restart - while it did not when i adjusted controls in a mission. Can anyone confirm if this makes a difference for them? 1
Volator Posted October 16, 2025 Posted October 16, 2025 On 10/4/2025 at 5:40 PM, Sano said: On my end, seems there is a difference between setting controls "in a mission" vs "in the main menu". In the main menu, my controls were saved/persisted correctly after a game restart - while it did not when i adjusted controls in a mission. Can anyone confirm if this makes a difference for them? I would have to check, but what I just tried in the main menu was configuring both F-5E (FF) and MiG-29 throttles directly one after the other, and the throttle settings of the former always overwrote the throttle settings of the latter. There is a direct connection between those two throttle settings 1./JG71 "Richthofen" - Seven Eleven
AngryButler Posted January 27 Posted January 27 Has there been any resolution to this issue? I too am experiencing my throttle settings being overwritten each time I restart DCS (regardless if the settings were saved while in mission or from the main screen). I am using the CM3 throttle as well.
Raven (Elysian Angel) Posted January 27 Posted January 27 I also have a CM3 throttle, and these are my settings for both L and R thrust: I chose not to mess with saturation, and the small curvature makes sure the reheat detent is where it is supposed to be (the deadzone of 3 is to take care of the physical idle detent). You peeps might try if this works for you. They are saved correctly for me, and I never had this issue... Spoiler Ryzen 7 9800X3D | 96GB G.Skill Ripjaws M5 Neo DDR5-6000 | Asus ProArt RTX 4080 Super | ASUS ROG Strix X870E-E GAMING | Samsung 990Pro 2TB + 990Pro 4TB NMVe | VR: Varjo Aero VPC MT-50CM2 grip on VPForce Rhino with Z-extension | VPC CM3 throttle | VPC CP2 + 3 | FSSB R3L | VPC Rotor TCS Plus base with SharKa-50 grip | Everything mounted on Monstertech MFC-1 | VPC R1-Falcon pedals with damper | Pro Flight Trainer Puma OpenXR | PD 1.0 | 100% render resolution | DCS graphics settings Win11 Pro 25H2 - VBS/HAGS/Game Mode ON ***DISCLAIMER: I'm just an armchair enthusiast. My posts may or may not reflect real life experience.***
Tango3B Posted February 4 Posted February 4 (edited) Just a heads up, if you`re using a CM3 throttle (like I do) then make sure you update your drivers and your firmware to the newest version. Having done that, this problem does not exist anymore. I had it, too...could trace it to having neglected to update my drivers/software for quite a bit. There you go...problem solved. Edited February 4 by Tango3B
Recommended Posts