slughead

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

Take a look at Fred's signature just above your comment.

Nothing more than you have now. That's useful information for this issue though thanks. FYI, HTCC can be used without pointctrl using finger-touching gestures. It takes some getting used to and I expect pointctrl works better for the mouse clicking. I'm still waiting for my pointctrl.... 14 months so far.

That's Fred's Hand Tracking Cockpit Clicking app to give Quest Pro (and other headsets) cockpit clicking in DCS. I guess you don't have this installed? Home | HTCC (fredemmott.com)

Thanks very much for your advice. I will test with the guardian on and off and get you the logs if it is still not working with the guardian back on. It's about 0920 here so may not be able to do it for 6 hours or so.

Thanks for the input. I'm not convinced that it might be a DCS bug. I haven't had this before installing meta-foveated and have been running with HTCC since April. I was just looking into why the Quest may drop down to 3DOF and I have seen a webpage that states turning off the guardian will cause this. So I shall test for that later as I turned off the guardian for Quest Link a few weeks ago. Although it seems odd that 6DOF works fine to start with and drops to 3DOF at some stage of the flight. I'll keep on trying to get to the root cause of the issue by peeling back the layers of the onion.

Ok. I have only had this since using meta-foveated. Could you try without meta-foveated and see if the problem doesn't occur? If we can isolate the problem, we can then ask the right people/person to investigate. Thanks.

Are you using HTCC too? If so, try removing either HTCC or meta-foveated and see if that solves it please. I think there may be a conflict with both running.

I got my answer… the CPU/GPU performance improvements in v55 will be of zero benefit to us.

Is anyone experiencing loss of hand and head tracking (side to side, forward/backward, up/down - not rotation) whilst using this app on Quest Pro along with HTCC? The mission starts ok and not too long into it the fault occurs. If I remove either app, I don't have the problem. Reinstall and it is back.

Here is an example of an F-16 wingman not aerobraking on landing and slamming on the brakes. The wingman is on the right. wingman_not_aero_braking_on_landing.trk

And here is a track with a wingman crashing into the hillside. wingman_crashed.trk

I'm still testing this on the QP. The performance gains are terrific, for sure. I recognise that there is a compromise for these performance gains. However, I notice whilst looking about that for areas such as forests, when you look away then back again, the colour or perhaps it is the contrast changes. I find it very noticeable. Is there a tweak that can be made to lessen this effect or remove it altogether without obviously just turning off this great piece of work? I have played with the available configuration options, although they haven't helped with this issue.

It's good that they have modularised it. For me, a VR pilot, the control panel would be wasted. So having the opportunity to purchase just the TQS is great. I currently have two Thrustmaster Cougar TQS that I have modified with hall sensors / contactless potentiometers and installed low friction tape that makes it glide without sticking but I yearn for the detent lever. So I expect I will purchase this from Thrustmaster. I will probably buy the whole kit anyway. I heard elsewhere that pre-orders would be in late July with shipping in August. But hey, it's coming sooner or later.

The only way to force it is to join the PTC. Then you run the risk of getting an older beta version of v55 and have a much worse experience. Without using the PTC, you just have to wait. Could be days or a month.

What I can confirm is that setting the encoder rate to 960mbps makes it worse!