sleighzy

Repeat the crash and then attach your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file (may just be a text document named "dcs") here. Don't restart after before retrieving the log file. Check the docs for the OpenXR Toolkit as there is information there in running in a safe mode and reverting back to the default settings. https://mbucchia.github.io/OpenXR-Toolkit/ You may need to completely uninstall it. Because even disabling it in the companion app isn't working for you then you can also the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool and untick the OpenXR Toolkit API layer in there. This should completely disable it so that it is not used when DCS starts whilst troubleshooting further, you can tick the box to enable it again.

Wasn't quite sure if I understood your update. QuadViews Companion doesn't work with the Quad Views in the PimaxPlay, so any settings you have in there won't be taking effect. You need to install the Quad-Views-Foveated API layer and use that instead if you want to use the Companion app.

Just a heads-up as well that the BeaconTypes.lua script error is a red-herring. This appears in pretty much everybody's logs at the moment so won't be something that you've done on your end, you should be able to safely ignore that one.

All good mate My mantra for the last couple of decades has been "It's always the simple things that cause the most problems". Just a matter of finding them. Glad we good we got it. Happy flying, sing out if it crops up again.

I've had a look at this log, and dropped it into the DCS log analyzer. It doesn't contain a crash, so load into that multiplayer server and send one when this occurs. Here is the initial following feedback. If you have FPS issues, try turning off VSYNC in graphics settings. Enable Full Screen mode. Turn off Depth of Field. Turn down Anisotropic Filtering. Set Preload Radius to max. 60000. Disable civil traffic. Your preload radius is currently really high (100000) so dropping that right down will reduce the amount of textures that get initially loaded. This may be why you get that long slow load time at the beginning. You only have an 8Gb VRAM card so once that's full it'll start spilling out into your system ram and page file, which will be much slower. Are both DCS and your page file on SSD drives (preferably NVMe)? If you haven't already then add the entire DCS installation folder as an exclusion into your anti-virus software as well and then restart your PC. Are you using Windows Defender for this, or another 3rd party anti-virus software?

Its a Windows tool. Run DxDiag and save the report it produces and drop it here. It tells use more about your system and also contains the last 10 application crashes on your PC.

DCS won't do this. If your PC is shutting itself down then you have an instability in your system somewhere else, e.g. memory timing issues, temps, hardware etc. There are ways of diagnosing this.

Can you please attach your “C:\Users\<username>\Saved Games\DCS\Logs\dcs.log” file, may just be called “dcs” if Windows is hiding file extensions. Make sure the log is taken after the game has completely loaded. Remove all mods, run a slow repair of the game (with the option ticked to remove files), delete the fxo and metashaders2 folders in the “C:\Users\username\Saved Games\DCS” directory and try again. If it crashes again then without restarting the game send another log. There may also be a crash zip file there as well.

I also notice you have a lot of OpenXR headset related items in the logs. These are not something I've seen to the same extent in other logs in the past, e.g. here is one snippet. These are repeated about ~10 times with about 2 minutes in between some of them. How is your headset connected to your PC? 2024-11-26 17:17:55.593 INFO VISUALIZER (Main): [18:17:55.676][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_FOCUSED->XR_SESSION_STATE_VISIBLE session=72075443922010113 time=275600165189399 2024-11-26 17:17:55.593 INFO VISUALIZER (Main): [18:17:55.676][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_VISIBLE->XR_SESSION_STATE_SYNCHRONIZED session=72075443922010113 time=275600165203200 2024-11-26 17:17:55.593 INFO VISUALIZER (Main): [18:17:55.676][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_SYNCHRONIZED->XR_SESSION_STATE_STOPPING session=72075443922010113 time=275600165244099 2024-11-26 17:17:55.603 INFO VISUALIZER (Main): [18:17:55.685][Info ] OpenXR: XrEventDataSessionStateChanged: state XR_SESSION_STATE_STOPPING->XR_SESSION_STATE_IDLE session=72075443922010113 The log seems to indicate that it takes a really long time to load into missions, minutes at a time? How long does it feel like on your end?

Pun intended?

Improved spotting dots, the ability to turn them off, is currently broken in DCS right now. Heaps of complaints around issues with the new spotting changes, and zero ability to opt out using that switch as it’s not working.

If you're referring to the PimaxPlay runtime and turning on Quad Views in there then that is different from Quad-Views-Foveated which you get from Mbucchias Github repository (if this is the thing you additionally installed). Can you confirm whether or not that is the case. You may find that one is interferring with the other if that is the case. "I also installed the thing QuadViews tells you to install to make it work." - what is this additional thing?

