diamond26

I guess each country has its own standards on this one. In my experience we used to change barometric altitude at 10000ft.

Usually above a certain altitude ( in real life 10000ft or 18000ft, I’ve seen both depending the area) you reset barometric pressure to 2992 (1013) so all planes have same reference. Upon return to airbase you receive new barometric from ATC. I had the TK PRES LO indication last time I flew and forgot to put 2992 back. ( I had 3031 at the time)

My response was related to what @edmusssaid about PD and in that case we are talking about DCS PD.

When someone mentioned PD 1.0 in this context is talking about DCS PD not Oculus or Super sampling

I wondered why some people get this problem and others not. I for example don't have this issue with my Quest2

as long a track is available that shows acquisition in a significantly less distance than 40nm, I guess it can classified as a bug. At least in that case we may take an answer why its worst than it was before.

Yes I had a similar detection range, max 25nm

@wheelieGood tip to play with Appearance tab. I used your saturation settings in a Quest2 and yes I saw a nice difference in colors (more vivid). I don’t use anything else from OpenXR toolkit

0.6.3 Works fine with my quest 2 and I have the feeling that the picture is crispier (Don’t know if there is any additional sharpening in OpenXR). This is without Openxr toolkit and using only Quest 2 sharpening option

My statement on the OpenXR/Open Composite discord

The simple answer is Yes it works with Quest2. Follow the instructions mentioned here: (I didn't have any distortion) For the performance issues follow the PC hygiene steps mentioned in the second link

I'm testing Quest 2 and OpenXR and so far I can say it works. It produces a smoother feeling and gives better clarity as I can use full resolution without the need of upscaling technics. Bare in mind my system is a gaming laptop with i7 9750 32 gb RAM and RTX2060. I saw above an option in toolkit "Lock motion reprojection" Is that only visible to G2 users? Cause I don't see it in mine

I’m on testing too to see the benefits. I just wanted to make sure I followed the right steps. I need to test one after the other previous configurations and OpenXR as the FPS count is not the perfect measure for this from what I read. Not sure yet I need to use the OpenXR toolkit

OK, this is what I did. So from the 3 requirements mentioned in OP first post only the first is required to make it work. Then Skatezilla’s app and api set to SteamVR

@zombiesyardI wonder how you did it. Did you use WMR with Oculus ? I had used opencomposite in the past to bypass SteamVR and use the then compatible Reshade, but WMR is not of use with Quest2

I can confirm, unfortunately, that one of the JHMCS benefits is not working as described. There is no way lately to get a lock with LHACQ beyond 25nm

Seems it’s working for me.

Very happy so far with the performance benefits from vrperfkit!

+1

I had a similar picture with Ready on how the shader mod behaves under 2.7.11. Performance wise seems same or little worst with the updated shader but the feeling was better with it (headset is Quest2)

Good one not only about F-4

Done!

I would suggest starting with the high preset setting offered from the game and adjust step by step from there

Just follow what it says at the point I share (Button V) It’s dead simple!

I just want to reiterate what @Hoirtel said about DCS PD set to 1.0 and mainly use Oculus resolution. Anything else does more damage than good.