sleighzy

You have a number of mods, some of which are known to cause issues. Please remove your mods, run a slow repair of the game, delete your Saved Games\DCS\fxo and metashaders2 folders, and then try again. In addition to this your preload radius is set to 150000 which is really high and you're unnecessarily loading a lot of stuff. The DCS log analyzer recommended to drop that to 60000, as well as turning off SSAO which is a performance hit with little benefit. Looks like there is a track (.trk) file in that zip already so may or may not (if crashed without a chance to write this correctly) be from this occurrence.

This is a pretty common solution for VR players when they get FPS drops due to having used the F10 map (which loads in all textures around that area) and is the current hypothesis that this is freeing up VRAM resources.

Your log file shows an error in the logbook for the Mission Editor. Try renaming your C:\Users\username\Saved Games\DCS\MissionEditor folder to MissionEditor.old (this will get recreated when you next start the game). If you haven't already then I'd also recommend deleting your fxo and metashaders2 folders in the Saved Games\DCS folder as well. If that still fails then: Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. (it's important to rename so that you can copy back config afterwards to get your bindings if this works) In addition to this you have heaps of mods so failing that try removing the mods and run a slow repair of the game. You can add the mods back again if that fixes it (may need to do one by one to figure out which one caused the issue if that was the case. Mods can often break between upgrades) You have an existing page file set to 16384. I'd recommend increasing that to 32768. Some additional tuning items reported by the DCS log analyzer for your log file: Disable civil traffic. Set Preload Radius to max. 60000. You currently have a preload radius of 109700 which is really high, especially given your RAM and VRAM, so you are loading a bunch of unnecessary stuff. Decrease Terrain Textures. Turn off Depth of Field. Set Water to Low. Turn down Anisotropic Filtering. Drop another log file here if this continues to happen after you've tried the above.

Awesome, glad it's working. Yeah normal start process would be to connect your headset via Link and connect that first, and then go to your desktop and start DCS. Happy flying!

Those shortcut parameters don't have a space between them so aren't doing anything anyway, you can delete them. Your DCS settings obviously have "Enable VR Headsets" turned on which is why it launches in VR. It doesn't matter that the other one goes to "DCS_updater.exe", this just checks for updates and then will go to DCS\bin\DCS.exe automatically. If you go into that DCS\bin directory and double-click DCS.exe (don't use the shortcut) what happens? Does it still fail then? Both of the DCS.exe files in bin and bin-mt are identical so it shouldn't make a difference. Are the file sizes of the DCS.exe identical in both of those directories?

Can you please attach another log file for this working now for comparison purposes. Both bin\DCS.exe and bin-mt\DCS.exe should be the same as there is only multithreaded now. You also don’t need those command line arguments. The —force_OpenXR one is redundant as there is only the OpenXR version so this is the default.

This log shows that you do not have an OpenXR runtime installed or configured properly. What headset do you use? What is the app you are using for your OpenXR runtime (depending on the headset, e.g. for Quest you need Meta Link app or VirtualDesktop, Pimax will be PimaxXR or PimaxPlay etc.)? 2025-01-05 00:49:23.845 INFO VISUALIZER (Main): [19:49:24.465][Info ] OpenXR: Environment Access Check timeout is: 25047 milliseconds 2025-01-05 00:49:23.845 ERROR VISUALIZER (Main): OpenXR failure runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:433 2025-01-05 00:49:23.845 ERROR VISUALIZER (Main): OpenXR exception: runtime is not available Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:433

Your issue is unrelated to this post. Please raise another post, or alternatively take this to the Eagle Dynamics Discord server. You can drop your log into the #dcs-log-analyzer channel which will provide feedback, and/or ask in the #dcs-help-channel

No "fix" required. Drop your dcs log file here as it may give indications as to why it's falling back to 2D. I'm assuming you're attempting to launch in VR, e.g. have ticked the "Enable VR headsets" box in the DCS VR settings, or selected the little man in the goggles by the big orange button in the new launcher (which does the same thing). What is set as your OpenXR runtime? You have PimaxXR installed, or have PimaxPlay installed and have selected Pimax OpenXR within it? The dcs log file will help identifying more of that info as well.

