dutchili

see 2nd post. There might also be a left to right difference which you can update from the Windows Application.

@BIGNEWY: the Viper manual on the website is still the december 2024 version: https://www.digitalcombatsimulator.com/en/downloads/documentation/filter/aircraft-is-f-16c/apply/

Can't ED implement some kind of 'vr-sync' so we don't have to fool around with settings so much and hope Windows does not assign something else to a 'render core' causing 1 frame 'off'?

well, that could be right as i am heaving DCS crashes where the dcs.log and eventviewer point towards my GPU. Still investigating this with ED. I also read somewhere that the earphones are clipping, setting the volume in windows lower, and higher on the headset could work. Haven't tested it yet.

no voice attack in my case. Also not related to SRS

Nope, the amount of click seems somewhat related to whether the pimax is the default audio device. But I don't have hard evidence. I haven't contacted pimax. Did you?

yes, same here

I think this has to do with how the game engine works. There must be some 'additional processing' that is too much for the CPU to handle.

I tried increasing and decreasing the boost clock with Intel XTU on a i9 13900KF to solve crashes with Pimax OpenXR (Crystal light) and a 4090. Like @shades71 I've noticed that lowering the boost clock actually improves performance. I ended up switching to SteamVR as it doesn't crash (so far) and currently has better performance that Pimax OpenXR. To respond to the core topic: still ground stutters, especially when 'changing direction', such as turning left/right while taxiing, rolling, pulling G below 6000ft AGL.

Things seem better with NVidia driver 576.66 (no need to blame mod's that are known good)

I experience the same thing with Nvidia 576.52. After the latest DCS patch...it's a matter of time, you just don't know how much time. No crash in DCS log, app hangs. When the app is windowed (while playing VR), i can usually sit it out and get control over windows in a few minutes. In full screen mode....automatic reboot (no BSOD).

no stutters, but crashes that are not mentioned in the dcs.log. Here is an example. After about 20 minutes of flying, the video froze, sound continued for a minute, then a full system reboot. Not an incident. dcs.log DxDiag.txt

Major component: SRS for radio communications in Multi-Player. Major component: Tacview for debriefing in both MP and SP Major component: LotATC for air traffic control in MP My discord uses several mods to enhance the visual experience at airfields and target area's.

I bought a Pixel Crystal Light... - i love the resolution, close to 2D experience - switching between game and 'desktop' is instant - sound of non-DMAS speakers is....better buy the DMAS speakers too - tracking is not as good as the quest. I have issues when looking at my F-16 wingtips. Could be due to my background. Besides this position, it is perfect and better 'smoothened' than the quest, which you will notice when aligning the JHMCS in the Viper. - quality upon delivery was not perfect. Had to correct contrast and brightness of the individual panels, throught the normal software, to balance left and right. One dead pixel in the right panel, no response from customer service on these issues for 3 workdays and a weekend. - setup was 'click and play' instead of those Quest 3 unwanted intro's and safety wizards. - wearing comfort is much better than the Quest 3. It is heavier, but feels lighter. - i get the best performance at 72Hz, quadviews FOV rendering, high(est) resolution. Low-level FPS depends on the map and visible distance setting, FL006+ is steady 72 Hz (and perceived as fluent). The 90Hz setting only works for me with Pimax upscaling enabled, but that comes at the cost of less crispy views. - the asferical lenses have a sweet spot. The pancakes from the quest have better 'edge to exge' sharpness. It took some time to learn to turn my head more, than just the eyes. Ther is also more chromatic abberation, comparable to a quest 2. Primarily visible with high contrast and red colors. Summary: not going back to the Quest 3.

@BIGNEWYThis thread can be closed. The root cause was incompatibility between the Nvidia driver (regardless the version) and Windows 11 core isolation.