sleighzy

Btw, the _downloads folder is just the temporary folder used to download the update. So you could have just deleted that first, if it was corrupted then copying it directly may not have solved it.

Here's the actual file, drop it in that location. This approach definitely works. So either it's in the wrong location, or your text editor named the file autoexec.cfg.txt and your Windows is hiding file extensions and you're only seeing the .cfg part, or you're overriding it somewhere else. Your screenshots show you overriding stuff so may be conflicting Try the file first. autoexec.cfg

Yes. Or just copy across your existing stuff and run a slow repair. In either case, if moving to a different drive then update your shortcuts to point to the new location.

You’re also running the DCS.exe file in the bin-mt folder. Both bin and bin-mt are multithreaded and the bin-mt folder will be removed in the future so just use the one in the bin folder.

Check your DCS log file. Look for the text about DLSS preset and K (if it says C then it isn’t using that file). If it says K even without that file then it means you’re overriding it somewhere else.

Please attach your DCS log file for review, this may be a separate issue in which case you can raise your own post.

I see this error in that log. 2025-09-17 17:27:53.596 ALERT LUACOMMON (Main): Error: GUI Error: [string "./MissionEditor/modules/me_news.lua"]:146: bad argument #2 to 'date' (number expected, got string) GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'date' [string "./MissionEditor/modules/me_news.lua"]:146: in function 'showNews' [string "./MissionEditor/modules/me_news.lua"]:259: in function 'funCallBack' [string "./MissionEditor/modules/me_waitDsbweb.lua"]:90: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> Try running a slow repair of the game. Additionally if this continues then try renaming your Saved Games\DCS.openbeta folder to DCS.old as per the suggestion in the previous comment in case of corruption in anything in the MissionEditor folder related there.

Just retested after updating. Can no longer replicate so this appears to be fixed now.

Just retested after updating. Can no longer replicate so this appears to be fixed now.

You mean the ones in this post, or from another one? The ones in this post are out of date. To use the native support in DCS do the following: Add the below line to your C:\Users\username\Saved Games\DCS\Config\autoexec.cfg file to set the DLSS preset, this is still C by default. You will need to create this file if it does not already exist. The second line there is optional but will mean that DLSS is not applied to MFDs or the HUD which can reduce ghosting on there, i.e. moving cursors on radar screens, etc. Nvidia App overrides will likely override that setting, so remove it, unless you have other games you want to apply it to. DLSS_Preset = 'K' HUD_MFD_after_DLSS = true

Can you please attach your DCS log file.

Latest update from the ED folk on the bug report in their Discord was that they were able to replicate, and now appear to have fixed as can no longer replicate in their testing version. Based on this feedback it looks like we might get this fix in the upcoming patch (hopefully this week).

Latest update from the ED folk on the bug report in their Discord was that they were able to replicate, and now appear to have fixed as can no longer replicate in their testing version. Based on this feedback it looks like we might get this fix in the upcoming patch (hopefully this week).

Not sure what your use case was but DCS has native support for this now so instructions re: Nvidia Profile Inspector, Nvidia app, etc. are no longer needed if you're just wanting to use in DCS.

Sweet. Little confused about your original question then, not sure what "some" of it means then. Turbo mode in general, whilst works for some people, effects the frametime pacing with the runtime so can cause issues. > You can also use Quad Views (Quad-Views-Foveated) which enables turbo mode by default. Correction on my part, SteamVR is the only runtime this isn't enabled by default, but can be turned on.

Why won't the OpenXR toolkit work? You can also use Quad Views (Quad-Views-Foveated) which enables turbo mode by default. Note, you can unselect "Quad Views" in the DCS settings with QVF installed (if you don't want to use quad views, although depending on your specs quad views may give you a performance bump) and turbo mode will still be applied.

DCS now has native support for setting the preset. You can also look in your DCS log file as it will output the preset being used.

One thing I notice in that log is that you're still on Windows 10. I'd recommend upgrading to Windows 11 as it'll better support your hybrid P/E cores. Then use software like ParkControl to disable core parking. This may help with microstutters. DCS should be allocating I/O to the E-cores, and I/O can be the cause of blocking and stutters, which can be noticed if it's not correctly allocated as otherwise that is being done using your performance cores.

DCS should not be run as administrator. It's possible you've run as administrator before which has meant the file permissions were messed up and the file couldn't be written to, so running as administrator again means it was able to write to the file.

The OP of this issue isn’t using VR so this isn’t really relevant. IMHO (while things are good for you) I wouldn’t recommend that.

I’ve touched base with StoneSky and they’ve confirmed it’s the same rockets loadout in their campaign

Thanks for the feedback mate, much appreciate the confirmation. I’ve pinged Bignewy for the dev team and will be attaching a track file for my instant mission replication to the ED bug report as requested.

@STONE SKY Issue with crash to desktop on switching George to rockets has also been reported on the ED DCS Discord server. I am able to reproduce as well. Issue is with switching to the rockets which are the M151 ones with the M433 Resistance Capacitance (RC) Fuze. This does not occur for other rockets. I don't have your campaign so cannot confirm what the rocket loadout is for your 1st mission in this campaign. May help you though with identifying this issue on your end if this is the case. If you have a different rocket loadout than that then let me know and I'll see if I can replicate that and add to the bug report.

@mla306 Yeah I can reproduce this as well, first time. @BIGNEWY can you report this to the devs please. Easy to reproduce. I just loaded the M151 rockets ones with the M433 Resistance Capacitance (RC) Fuze in the Instant Mission for Firing Range on Caucasus map. Had George switch to the rockets and crashed immediately after he said "Coming up rockets". Attaching my crash logs as well. Identical stack trace to this post, and the existing bug report in the ED DCS Discord bug reporting channel. dcs.log-20250911-232856.zip

@mla306, another user just reported similar behaviour, and has same stack trace as you, in the Eagle Dynamics DCS Discord server bug forum. I've dropped your log and link to your post there as well if it helps them further. The user who posted there stated that this occurred for them in multiplayer, so not just this mission. The key thing they've highlighted, and they tested a few things, was that this occurred when asking George to switch to rockets... and the rockets are the M151 ones with the M433 Resistance Capacitance (RC) Fuze. Can you check in the mission editor for that mission 1 (you said the others were fine), if it's possible, to see what the weapons loadout is for that Apache to see if it's the same. If you can't access that in the mission editor yourself then post this info back to Stone Sky. Would recommend asking them anyway. If not the same rocket type and fuze then see what it is for you, ask Stone Sky if needed, and report back. I can pass this onto the other user and see if they can replicate with that loadout as well. I'll try this in the next few days myself as well.