DerKlausi

Only when looking around inside the cockpit or outside as well? If the latter, do you have bloom and lens effects set to OFF?

Hi all, just updated to the latest DCS patch 2.9.12.5336 (after skipping one or two?) and recognized that the 'dreaded' QuadViews focus area rectangle, previously only appearing with lens effects or bloom activated, is now also visible when looking around in the cockpit. It turns out this bug is exclusively linked to SSAO being turned ON. This is with Pimax Crystal OG but has been reported by at least one more DCS user with Varjo XR4. Would be happy to see this getting fixed soon, as SSAO makes quite a difference for me in visual experience. Cheers, DK

Two questions: 1. What HMD are you using? 2. What is your VR view direction/position in the menu screen after launching DCS, but before centering VR view?

It is very likely that this is caused by your flight sim seated position/orientation not being the same as you used to set up your (Steam)VR environment (room setup). Also make sure that both when you launch DCS as well as launch & activate XRNS, you're seated wearing your HMD exactly (!) the way you will be later during flight. Means: same seated height, same lateral and longitudinal position on chair or rig, same default forward looking direction, same HMD pitch angle. For example, when I put my HMD on my rig's seat and launch DCS/XRNS, XRNS will be off in a way similar to yours. I have to wear it on my head sitting with the rig already in the neutral instead of parking position (motion rig). Good luck!

How did you guys mount the Ultraleap 2 to the Crystal? Are you using it together with the Lighthouse faceplate? Cheers, DK

Question to you TQS owners: does your throttle have significant backlash? When I set mine to a medium to high friction resistance, the throttle grip moves like 2..3mm with the whole rod & friction brake assembly inside the base, before the rod itself starts to move in and out of the friction brake. Are you observing the same? Or did I get a faulty unit? Cheers, r.

Hey man - thanks a lot for your tireless efforts to get this great mod up and running again! I'm looking forward to giving it a spin this weekend!

Did you check proper OpenXR layer order? I'm running XRNS fine with varjo-foveated, OXRMC and OpenKneeboard when XRNS is the first being loaded. That is - at top of the list using fredemmotts OpenXR-API-Layers-GUI.

Sounds like an issue I had a while ago - did you check my post on how I solved it?

+1

In many programming languages, ";" ends a code line and "//" indicates the beginning of a comment. So anything on the above line after the double slash is just for documentation. I did not find the time to try the mod though, but please feel free to report back if you were successful! DK;

Thanks for the insight - I'll give that a go!

Thanks, much appreciated - let's keep our fingers crossed! For the time being - do you know of any other way to reduce the haze? Cheers, DK

Thanks a lot - I had already tried querying LoGetMCPState() substates but unfortunately with limited success. In contrast to what I expected to happen after being hit by an AIM120, I found that with the Viper, only LeftAileronFailure and/or RightAileronFailure will ever trigger. Maybe you are able to enlighten me on why that is? Cheers, DK

Would be great for others if you let us know the 'how'!