VR Flight Guy in PJ Pants

Humm, I dunno if these have been reported before. If so, I will edit them. 1. In flight, with the HOTAS in game matching the actual HOTAS, the flap is down in various degrees randomly even though no axis is mapped with the flaps 2. The wheels now seem to be skidding a bit too much 3. It does not go automatically into AA mode, but some time it does 4. In PAL, the radar cursor cue does not move, but some time it does.

Noted with thanks.

should be F-22A/FM/F-22A/config.lua (?) and the and this line should be F22A (?) If I follow the changes, it did not work at all as I cannot jump into the aircraft. Update: change the config.lua and retain the entry.lua with F-22A, it works and the pitch seems more responsive as if it were normal. However, the trim was still a bit rough.

Three cheers! Hip, hip, hurray!

Here here. Also nose trim up and down. So far, any F-22 specific key and axis bindings do show some sort of issues.

Same here, watch my stupid video above. BTW, as a lazy noob, is there any combined fix available? Not that the @SkateZilla one was not good enough.

Thank goodness, finally some good news. I cannot speak for others, even though I have paid, if there would be a need to pay again just in case, here take my Sterling.

Oh no...

Found out why. The HMD vanishes whenever I sequeeze the trigger and somehow I map the RECCE to button 1 which was pressed whenever I fire, which is button 6 on my TM HOTAS. Case closed for me.

I think F22 use its own pitch mapping. And the nose trimming up and down, are also specialised in the key bing. I find them very sluggish too and the controller indicator does not move accordingly.

The changes work! Thanks @SkateZilla. Video in works processing at the time of typing.

Uploading as I type. Good night!

I try hitting "toggle goggle" but it does nothing. I find that some time, it just vanishes even I did nothing. It is random. Some time after a while, it reappears and I did, again nothing.

I have only question: when?

Some super low quality, unprocessed TTL images here. Oculus OpenXR, setting as per in video above. May try again when the room gets darker Dim off: Dim on:

Agree on the above, plus, by going back to 72Hz, it generates much less ghosting problem on my end, especially when QVFR is involved. I used to use 90Hz too much

Only manage to capture the the LCD screen on F/A-18C cockpit, not much difference. Will try your idea.

Thanks for pointing out. Okay. I tried a bigger tag, and I also need to turn off the pesky pass-through mode. It seems to work but I am not sure it worth doing it now as first, the FoV is very small and the video tends to be shaky. I tend to be a bit more argumentative here. I dunno a setting there means it actually worked. If it worked, great, but it would not be as good as what VD is doing. For example, when loading a mission, after pressing the start button, the screen goes black in VR (which has never been fixed since the introduction of MT!), there is usually a white dot at the bottom right. In OCXR, the dot is bright like Sirus, but in VD, it is not so, even if gamma in VD is set to 1.00 I think this is the time when I take TTL pictures instead.

Partly, but if I am informed correctly, Quest Link has no local dimming. The problem is, I tried to put on some blue tag thingy between the lenses and it did not work...

Good point. I am not sure if VD and/or OBS have messed with the colour space, it is rather apparent that VD had more of a yellow hue, or less blue (see the HUD). Also, the contrast and saturation were more "pleasing" in VD, as if Reshade has been applied (cough). Thus, the details in the shadow area were also a bit more -- detailed. I would admit that the scenario here was a bit too gloomy. I would try to use a flight in darkness to see if I can show any differences. And "through the lens" idea is great. I still has yet to manage to get the QPro running without it on my face.

New video, a rework of the original:

I have a bit -ve view on DLSS since it makes the office less sharp (see I am a kind person), also ghosting and images trail. I use MSAA in actual play but DLSS for benchmarks, so compensate performance issues

May be it was me! I have enabled local dimming (LD) in the headset, I can only find this in the non-Link, experimental features section. If what I got was correct, this has no effect in PCVR, and my video may prove that. I checked the PC Oculus application (or Meta if one prefers), I have Developer mode turned on, but, iirc, there was no LD option there. Please kindly let us know where to turn on LD for PCVR under Airlink/Link. (And below is about QVFR) I find the “sharpening” setting in VD may have something to do with the lack of distinction between “sweet spot” and what not. My video was in 0.5 so the “sweet spot” was quite blurry, the HUD reading demonstrated this issue as blurry + blurry = blurry. I changed the sharpening to full, and the distinction was clearer, no pun intended. But I still has to look for it. i think I better remake the comparison video, probably into 2, one for LD without any QVFR and the other is for QVFR only. The current one is not very up-to-date.

No hard feeling actually. Just clarification It does make a difference. When the “loading” screen goes all black, it is very noticeable here the cursor is not bright like Sirus. And the contrast in low light situation is much higher, in the headset.

It is from the gorram developer! Talk to the guy, not me. Thanks.