sleighzy

Myself personally, I'd update your DLSS library to this version. Means no need for DLSSTweaks/Nvidia config if you just want to get preset E by default. This should hopefully reduce your ghosting, and who knows when DCS will get around to updating their version of this.

Just retested with this latest version, after removing my preset override. DCS is now using preset E as the default preset C it was previously using has been removed.

Just tested now using the latest version and not overriding the preset. The debug overlay shows that DCS is now using preset E. This was previously C by default but now that this has been removed it's on E.

DLSS 3.8.10 has been released https://www.techpowerup.com/download/nvidia-dlss-dll/?amp Notably based on this article all other presets have been removed and only E and F remain. I’ll test this latest release with DCS using the defaults and see which preset it decides to use. https://www.tomshardware.com/pc-components/gpus/nvidias-latest-dlss-3-8-10-version-features-only-two-presets-preset-e-and-preset-f-chipmaker-trimmed-the-dll-file-size-by-more-than-50-percent

@Mustang, these dlls can be located at this site so you don’t need to extract and share yourself (especially for folk who may be nervous about downloading a dll from an unknown user). https://www.techpowerup.com/download/nvidia-dlss-dll/?amp Ran across this article on the latest release and looks like the other presets have been removed and only E and F are remaining. I’ll retest this with the defaults (not overriding the preset) with this latest dll and see what DCS ends up using. https://www.tomshardware.com/pc-components/gpus/nvidias-latest-dlss-3-8-10-version-features-only-two-presets-preset-e-and-preset-f-chipmaker-trimmed-the-dll-file-size-by-more-than-50-percent

@RotoDan, that latest log is just from you opening the launcher. I need a log from when you actually start the game completely (using VR).

@Joch1955, just a heads-up from the current log attached previously (while you're waiting for feedback for the other items you've requested): this is a standalone DCS installation (non-Steam) there are no shortcuts in use Mbucchia's OpenXR Toolkit is not currently in use, and there are no other API layers installed either (unless this has changed recently)

@RotoDan , can you send a log file for this happening. The original log shows that DCS doesn't even think you have a headset connected. The original log also doesn't show an immediate shutdown. If you can repeat that with the reverb on and DCS immediately shutting and attach a new log that more provide more info. I'll leave the process of starting DCS with a G2 (and any associated screenshots) with @Joch1955 and @Maddaawg as they appear to be more familiar with those aspects.

Ok, so based on the log file it appears that DCS knows that you're using the Windows Mixed Reality (WMR) runtime, but it is not detecting the headset itself. As you can see from the below lines it waits for the headset for 10 seconds, then gives up and starts DCS in 2D. This is normal when starting up if you haven't connected a VR headset, but from what you've described the headset is connected and you can see DCS in the googles, but it's just in 2D. Just to confirm, this is the log file from when attempting to start DCS in VR when you're wearing the headset and it's connected? Not owning a G2 myself I can't comment as to why that would be, other than it is. 2024-11-12 04:42:50.861 INFO VISUALIZER (Main): [21:42:51.226][Info ] OpenXR: Instance RuntimeName=Windows Mixed Reality Runtime RuntimeVersion=113.2405.31001 2024-11-12 04:42:50.861 WARNING VISUALIZER (Main): [21:42:51.226][Warning] OpenXR: waiting for HMD to warm up... 2024-11-12 04:43:01.149 ERROR VISUALIZER (Main): OpenXR failure XrResult failure [XR_ERROR_FORM_FACTOR_UNAVAILABLE] Origin: xr Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:500 Further to this you're also running an old version of DCS, and it looks like maybe you need to update your Nvidia graphics driver as well. You should also go into the DCS controls settings and click the button at the bottom right to disable hot plugging (with hot plugging DCS will constantly scan for new USB devices which can lead to stutters within the game, if you add a new controller just click the Scan devices button there). Can you send a log file of this then. You also have tons of what appear to be shader issues. Can you delete your "C:\Users\username\Saved Games\DCS\fxo" and "C:\Users\username\Saved Games\DCS\metashaders2" directories before starting the game. I also recommend you update the game as well.

“Enable VR Headsets” is ticked under the VR tab in the DCS settings? Drop your “C:\Users\username\Saved Games\DCS\Logs\dcs.log” file in here (may just be a text document named “dcs” if Windows is hiding file extensions) so we can review, might be a runtime issue in which case DCS will start in 2D.

Is being covered in this forum thread, you can track progress and provide info there.

Given you're on a Quest 3 try AV1. Alternatively h.264+. Really comes down to your preference and performance. This is from the Virtual Desktop Discord: H.264: has the lowest latency but not as efficient as the other codecs H.264+: has higher bitrate limit; good for racing or fast-paced games but requires ideal network conditions HEVC: has improved efficiency (looks better at the same bitrate compared to H.264) but takes a bit more time to encode/decode AV1: has best efficiency but requires Nvidia 4000 or AMD 7000 series GPU and a Quest 3 10-bit encoding: improves color gradients, recommended for darker/slower games

