slughead

The lenses. Local dimming was available in v54. The light bleed isn't improved by local dimming. This is something more widescale. Similar to the background light bleed of a television screen. As others have also described... a haze.

Although the Quest Pro is awful in night missions. So much light bleed.

It seems to be a lot of conjecture to me. People love to make exaggerated headlines and love a bit of bashing (otherwise known as being negative for the sake of it) when the reality of the facts appears much more sublime. So Meta has said to their suppliers to hold on ordering parts, please. Sales are slow, we don't want to have to pay for and store a whole load of stock (so they can maximise their profit for the accounts - shareholders). So let's put the brakes on, as there's a cost of living crisis going on and folk are holding on to their cash, let our stock level come down and then rethink in the next quarter or half year. It's all about end-of-year profit. It's called business. I notice that the "report" (lol), has already posted an editorial update.... null

With the Quest Pro you have hand tracking and can control the cockpit instruments that way. Pinch with first finger and thumb for mouse click, second finger and thumb for other mouse click. Pinch and raise or lower your hand to turn dials.

You'd need to ask the manufacturer.

Price? Location?

As I said... "turn off the headset when you're done with it".

I have had problems with tracking and dropping down to 3DOF with the guardian disabled. Have you experienced this?

The Oculus Developer Tool has a "Bypass Proximity Sensor" option. This may work. What will work 100% is some tape over the sensor just between the lenses. Just remember to turn off your headset when you're done with it.

No.

I'm still having issues. So far not dropped to 3DOF but goes black screen with a warning message that tracking is lost. I think this is a headset bug. I have performed a factory reset and as part of that the guardian is recreated. Will monitor.

Yes. I have been getting this too. Is your guardian enabled and have you cleaned your headset lenses?

I bought the Globular Cluster comfort kit. The pads are larger and softer. A huge upgrade in comfort over the stock pads.

La la la la la... I can't hear you...

Yes.

Don't mix and match PD / render resolutions in the two apps (Oculus app and ODT/OTT). Just pick one for sanity's sake. And if you want better frame rates/more headroom to stay out of ASW, drop the render resolution down to say 1.3x. Mine is set to 1.2x (4864 x 2448).

It's really down to personal preference. I run at 72Hz with the bells and whistles on with occasional drops to 36Hz/ASW.

If folks are not using the F-15 module why not downgrade to the previous open beta until a fix is released?

Instead of hitting keypad 5 or mapping it to a button on a HOTAS, I use a USB footswitch commonly available from Amazon. Actually, I use a triple USB footswitch. One for re-centre, another to enable/disable night vision on the open kneeboard and a third to show/hide the kneeboards.

I concur. No need to overclock the 4090.

@markturner1960 have you set the target frame rate to 90? This is just under the setting for FPS/Developer/Advanced.

Sounds like he means the OpenXR Toolkit.

This isn't really the thread to discuss support for HTCC. I recommend either starting a new thread about it or seek help on Fred's discord server.

It looks like that was it. Two flights in now and the problem has not returned. I guess I'll just have to live with the guardian on despite the headset not being supposed to drop to 3DOF in developer mode with it disabled. But hey, it's developer mode. Thanks to @actually_fredand @mbucchiafor their time.

Here is another example of AI logic gone wrong. This time the wingman has called bingo and a few seconds later ejects. Plenty of altitude, no enemy, and no damage. Just decides he wants some fresh air. ai wingman bingo then ejected.trk https://youtu.be/NZKGrSg5Ft8