sleighzy

Warning can be ignored, it just lists your available API layers. Looks like you have Quad Views in that list so should be all good. As long as it’s visible and ticked in the in-game menu (not just the launcher), then it should work fine. I’d put back the Mbucchia one now as the Sandbox version isn’t needed anymore.

Quad Views will only be available, and selectable, within the in-game menu if you have Quad-Views-Foveated installed (or an OpenXR runtime that natively supports this, eg PimaxPlay). The reason this shows up in the launcher is because it doesn’t check if this is present. Even if your friend sees it and can turn it on in the launcher it won’t do anything without QVF being installed. Also the launcher doesn’t hog resources, it just restarts DCS so I’m not sure where that information came from.

The dxdiag report shows that of the last 10 crashes, 4 of them were for "pppd.exe" (internet says this is for your UPS software, so something with the power supply?). There are another 3 for "fsx.exe", so I'm assuming you're using Microsoft Flight Simulator X as well? Do you experience any crashing issues with that too? The final 3 are StoreAgentScanForUpdatesFailure0 which can be related to a few different reasons, including issues with software and corrupted system files. Can you open a command prompt as an administrator and run the below two commands as well to confirm whether or not there are issues and they get fixed. dism /online /cleanup-image /restorehealth sfc /scannow

Not sure what you mean by "steam link". You shouldn't be connecting using SteamLink if connected via cable, just connect your cable and then use the Meta link app with it set to be the default OpenXR runtime if you haven't already. You can drop a DCS log here for reviewing your settings. Drop some screenshots of your Meta link app as well, e.g. what your resolution slider is set to.

This looks like a double-posting of

You're applying resolution multipliers in two different places so may effect things as well, e.g. multiplying things multiple times. Will also cause both GPU and CPU load (QVFR is gonna be more CPU load). Could try dropping the Quest to 1.0 and then bumping up higher in QVFR instead. YMMV. (...my comment above may be a little off-topic for this thread)

Yeah, drop your settings and see if this changes anything. I also ran your log through the DCS log analyzer which only highlighted the following items: drop your preload radius to 60000 change your custom page file to have initial and max values set to 32768 (looks like currently 12288), you should only have one page file on the PC and on your fastest SSD (with at least 10% free space) enable Full Screen mode

This is just a log from opening the launcher. Start the actual game, fly around a bit for the stutters, and then drop an updated log file in here. You also don’t need the “—force_enable_VR” and “—force_OpenXR” parameters on your shortcut.

Yuuurp. I think a bunch of people (myself included) have gone "wow, that's amazing, I definitely wanna do that"... then after 5 minutes of it we realise it's janky as hell and get the mouse out again.

One thing I note in the log, not saying it's the issue, is a few problems around the F14, including messages that it is a different version than the latest build. Can you remove all custom mods from your game, (including the lottafGameGUI.lua from your Scripts/Hooks directory which I'm not familiar with), and then run a slow repair. Delete your fxo and metashaders2 caches from the Saved Games\DCS folder as well, and then see if you can replicate this issue. If this continues to crash can you also run the Windows dxdiag tool, save the report, and attach here as well, along with the latest log.

Classic IT. Have you turned it off and back on again?

Another option is to install the Standalone version of DCS on your new drive. This will give you things such as 2 week free trials of planes and maps, as well as ED miles to go towards purchases of other planes/maps. Any modules that you have purchased on Steam can be transferred to Standalone. Just download the DCS installer from the web site and run it. It should attempt to find an existing Steam installation and copy the files from there so you don't have to do a full download.

The default preset for DCS is C. The default preset for the DLSS 3.7 library is E these days if an application does not set this. However it appears that DCS does actually set to this to C (you can see this when enabling the debug overlay), which at the time was the recommended preset for Performance/Balanced/Quality options.

No reaction in the Discord server?

Try removing your previous firewall rules for DCS and then start the server again so that it asks you if you wish to add rules for it. It’s been mentioned that with the latest patches that DCS will now run the DCS.exe in the bin directly, was previously bin-mt, now that everything is multithreaded and that firewall rules need to updated for the new executable. Give it a shot anyway.

This is out of beta and is available in the current v1.33 release.

Do you also have hand tracking enabled for your Quest, eg developer mode enabled and hand tracking working?

Are you looking at the settings in the launcher, or under the VR tab within the DCS game itself while wearing your headset?

It happens in a layer before it even reaches your OpenXR runtime or headset, so yes this should work for that.

DCS supports OpenXR runtimes and not specific headsets. So, as long as your headset has an OpenXR runtime for it then you should be all good.

Yes, this is just a general graphics setting and is not specific to VR.

Ahhh, in that case you’re not actually using Quad Views. Ticking the box in DCS just enables DCS to send 4 views, but you still need to install Quad-Views-Foveated or use the new Pimax software (which may actually be out of beta now). The QuadViews Companion app never gave you quad views, it is just a config app for Quad-Views-Foveated. If you go into DCS into the actual in game settings and not the launcher do you have the ability to tick and untick that box? Do you already have this installed? https://github.com/mbucchia/Quad-Views-Foveated

Note, the new PimaxPlay has native support for Quad Views (there is a tick box for it in the PimaxPlay settings). You can use this instead of the Quad-Views-Foveated API layer, so can uninstall that layer to test it out (still need to have the Quad Views box in DCS), but you will lose the ability to use the Quad Views companion app so will be restricted to the three options that PimaxPlay offers. You can also optionally install the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool and just untick the quad views layer vs. uninstalling it completely. Might be convenient if you're wanting to test out PimaxPlay native Quad Views vs. Quad-Views-Foveated layer to see what performance / visuals difference you get between the two.

Are you still using the Quad-Views-Foveated API layer, or are now using the new Quad Views support in PimaxPlay?

No loss of OpenXR Toolkit, you can still use this. If you instead switch to using QuadViews (as a number of us have for some time) then you can still use Fixed Foveated Rendering using quad views instead, with potentially a greater performance bump for you. Just install the Quad-Views-Foveated API layer, and then tick the "Quad Views" box in DCS under the VR tab. You can disable the OpenXR Toolkit as it will no longer be needed.