Interesting. Potentially the request from PimaxPlay will state the resolution and focal area it requires. The QVF API layer sits between DCS and the runtime, so in theory will be converting the 4 views per frame back to the stereo 2 views prior to it hitting the runtime, in which case the conversion occurs in the API layer and not the Pimax runtime. I can edit this comment later with a link to a good diagram from Mbucchia on this topic. QVF and DCS logs would indicate more. Don't know if you tried with turbo mode turned off in QVF as well?

Check what I was responding to. If Mbucchia's Quad-Views-Foveated layer is still installed, and you enable Quad Views in PimaxPlay, it will still use Quad-Views-Foveated. It doesn't "take over from it".

This is not the address for credentials but can you run the below two commands (run each one seperately) from a command prompt in Windows and drop the results here: ping cdn.digitalcombatsimulator.com ping www.digitalcombatsimulator.com EDIT: and just to be 100% clear, should be run when NOT on the VPN.

Mbuccias QVF API layer still needs to be uninstalled though if you were previously using it otherwise it will use that.

No. You do however need to replace the nvngx_dlss.dll file in the bin and bin-mt folders again. Is this dropping the sharpening slider in DCS to 0, or some other config item?

Can you attach a dcs log file here after starting up completely into the game as well.

Hmmm, yeah I’d noted an odd saved games path for the other reporter as well. So possibly just an issue with the saved games location and resolved now with moving it properly back to another location?

This is not the standard path which would be under C:\Users\username , did you use the Windows procedure for moving the saved games system folder (right-clicking the folder and then choosing properties and updating the location to another root), or some other means?

I would recommend 2x32 sticks if you’re going to 64gb. Having 4 sticks can reduce the speed of the RAM due to the number of additional channels, can cause issues for OC profiles and memory timing issues. In the interim I’d recommend a 32gb custom page file if you don’t have one already. Single custom page file with Initial and Max values of 32768 on your fastest SSD (remove any other system managed page files). Click set, apply, and restart your PC.

Update to my earlier comment: The Quad Views Companion app v1.0.14 added support for configuring the height and width of the focal area for fixed foveated rendering (non-eye tracked headsets) a few days ago. https://github.com/TallyMouse/QuadViewsCompanion/releases

Can you drop more info around the registry issue and what you did to fix it in case other folk also hit this problem. Cheers.

I believe one difference with Steam is that the verify files does not have the option like Standalone does to remove any files that are not part of the core installation. This means it could fix modified files, but the installation could still contain other mod files, etc. To clear shader caches delete the "C:\Users\username\Saved Games\DCS\fxo" and "C:\Users\username\Saved Games\DCS\metashaders2" folders. The new launcher also has this option under the Files item in the menu.

Missed a testing use case, going to retest with replacing the %20 with a space like Mordants did and see if they are renamed, and if any freezing occurs. EDIT: Retested. The files are not renamed, they are added again so you have duplicated ones, e.g. same filename, one with %20 and one with space.

I have a new ImagesShop folder, this is post the unification of the versions, which contains only %20 files (this is from DCS on a new PC from a few weeks ago) and no duplicated ones for spaces. I also have a backed up one from my old PC that contains files both prior to the unification and from when they unified it, which contains both the old (non %20) and the new (%20) file names for the "same" (duplicated) filenames. So would appear that somewhere along the way the packaging for these filenames isn't url decoding properly (or something of that nature) so isn't replacing the %20 with a space. My testing steps: Delete the ImagesShop folder and start DCS. The ImagesShop folder is created but contains no contents. Start a mission. The ImagesShop folder is then populated with the images. This contains the ones with %20 and no duplicate filenames with spaces. This is why it would appear to work the first time, as there are no images to load when DCS is first started, until you are flying. I then stopped DCS and started it again and it works as expected. I then stopped DCS and replaced the ImagesShop with my older version that contains the duplicates Started DCS and has no issues, the same as you and apparently most other DCS players except for the two reporters here. If @Mordants is deleting the ImagesShop folder then in theory when it is recreated it should only contain the ones with %20 and no duplicated ones with spaces. So I'm curious as to whether or not he gets duplicates, and/or he has any other files that we don't which may/may not be duplicates, and/or have %20 in the filenames.

Yup, I only have a subset of those however. I'm curious as to whether or not he also has a subset, or any additional ones which we may not have.

Sorry, don't mean to tangent here but you need to replace the nvngx_dlss.dll file in the "bin" and "bin-mt" folder. Should be both (although you'll only be likely to be using the "bin" directory using the normal DCS shortcuts).