Has been reported by other users on the DCS Discord server bug reporting channel for other maps and multi-player servers as well.

You don't for DCS. That list is for SteamVR games and does not include OpenXR games. That list is for compatible games that can VD can "inject" into their runtime (I need to refresh my memory on the more technical description), but is not like how you can add non-Steam games to your Steam library.

Attach your DCS log file for this occurring. Will be C:\Users\username\Saved Games\DCS\Logs\dcs.log (or just a text document named “dcs” if Windows is hiding file extensions). Attach a screenshot of your Oculus Tray Tool settings. What resolution do you have set? Do you use any other OpenXR tools etc? Can you also attach a screenshot with the DCS performance overlay open, believe it’s Right CTRL + Pause twice.

A log file might show why this is occurring for you, lots of folk still using it without issue, possibly something else you may have which is inteferring with it, e.g. you can use the tool I linked earlier to see what other API layers you're using. Quad Views has turbo mode enabled by default, which can break motion smoothing. Try disabling that and see if it resolves the issue.

@xxwolfxxkillerxx, the DCS log analyser had the following to say: For the repair, run a slow repair with the option selected to find extra files and remove them. For the repair, run Verify files in Steam. Can you drop another log / zip file here if it is still occurring after trying those steps. Based on the contents of your log there will be other suggestions for improvement and tuning.

@LucShep there’s a script here for generating optimized textures from your current game files (similar to Taz’s already optimized textures).

Might be worth trying Quad Views. You can install Quad-Views-Foveated (https://github.com/mbucchia/Quad-Views-Foveated) and then tick the Quad Views box in DCS under the VR tab. This is somewhat of a replacement of some of the functionality from the OpenXR Toolkit which is no longer supported. Turbo mode is enabled by default. For non-eye tracked headsets it uses fixed foveated rendering and will display a lower resolution image around the periphery with an adjustable multiplier for the main focal area. The focal area can be increased or decreased. This will increase load on the CPU (and remove some from your GPU) but with your 5800x3D you’ll be fine. if you don’t like it then just untick the Quad Views box in DCS and remove it.

OpenXR won’t be the root cause as this is the API used by the game for VR (which is used by all runtimes / headsets). When using Virtual Desktop you should use its VDXR runtime vs. the Steam OpenXR runtime.

One thing that sprung to mind is you mentioned you have 4 sticks of RAM. You could check if you have an XMP profile set in your BIOS for your RAM, and turn it off if so. Four sticks may be more susceptible to timing issues and crashes than two sticks when using some XMP profiles. Worth a shot to rule it out.

Humble apologies for the late response. From the latest log you attached I can see the runtime XR_ERROR_RUNTIME_FAILURE error, no specific cause though. This log shows that the Mbucchia Quad-Views-Foveated api layer was running. Do you recall (been a long time I know) if the crash in this log was when the "OpenXR QuadViews" box was ticked in PimaxPlay? The log also shows a lot of USB unplug/plug events. Can you disable hot plugging in the DCS controls settings (it'll be a big button at the bottom right). This will stop it constantly scanning for devices (and can help with stutters as well). If you plug in a new device you can hit the scan devices button on the controls page.

Oh well, good progress anyway, at least you’ve narrowed down the cause. Small consolation, but you get to play DCS without it crashing on you You could also add a larger page file to help with the loss of RAM. If you do decide to then just add a custom page file on your fastest SSD with initial and max values of 32768, click set, apply, and restart your PC. Make sure you only have one page file, eg remove any system managed ones. Might help with performance where needed until you get your full physical 64gb ram back again.

Really sorry to hear that mate. From that last DxDiag log: Couple more of the LiveKernelEvent 141 errors Some blue screen of deaths which you've noted (don't have a system code, or not seeing it properly, for cause of these) ASUS Armoury software (ArmourySocketServer.exe) Crashes with the Windows login screen (LogonUI.exe) Another one for DCS with the same memory problem If you do manage to get into your system, even if starting up in safe mode, there are some items you could check here, one of them being a memory test. Don't know if you're getting any system codes etc. on your blue screen which may indicate more around the cause. https://support.microsoft.com/en-us/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6

The DxDiag report shows that there are crashes for the following: Google Earth (googleearth.exe) Ghost Recon Breakpoint (GRB.exe) - this is an assumption based on a Google search for that process name. This crash indicates the application wasn't properly handling memory(?) DTS Sound Studio (DtsApo4Service.exe) Cinebench DCS (DCS.exe) - possibly not handling memory properly LiveKernalEvent - this has a code of 141 which indicates a hardware issue Based on the above it appears you may have issues across your system and not just DCS. Does the above list sound correct? The "not properly handling memory" ones may be related to system problems. Can you run the below two separate commands from a command prompt (cmd.exe) as an administrative user, restart your PC, and see what happens. Let me know if those commands identify and fix any issues. dism /online /cleanup-image /restorehealth sfc /scannow If you're updating graphics drivers try using DDU to completely clean any old drivers first.