sleighzy

Drop a DCS log file here and we can have a look at your current DCS graphics settings. With your specs you should be able to pump things up. Confirm also that the Pixel Density (PD) setting in DCS under the VR tab is set to 1.0 as some of the recommendations, e.g. additional VR tools, we can provide will depend on that. Within Virtual Desktop (the settings in the headset) what is your resolution set to? Godlike? And what is your VD codec and bitrate set to as well. With respect to the Nvidia settings I've attach a document with some recommendations from the VR4DCS Discord server (the #nvidia-gpu-discuss channel)NVCP_Settings_V3.2_WIP.pdf

The general reason the log analyzer has that message is that the recommendation is to use Windows 11 (and disable core parking) as this has better support for hybrid CPUs (P/E cores). This will be more performant as DCS will select the best cores to run things on, and Windows 10 may mis-report these which is why people sometimes get stutters (and use Process Lasso so that they can set which cores should be used).

Nice! Fixed after renaming the file? If so then somehow the config file got corrupted so was preventing things from starting up correctly.

Some additional items I noticed from your log. It shows that you have core parking enabled for your CPU. You should use something like ParkControl to unpark your cores. You preload radius is set at 100 which will mean it will be loading in assets frequently while you’re flying, may or may not cause visible stutters. With your RAM I’d change that to 30000 instead.

Your config is corrupt. Rename your Saved Games\DCS\Config\options.lua to options.lua.old and then restart DCS. It should regenerate new config again, you’ll need to reapply your graphics settings etc afterwards (it won’t lose your control bindings) You also have errors in the logs for it trying to start in VR and not finding an OpenXR runtime. In those cases it will just open in 2D. Can resolve that later if you do want to use VR.

Similar feedback from other folk re: the triggers. In all honesty DCS does not really support VR (quest) controllers for flying planes all that well. You'll have nowhere near enough buttons for the hotas controls. If you don't have a hotas then use an Xbox or PS controller. Look on Youtube for videos by Tuuvas on how to set that up and all the profiles for all the planes. Really simple and how many of us started off before getting a proper hotas.

This post is about cores reaching 100%, is this what you are experiencing? Your log is filled with errors from your mods and terrains. Remove those (including saved games mods/terrains) and run a repair. You can put them back, check the log to see which ones are causing errors each time, eg zip driver failing to open them Also what @scommander2 said, remove that process affinity mask from your shortcut, you’re killing off 3 cores (which seems like a weird number) making them not available. Recommend upgrading to Windows 11 as well to make better use of your cores. Run DCS from bin instead of bin-mt as well, they’re both multithreaded and bin-mt is going away. Ensure that DCS is also not being run as admin If you’re not using TacView then remove that as well as can cause additional performance issues.

Running UAC at lowest is bad. The description for it is a little wrong. The lowest setting will silently run some things as admin, even though they would run as non admin. This is possibly why you are getting this message.

The hard wiring is needed for the Ethernet connection between your PC and the router that you are connecting to with your headset. They recommend a dedicated router close to your play space. In the diagram above the dedicated router is on the right hand side, and the blue line has an Ethernet cable connected from that to your PC. Basically your existing router is just providing internet…which doesn’t matter as Virtual Desktop just needs a fast connection to your headset, it doesn’t use internet. Virtual Desktop guide for Internet Connection Sharing: https://github.com/Crayphish/vrdocs/wiki/Internet-Connection-Sharing

Not sure how your PC currently gets it's internet based on the distance between it and the router. Would this network configuration work for you? (Taken from the Virtual Desktop Discord for alternative network setups). I can post a link to the setup guide if needed. null

@Grubenstein, this is a log file from DCS 2.9.1 , I'd recommend upgrading as there have been a number of changes, including around multithreaded performance. There may be more info in logs from later versions as well that may be more helpful. You've said performance is bad across all versions so upgrading to current shouldn't be an issue. Nothing major jumps out in the logs, the DxDiag report however shows a number of issues when run through the DCS log analyzer. Windows Error Reporting (WER) Application Errors bad_module_info: 00000000 (StackHash_0000) Memory Timing Issues Remove any overclocking (XMP) from your RAM. Microsoft Update / Store issues Make sure you have enough free disk space. Run SFC and DISM to check your Windows. Run wsreset.exe to reset the Microsoft Store cache. For the SFC and DISM commands open a command prompt as administrator and run the below two commands separately. Restart your PC afterwards. dism /online /cleanup-image /restorehealth sfc /scannow Address the items above. Upgrade DCS. Replicate the issue again, with a full load of a mission, and then drop another log file here. When upgrading DCS delete the Saved Games\DCS\fxo and metashaders2 folders. (In your case it appears to be looking in Saved Games\DCS.256) Some additional items from the log analyzer: Set Water to Low. Disable civil traffic. Enable Full Screen mode. Windows 10 will be EOL Oct 14th 2025. Upgrade to Windows 11. Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled

