Sile

In my case, despite a frametime way below the required frametime for my VR headset (72 Hz) the terrain stuttered with the MT Client and the Oculus OpenXR Runtime.. Also with lowest possible Settings and Resolution (ST Client OR OXR toolkit turbo mode OR SteamVR OpenXR Runtime -> no stuttering). So I suspect the MT client to have some problem with the correct timing of the rendering of the terrain/outside of the cockpit. Also visible in 2D when looking at plane contacts. There is also a thread about terrain stuttering in the MT Client Bug Section.

Try to select a "Preferred Somnium VR1 Variant" before clicking "Confirm my Email" button. You can find the 4 possible variants below the "Confirm My Email" button. For me it only worked after selecting one. Without selection nothing happened.

thanks, fixed

Please don‘t derail this topic. This is not the right place for a PSU discussion.

https://www.digitalcombatsimulator.com/upload/iblock/f4b/kx2ch5ix0ilve964dr5u1xbik4u2ekvn/DCS_F-15E_Manual.pdf TFR - Chapter 8.20 - Page 271

AFAICT OpenXR Toolkit has an option to limit FPS. And Rivatuner might work as well. At least it worked for me some months ago when i still had a G2.

Yes, just wanted to post this. Wouldn't say the airports have been swapped. But the Tacan Channels and the ILS Freuqencies are, see attatched kneeboard.

I wish the topic wouldn‘t be marked as solved. Because obviously it isn‘t.

Get this error too. But every second or third DCS start works. (tested some VR settings) Out of 8 starts three were successful. So maybe those who say a restart works might just have been lucky… till the next DCS start.

I have never tried it, because i optimized everything to stay above 72 fps and have ASW disabled, but i remember there is a setting "Mobile ASW" which can be enabled/disabled with the Oculus Debug Tool. Maybe this changes the transition behaviour. And there are keyboard shortcuts for setting ASW ingame: ctrl-keypad1 ASW Disabled ctrl-keypad2 Force 45 fps no ASW ctrl-keypad3 Force 45 fps with ASW ctrl-keypad4 Enabled ASW auto (45 fps above is with 90 Hz headset refresh set. With the headset running at 72 Hz you get 36 fps with ASW.)

no mouse support in VR, see faq #2: https://openkneeboard.com/faq.html

Just start it from 2D Desktop with link already running.

Quad-Views-Foveated updated to 1.1.1 (Linked to instructions page as requested by author - goto "Download & installation").: https://github.com/mbucchia/Quad-Views-Foveated/wiki Changelog: Add support for HP Reverb G2 Omnicept, Pimax Crystal (via SteamVR OpenXR) and Varjo (via SteamVR OpenXR) through OpenXR-Eye-Trackers. Please install the OpenXR-Eye-Trackers separately. Add a configuration file option to un-advertise quad views support with certain apps (does not work with DCS). Update the installer to order XRNeckSafer and OpenXR-MotionCompensation properly.

Just for the case you have turned around the rear headrest of the pro, the charging contacts for the dock won't be properly aligned anymore and it won't charge. And there should be a bios setting for USB to still deliver power even if the pc is turned off. The exact location depends on the board manufacturer, though.

And developer mode isn‘t needed for „oculus debug tool“ to work. (maybe you were confused because another user called it „oculus developer tool“ some posts ago) The option „Bypass proximity sensor“ in the debug tool doesn‘t seem to work for the pro anyway, it seems.

You are correct on FFR and DFR. The poster @Bazz_Mulder above somehow confuses DFR (DYNAMIC Foveated Rendering) with FFR (Fixed Foveated Rendering). Quad Views is the technique that mbucchia uses to implement DFR for DCS and it only works with OpenXR. Installing OpenXR Toolkit is optional and it should be installed before "Quad-Views-Foveated". Some Settings (e.g. Foveated Rendering like posted above by Bazz_Mulder) are incompatible with Quad Views and should be avoided in OpenXR Toolkit. See Wiki: https://github.com/mbucchia/Quad-Views-Foveated/wiki Your Oculus headset runtime will still use ASW even when running with OpenXR API.

Same here with Quest Pro in OpenXR with Dynamic Foveated Rendering. The pixelated frame is one thing. But the NVG circle moving with the eye instead of the head is very irritating. It would be great if ED would please look into this.

@BIGNEWY @mbucchia On the topic of the NVG bug with Quad Views DFR - NVG gets a pixelated mask moving with the eyes: I would like to link the following topic from the VR Bugs section here in an attempt to bring it to the mods attention. I think this affects all headsets that use Quad Views DFR.

Official cable here. My headset slowly discharges to 80% and stays there on proper USB Port. 5 hours is the max time I tested. Didn‘t drop below 79%. Maybe check your mainboard manuals for port specs (max wattage or current) and connect accordingly.

Hast Du evtl. die Encode Resolution Width, z.b. mittels Oculus Debug Tool oder Oculus Tray Tool geändert? Bei zu hohem Wert hatte ich diesen Effekt. Evtl. mal kontrollieren und zum Testen auf max. 3.600 (irgendwo mal empfohlen für QPro) oder 0 (default) stellen.

@hsthMaybe worth to try with the current Version 2.0.0.36.

@nikoel thanks, found it! But good news. Have just been testing the latest experimental build from @mbucchia and had no (turbo mode on) crashes when taking off the headset in a 15 min test session. Took it off multiple times for 10 to 30s.

Last time i tried it did nothing for me. Thinking of taping it: I can't even find that sensor. In pictures of the Quest 2 it is clearly visible. Does it work differently for the pro ...? And is that feature only for other models?

No. It does not mess with the game, because the dcs_variant.txt points your game to the renamed saved games folder. And if it should go wrong, delete the dcs_variant.txt and reset the saved games DCS name. That said, a backup is always nice to have. SRS was no problem. Simshaker was no problem. (Tacview wasn't installed at that point.) In Openkneeboard i had to reset the path in OKB. But hey. Just trying to help.