Yeah may not have uninstalled everything correctly. ReShade 6.0 definitely had problems. Recommend using this tool and just untick the ReShade box so it's completely disabled in VR so you know for sure: https://github.com/fredemmott/OpenXR-API-Layers-GUI

Especially as how you wrote the go-to handbook on setting up ReShade with OpenXR

You have the ReShade OpenXR api layer installed. Remove this and try again. There are known file access issues with this. What version of ReShade do you have installed? Can you also drop your ReShade.log file from the bin and/or bin-mt folders of your DCS installation for both this issue occurring (no OXRTK) and when it's fine (OXTK). Probably best to raise a new post with this information like Slugmouse said so that this current thread doesn’t get polluted. Really interesting that OXRTK seems to have an effect on this.

Drop your DCS log file here. “C:\Users\username\Saved Games\DCS\Logs\dcs.log” (it may just be a text document named “dcs” if your Windows is hiding file extensions). Drop the crash zip file here as well if one was produced. Make sure you replicate the issue and drop the log here first before restarting the game Does this only occur for missions from the mission editor, ie single player missions, instant action, etc. all work fine? You can also try renaming your Saved Games\DCS\MissionEditor folder to Saved Games\DCS\MissionEditor.old and starting the game again. This will cause DCS to recreate the Mission Editor if this is corrupt.

That shortcut you’re using to launch the game with looks a bit suspect. It has params in it to specify the manifest file, which is exactly the error you’re getting. May explain why it works when you run it directly without using that shortcut. Where did that shortcut come from? Delete all the params from the end of it (force_OpenXR is redundant as the game only uses OpenXR). You can keep the force_enable_VR one if you have one for vr and one without (although with the new launcher you can do this anyway).

@Licenceless, you have lots of usb plug/unplug events in your log file. Go into your DCS controls settings and there will some buttons on the bottom right. Click the one to disable hotplugging devices. If you add a new controller in the future you can click the Rescan devices button. Having this enabled can cause stutters as DCS will be constantly scanning for new usb devices.

There is zero difference. Standalone will still use SteamVR for headsets that need (or want to) use SteamVR as there OpenXR runtime. All you are downloading is DCS from Steam, it does not have anything to do with SteamVR. You can’t. If you bought DCS modules from the website then you’ll need to purchase them again from Steam, they aren’t transferable.

In this earlier comment (https://forum.dcs.world/topic/362630-hp-reverb-g2-flying-ah-6/page/2/#findComment-5554723) you posted some screenshots of your settings. On the screenshot that shows "Startup and desktop" you have a box ticked "Start Windows Mixed Reality for SteamVR automatically when Mixed Reality Portal is launched". If you untick that box does it prevent SteamVR (completely close it first) from automatically opening like it is right now and just launches DCS with WMR without bringing up SteamVR?

Just a heads-up that the Steam version and the Standalone version are completely identical (same files and everything). I'm assuming you don't own any modules on the Standalone version as you won't be able to play them on the Steam version though due to licensing.

The crash in this log is different from the original crash in this post, unknown as to whether or not they are unrelated. In the case of this one have you tried disabling ReShade and running DCS for awhile to see if it crashes? Do you recall what ReShade version you're running? You can use the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool to uncheck the ReShade box to disable that OpenXR API layer for testing purposes. What version of Virtual Desktop are you on, and what other games do you use it for? You could always uninstall and reinstall the VD Windows streamer app in case there's any problem there. Essentially, if you're using VD then you want to use the VDXR runtime vs. SteamVR. It's more performant as you're not loading all the SteamVR overhead. I also noticed in your log you have the gunner_export hook from the OH-6 mod. This has documented performance issue than can cause stutters. There's a new release of this mod that apparently has a more performant hook, I don't know which version you're on, but otherwise it recommends to remove that hook. The mod itself is fine. Just something to look out for if you do notice stutters in the game.

This log is just from opening the launcher. You need to actually start the game completely and then provide the log.

Bit of a known issue that a number of people are reporting. Seems if you go to the VR tab they stop working until you restart the game again.

Did you also install Quad-Views-Foveated, or just tick the box? What headset do you have? You need to install Quad-Views-Foveated if the runtime you're using does not natively support this, e.g. PimaxPlay is one such runtime that does (if you've selected that it is the OpenXR runtime).