Never run DCS as administrator.

https://forum.dcs.world/topic/368163-dlss-4/page/11/#findComment-5611147

Attach your C:\Users\username\Saved Games\DCS\Logs\dcs.log file (may just be a text document named "dcs" if your Windows is hiding file extensions. Attach your <DCS installation dir>\bin\autoupdate_log.txt file You can also run the update/repair tool from the command prompt so you don't have to launch the game for that. Go to your DCS installation folder Right click on the bin folder and select "Open in Terminal" from the menu Run the below command in the terminal and hit enter .\DCS_updater.exe repair For your question about what to rename the folder to it's just rename Saved Games\DCS to Saved Games\DCS.old (then you can copy back the Config\Input folder once it's working to get back your controller bindings)

As long as VR headsets is enabled in the DCS config then it will always attempt to launch VR, don’t need special shortcut params for it. It’ll only use 2D if it can’t find a connected headset, or if your VR runtime is broken (check the log). Do you have one shortcut for VR and one for non-VR then? Does it start in VR just fine if you do use the launcher, or enable VR headsets in the config (which is what the launcher does automatically when you select the man with the goggles) or it’s only ever 2D, in which case the param isn’t the issue? Have you updated DCS since this param was working? Also use the DCS.exe in bin and not bin-mt (they’re both multithreaded now and bin-mt is going away in the future). Maybe the param works there (they should be identical though), I haven’t retested with the param.

Yes, I would make the core parking changes. As to recent changes, Windows 11 has better support for hybrid P/E cores and will identify which is which. Based on other forum threads and Discord channel comments DCS now makes better decisions around which to use for what. For example, allocating I/O to E cores so that those operations aren't being performed on your Performance (P) cores. Note: This may not solve your issue, but will be in a good state and filter this out going forward for any other logs or ongoing investigation.

I've made a fix for this to better handle on our end, no idea why the OpenAI Whisper model transcribes it this way. Will be available in a future release. The workaround should hopefully suffice for now.

I dropped your log file into the DCS log analyzer which reported at least one item which aligns with your log file. Update-Server unavailable Make sure your Internet connection is available. Wait some minutes and try again. The log file shows internet auth issues attempting to contact the server. 2025-04-29 18:47:22.109 ERROR SECURITYCONTROL (20596): Auth data has expired. 2025-04-29 18:47:22.110 ERROR ASYNCNET (20596): Getting auth data failed becase server returned invalid reply. 2025-04-29 18:47:22.562 ERROR APP (Main): Failed to get authorization data. Error code is: 500 2025-04-29 18:47:22.562 INFO APP (Main): Loading cached Steam auth data... 2025-04-29 18:47:22.564 INFO APP (Main): Nope 2025-04-29 18:47:23.951 ERROR APP (Main): Failed to get authorization data. Error code is: 500 2025-04-29 18:47:23.952 INFO APP (Main): Loading cached Steam auth data... 2025-04-29 18:47:23.954 INFO APP (Main): Nope The crash appears to be it attempting to write (unpack) files. 2025-04-29 18:48:01.169 ERROR EDCORE (Main): [C:\Users\igort\AppData\Local\Temp\DCS\Mission/l10n/RU/TF-51_FOT_ru{066DE39B-A9A7-4679-B36B-5785C8AFBDA9}.png] CreateFile(REWRITE): Access is denied. 2025-04-29 18:48:01.169 ERROR EDCORE (Main): Can't open file 'C:\Users\igort\AppData\Local\Temp\DCS\Mission/l10n/RU/TF-51_FOT_ru{066DE39B-A9A7-4679-B36B-5785C8AFBDA9}.png' from real path fs. 2025-04-29 18:48:01.169 ALERT LUACOMMON (Main): Error: GUI Error: [string "./Scripts/dictionary.lua"]:579: VFS_open_write: Can't create file C:\Users\igort\AppData\Local\Temp\DCS\Mission/l10n/RU/TF-51_FOT_ru{066DE39B-A9A7-4679-B36B-5785C8AFBDA9}.png GUI debug.traceback: stack traceback: [C]: ? [C]: in function 'unzUnpackCurrentFile' [string "./Scripts/dictionary.lua"]:579: in function 'unpackFiles' [string "./MissionEditor/modules/me_mission.lua"]:2258: in function 'load' [string "./MissionEditor/modules/me_quickstart.lua"]:275: in function 'func' [string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater' [string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40> You'll see there that it doesn't have permissions to write to that file path. Can you delete the "C:\Users\igort\AppData\Local\Temp\DCS" directory and try again. Have you ever attempted to run DCS as an administrator? Don't do this, but just wondering if file permissions error.

I dropped your log file into the DCS log analyzer. It’s identified the crash as being a GPU related issue. Reinstall your GPU drivers. In addition to this make sure any overclocks have been removed from your GPU. This log file still shows a large number of mods installed. Reinstall clean GPU drivers using DDU to remove all traces of old drivers first. If the latest driver still has issues you could try rolling back to 566.36 Remove you mods and run a slow repair, replicate the issue again if it still occurs and drop a new log.

@FredOfMBOX Definitely looks like a bug. I’ll have a look into it. If you’re getting it consistently with menu— (and other words) you could try adding the below into the word_mappings.txt file to workaround it for now. menu--=menu EDIT: try just applying this as a blanket thing to see if this handles it. --= I’m not around for a couple of days to confirm the above blanket approach, but give it a shot.

That’s fine then, standard response from the analyzer when it sees memory timing issues so may be unrelated. Have a look at the other items and see if those help with what you’re experiencing.

@Aluminum Donkey @t-stoff, drop your DCS log files here. Helps provide information and knowing whether or not they correlate with the issues experienced by other users.

Dropped your log into DCS log analyzer, sounds like you have a few issues going on there. If you haven't already then general first steps: Try a slow repair of. the game, verify files in Steam Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Critical items from both DCS and your Windows DxDiag report: Windows Error Reporting (WER) Kernel Events The following kernel-events have been detected: BUGCODE_USB3_DRIVER Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. Application Errors DCS.exe: c0000005 (Effects.dll), was hung for 14.47s and killed, was hung for 41.06s and killed Memory Timing Issues Remove any overclocking (XMP) from your RAM. Generic Windows or Hardware Issues Remove any overclocking (including XMP). Run SFC and DISM to check your Windows. Check for any updates of your BIOS or chipset drivers. For the SFC and DISM commands, run a command prompt as administrator as run the two separate commands below: dism /online /cleanup-image /restorehealth sfc /scannow Additional advice. Note that upgrading to Windows with offer better support for DCS and use of hybrid P/E cores. I would highly recommend that. Upgrade your OS to Windows 11 to better support your CPU, or disable cores 16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31 in Windows or Process Lasso You have core parking turned on in your system. Install something like ParkControl and disable core parking. This has resolved this issue for a number of users, especially those upgrading to Windows 11 as well Verify that this is configured correctly in Windows: Game Mode disabled Hardware accelerated GPU scheduling disabled

Quad Views may also be an option if you haven't looked into this yet. Will be able to increase the resolution at the center and reduce in the outer edges. This will put more load on your CPU, and reduce it from your GPU. I'm not familiar enough with your CPU to comment further. All depends on where your bottleneck is but you may get some performance benefits, if not then adjust as necessary, or just turn it off.

Can you drop a DCS log here as well. Your settings look quite high, eg visibility range, and as much as you hate it the shadows. The Forest Visibility and details are really high as well, you can play with those sliders while playing to see the difference but being high is a performance hit, and may be unnecessary unless you’re flying treetop level in a helicopter the shimmering will most likely be due to MSAA, especially at only 2x. Going higher will be much more of a performance hit though, and still won’t entirely solve it. Recommend you try DLSS4 with either DLSS/DLAA or with using the newer J or K presets in later versions of the Nvidia driver. For your Nvidia control panel settings you want to set Low Latency Mode to “Ultra”.