sleighzy

I've dropped your logs into the DCS log analyser which has the following to say for the crash: Your DCS has crashed. Errors Memory Timing Issues Remove any overclocking (XMP) from your RAM. There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. The crash occurred inside dx11backend.dll. Try running a slow repair for the game including removing extra files. Delete C:\Users\username\Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. In addition to this you only have 32Gb of RAM so you can create a custom page file to give you more headroom and reduce the chance of out-of-memory problems. Create a custom page file, just a single one on your fastest SSD, remove any system managed ones. Create it with Initial and Max values of 32768, click Set, Apply, and restart your PC. Additional tuning tips: Turn down Anisotropic Filtering. Set Water to Medium or Low. Enable Full Screen mode. Set Preload Radius to max. 60000. You currently have 150000 set for your preload radius which is really high for your RAM and you will be unnecessarily loading in a bunch of textures and other items when not required and may be redundant. Advice for Windows if not already done. Note that these are general items to help with performance and not to resolve your issue: Disable Game Mode Disable Hardware accelerated GPU scheduling Disable Core Isolation Disable Core Parking

Won't solve your overall problem, however if you download the latest DLSS 3.8.10 version and replace the nvngx_dlss.dll file in both the bin and bin-mt folders with that then it should reduce the ghosting. This is especially true of DLSS, but should apply to DLAA as well. https://www.techpowerup.com/download/nvidia-dlss-dll/

For an alternative map use the DCS Web Editor Moving Map. It’s a dynamic F10 map replacement. For VR this can be displayed within OpenKneeboard.

No. The DCS log will tell you that the Quad Views layer is there, but not if it is activated or not. You need to turn on Quad Views in DCS settings as to enable this. If you are using Mbucchia's QVF layer then you will need to check the "C:\Users\username\AppData\Local\Quad-Views-Foveated\Quad-Views-Foveated.log" file to verify this. This should display the settings that you have configured and the pixel savings it is giving you.

No, those line are common to all DCS VR launches regardless of the runtime used or whether or not Quad Views is used. EDIT: I see views 0-3 listed here so yes looks to be Quad Views with the calculated values for each of the 4 views. Other logs without Quad Views show only views 0-1. I'll retest mine with Quad View disabled to verify that mine also drops from 0-3 down to 0-1.

I've dropped your DCS log file into the DCS log analyser which has the below information. Note that this may not resolve your issue. Hot plug Events Disable hot plug in your DCS CONTROLS section, it's the button at the bottom right of the controls settings. If you plug in new controllers in the future you can click the "Scan devices" button. This will prevent DCS from constantly scanning for new USB devices, which can lead to stutters. Advice In Windows: Disable Game Mode Disable Hardware accelerated GPU scheduling Tuning Tips Disable civil traffic. Consider using DLAA. Errors Error attempt to index local 'accel' (a nil value) Line 69 Script C:\Users\game\Saved Games\DCS\Scripts\Export.lua Can you expand a little on "pausing and loading". Do you mean like lengthy stutters? How long are the pauses? After the initial take off does the game become smooth again, or this continues to happen throughout the flight? You could also drop your preload radius down as well, it's currently 100000. You could drop to 60000 so that it is loading less map and textures (possibly unnecessarily) into RAM when you first start. Have you also tried removing your custom mods, deleting your Saved Games\DCS\fxo and metashaders2 folders and seeing if this makes a difference?

There is apparently a fix in the latest v1.9.12 beta release for this you can download. Additional comment here re: config setting that can also be updated that may help: https://github.com/OpenKneeboard/OpenKneeboard/issues/658#issuecomment-2395163358

My humble apologies. I’d thought at the time that only Varjo and PimaxPlay had native support in their runtimes for Quad Views. So yes Somnium does too.

Numerous forum posts on this. Index controllers are still broken.

If you want to try Quad Views (may help you with performance but will also depend on your CPU as it increases the load there) then yes. You will also need to install https://github.com/mbucchia/Quad-Views-Foveated as well.

