Flappie

I see. Then I'm not sure what happened to you. Anyway, you have a backup, which is a very good thing. Never delete at first. What you want to do is: Go to "Saved Games/DCS/Config". Rename "Input" into "Input_old". Unzip the content of "Input2.zip" in this Config folder. Run DCS and check your custom keybinds. If all your custom keybinds are present, you can now delete "Input_old". Yes they are, as long as they are connected when DCS starts.

You're welcome. I couldn't find any issue in your Input archive. According to your log file, your devices UUIDs are: [Saitek Pro Flight X-56 Rhino Stick {AC13A570-BEED-11ef-8001-444553540000}] [Saitek Pro Flight X-56 Rhino Throttle {C26F37D0-BEED-11ef-8004-444553540000}] And your .diff.lua filenames match, which means your .diff.lua files should be recognized by DCS, and therefore your custom keybinds should be present in the Controls menu. For the sake of it, I removed some obsolete .diff.lua files I found, but I'm pretty sure it won't change anything for you. DCS looks for your .dff.lua files in "c:/users/huggy/saved games/dcs/config/input", so please make sure this is where your custom keybinds are stored. Input2.zip

Please attach your dcs log file from "Saved Games/DCS/Logs".

Right away, sir.

This is no joke. Then please share your link.

@huggy98 We'll do this manually, then. Please attach: Your "dcs" log from "Saved Games/DCS/Logs" A zip containing your Saved Games/DCS/Config/Input" folder. I'll rename your files then will send you the resulting Input folder.

If they would know the salvo controls also affect rockets, they certainly would have coded it and mentioned it in the Su-25/T manuals. Not to mention they work with publicly available data. If the source you have in mind is not for public disclosure, they won't be able to use it (see rule 1.16).

Ensure your helicopter is facing wind when taking off. To my knowledge, DCS does not simulate wear/damage from dust to the engines (well, not yet ). EDIT:

@huggy98 There is a high chance that Windows has changed the UUID of your peripherals, hence breaking the "link" between your DCS .diff.lua files and your gaming devices. @niru27's software should help with that.

Ensure that you are not running DCS as Administrator, and that your BIOS is up-to-date.

Please ensure you are not running DCS as Administrator.

Do you have a source?

A DCS track would help.

2025-03-30 20:59:02.293 WARNING EDCORE (Main): hypervisor is active Ensure Windows VMP is disabled if you don't need it. https://support.microsoft.com/en-us/windows/options-to-optimize-gaming-performance-in-windows-11-a255f612-2949-4373-a566-ff6f3f474613

Thank you. My GPU is not able to do DLAA. I've just asked my fellow testers to try and reproduce the artifact. EDIT: none has reproduced the issue so far.

Please provide a track. Eejection time.trk

I've just bumped the internal report.

There's an issue with the third livery, called "IRIAF F-5E Standard". Reported.

@swartbyron 41rd (sic) TFS and 43rd TFS liveries seem to have been fixed with March 19th update. Can you please confirm it's all good for you?

Issue reported. Thanks for the heads up.

Nice catch. Both static and "uncontrolled" F-5E-3 are affected. Issue reported.

I bet that you installed the Rafale mod in the core game folder. You should not. Mods should go into your "Saved Games/DCS" folder. Your next steps are: DCS cleanup then DCS repair Install the Rafale mod in your "Saved Games/DCS" folder.

Analogy: A lot of people complain about unexplainable car crashes. A thread is created. The issue is reported internally with a link to this thread and fresh user logs. Car makers scratch their head, then they find an explanation: there is no pressure in the brake system. They issue a fix, and the fix works for the guys who test it. Car makers publish the fix and the fix works for most people who were complaining about the car crashes. Now, a few people still complain about car crashes even though they received the fix. Since their problem was not solved with the fix, it certainly has a different root cause. A new thread is opened, the issue is reported internally with a link to the new thread and user logs.

Hey @hannibal, could you please check? I'm not sure how to check this.