sleighzy

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.

The QuadViews companion app only works with the Quad-Views-Foveated API layer, so make sure you have that installed. https://github.com/mbucchia/Quad-Views-Foveated Make sure you tick the “Quad Views” box in the DCS in game VR settings as well.

This is using your integrated graphics, and not your actual dedicated GPU. Is the headset plugged into the right thing? Can you disable your integrated graphics so that it will only use your normal GPU.

Is this a "vanilla" DCS VR setup (which means possibly a Vive Pro 2 which I'm not familiar with), or have you installed other tools like Quad-Views-Foveated or the OpenXR Toolkit?

I'm assuming you run DCS from your Steam library, correct me if you are using another shortcut (in which case look for the properties on that shortcut). Check your Steam library for DCS and the program arguments. - Right click on DCS World within your Steam Library - Select Properties - Click on "Set Launch Options" - Remove the parameters above

Based on feedback in the bug report for this on the DCS Discord the following steps seem to make these work. These are done in VR and the settings modified within the VR screen in the in game config, not the new launcher. 1. Update the controller settings (don’t change anything else) to something you don’t want, save and then restart the game 2. Next update the controllers back to the setting you want, don’t make changes to anything else, save and restart the game. It has been mentioned that in some cases these settings will be lost if you make and save changes later, to be confirmed but I’m sure you’ll find out. For reference go to the DCS Discord https://discord.gg/eagledynamics and it’s this issue https://discord.com/channels/542985647502393346/1291225941246476308

I recant my statement after further recent retesting. I get the normal black background and picture of the aircraft that is going to be flown, in an instant action mission, the loading bar at the bottom is displayed...but does not display any progress.

1. Drop a DCS log file here from when this problem occurs, need more information. Can be found in "C:\Users\username\Saved Games\DCS\Logs", will be either "dcs.log" or a text document named "dcs" in your Windows is hiding file extensions. 2. Some multiplayer servers use scripts, you may not be able to load these replays as you don't have the scripts on your local machine.

I couldn't locate what I was looking for on this topic, but you could try raising this in the OpenKneeboard Discord channel.

@michael1982, I don't know if it was you that posted in the OpenKneeboard Discord help channel yesterday (?), but this was the response from Fred on this topic. I've seen a similar response elsewhere but wasn't able to locate it: Try turning off header/footer in advanced settings, not just in the individual VR view settings If that fixes it, same problem as https://github.com/OpenKneeboard/OpenKneeboard/issues/658 If it’s actually specific to VD passthrough, and isn’t fixed by that, then yeah you need VD support

Couple of things of note (although may not resolve this issue) based on that log: 1. You can remove those "--force_enable_VR --force_steam_VR" parameters as they are redundant, and cause warnings in the logs as you aren't using Steam for your OpenXR runtime. 2. Disable "Hot plug" in the controls settings in DCS. This can cause stutters as DCS will be constantly scanning for new USB devices being connected. If you do add another device you can just click the "Scan devices" button in the controls settings to have it picked up 3. You have Tacview installed. I see some long load times around this area (although can't confirm if directly related to Tacview). Remove this for now, it can cause performance issues, you can retest with this off and we can revisit it later as there is a setting that could help if you have to use Tacview. Whilst these may not be directly the cause of the long loading times, you can at attend to those items to at least rule them out....and may help with stutters and other general game performance. The log analyzer also notes the following: * Disable civil traffic * If you have FPS issues, trying turning off Vsync in the graphics settings

Attach your DCS log file for folk to see if anything jumps out. Will be “C:\Users\username\Saved Games\DCS\Logs\dcs.log” or a text document named just “dcs” in the folder if your Windows is hiding file extensions. Take the log after loading the Syria map.

@cobrabase, Which of those drives is DCS installed on? Hopefully not a HDD and is on an SSD.... You can drop your DCS log file here instead if you like.

Yeah that's definitely worth investigating

Which of those drives is DCS installed on? Hopefully not a HDD and is on an SSD.... If I'm reading this correct you also only have 16Gb of RAM. Upgrade to at least 32Gb of RAM. As a bandaid fix for this you can make sure that your Windows page file is on your fastest SSD (preferably NVMe) with at least 10% space left after adding the page file. Set your initial and max values to 32768 for the custom page file, click set, apply, and restart your machine. See the attached screenshot for an example. You can also drop your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file (if Windows is hiding file extensions then this will just be a text document named "dcs") into the #dcs-log-analyzer channel into the official DCS Discord server which will also provide more feedback around tuning advice for your system. https://discord.gg/dR7U7ZgM