There are a few script errors to do with sounds, which may be related to your Echo19 mods. Remove all your custom mods and run a slow repair of the game. Delete your "Saved Games\DCS\fxo", "metashaders2", and "%LOCALAPPDATA%\TEMP\DCS" folders and try again. There is an OpenXR runtime crash message as well, although this is post the initial DCS crash in the log. I've also dropped your log into the DCS log analyser which has the following to say: Additional items: Set Preload Radius to max. 60000. Your preload radius is currently really high at 150000 for your RAM, and not necessary. Turn off SSLR. Turn off SSAO. Enable Full Screen mode. Consider using DLAA. In Windows: Disable Game Mode Disable Hardware accelerated GPU scheduling

You should probably be raising this as a new post. vs. adding to this one. However, try installing the latest version of the Microsoft C++ distributables, https://aka.ms/vs/17/release/vc_redist.x64.exe (which come from here https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170). Failing that remove all custom mods and run a slow repair of the game, or verify files if on Steam. A number of mods are now broken with later releases of DCS. If it still doesn't launch then upload 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) here for review. This should probably be done as a new post.

Changes almost of them, except for the Horizontal focus size and Vertical focal size for non-eye tracked. Changing the sliders in the Companion app for those will update the "horizontal_focus_section" and "vertical_focus_section" values (for DFR), but not the "horizontal_fixed_section" and "vertical_fixed_section" values needed for FFR. EDIT: sorry, saw you just responded with an edit as I was writing this. All good.

Just a heads-up that changing the focal areas in the Companion app only works for eye-tracked headsets. The config file needs to updated manually for the horizontal_fixed_section and vertical_fixed_section values to change these on non-eye tracked headsets. Saving any changes in the Companion app will also overwrite those.

New tool from Fred for performance profiling OpenXR games, e.g. DCS. Good info on FPS, frametimes, VRAM usage, throttling, etc. May help isolate some things. https://github.com/fredemmott/XRFrameTools

Can you ensure that you've removed all other page files, e.g. any other Windows system managed ones, so that you have only one page file for your entire PC. Your screenshot shows Currently allocated = 42752 (I would have expected 32768) and the screenshot is cut off at the top so can't tell what other ones you have.

Definitely upgrade now. Good performance improvements in Windows 11 for AMD chips and CPU core scheduling.

You could try deleting your shader caches and see if this makes any difference. Delete the fxo and metashaders2 folders in your Saved Games\DCS folder. (There’s an option in the Files settings in the new DCS launcher for this as well).

Yeah the second one which works is an older version of DCS that does not include the new DCS launcher. When you run the later versions of DCS now you’ll get a launcher which provides a lot (all?) of the config options Skatezilla does (without needing to start the game and can choose to launch in VR or not). The issue here looks to be Skatezilla tool passes some extra params which are not compatible with the new launcher (the manifest params causing your isssue). For the latest DCS version just use the launcher it now comes with (the DCS exe in the bin dir, you can update existing shortcuts to point to this).

Which GUI launcher is that, the Skatezilla one?

If you have the licenses for the planes which these mods require then add an exclusion to your anti-virus software, e.g. Windows Defender, for your entire DCS installation directory and run a slow repair of the game. Check also the instructions for the mods as most should be going into your Saved Games folder and not the main DCS installation folder. See here for more info on this: https://www.digitalcombatsimulator.com/en/support/faq/authorization/#3315427

Thanks @MAXsenna, nice followup. I'll have to keep those screenshots in my back pocket, cheers

System settings in Windows. Go to the graphics settings and its "Hardware-accelerated GPU scheduling".

Just a heads-up that the horizontal and vertical focal sizes can't be controlled via the Companion app for folk on non-eye tracked headsets. Those settings need to be updated for the "horizontal_fixed_section" and "vertical_fixed_section" directly within the settings.cfg file itself. In addition to this anything saved in the Companion app will overwrite those settings. So for a non-eye tracked headset that app is good for the initial creation of the default settings.cfg file, but after that you should tweak directly within the file.

The settings are not in Saved Games. The file is “C:\Users\username\AppData\Local\Quad-Views-Foveated\settings.cfg”