sleighzy

Don't know. DCS was always using C if not overridden. I'd only honestly tried E and F if memory serves me correctly (in VR), and stuck with F at the time like a lot of folk. Were you using D?

@BIGNEWY, if DCS were to ship with this later version then my original post here for a request to change the preset would become redundant as we would get this for free. Thanks in advance.

Yup. This release removed all the presets except for E and F. DCS used to use C, but now this is defaulting to E. No more need to use DLSSTweaks to override the preset (unless you still want to use it for updating other values / debug overlay).

It should have picked them up, it reads from the same location, so don't know why if you were noticing large differences.

Your DxDiag file contains the last 10 system/process crashes: DCS (3 times) - you're aware of this one The Oculus Tray Tool (4 times) 3D Mark Speed Way Live Kernel Event (2 times) - these ones have an error code of 141 which can indicate a hardware issue (particularly GPU overclocks in some cases). Even if you're not applying an overclock the manufacturer of your card may have. I believe MSI Afterburner may be able to identify that and remove.

I've dropped your DCS zip file in the DCS log analyser which had the following to say: Errors Memory Timing Issues Remove any overclocking (XMP) from your RAM. The Integrity Check failed Delete all unofficial mods and do a full slow repair of DCS, and choosing the option to remove files. Error Error: attempt to call method 'getCoalition' (a nil value) Line 2846 Script l10n/DEFAULT/Ground Missions.lua Error: attempt to concatenate global 'iniUnitTypeName' (a nil value) Line 1089 Script l10n/DEFAULT/RAT.lua There is a GPU-related error Remove any overclocking from your GPU. Uninstall your GPU driver with DDU and install a clean one.

There are a lot of memory allocation errors in that log with it attempting to decompress texture files. I see your preload radius is set to 150,000 which is far too big for your processor, RAM, and card. The DCS log analyser recommends dropping that to 30,000. It also states the following: Set Water to Low. Enable Full Screen mode. Set Preload Radius to max. 30000. Turn down Anisotropic Filtering. Can you also run the Windows dxdiag tool and save the report it generates and attach it here as well.

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).