slughead

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!

I had something similar happen to me too. The headset had an update pushed through to it and, for some reason, discharged itself even though it was on the dock. I can't remember how I fixed it. I may have disconnected the cable from the charging station and then connected it directly to the headset to charge it. Then I may have power-cycled it. That's all I can think of at the moment.

Exactly. I posed the question to the Meta team whether the performance increase is purely for standalone or would be of benefit to PCVR. No reply of course. It may well reduce battery performance so running over AirLink or Link (if port unable to supply enough power) may result in less flight time. I don't think the users will have the ability to de-clock the headset back to the clock speeds they are running at now. We shall see.

The first track is ready. This shows the AI pilot taxiing straight off the end of the runway into the sunset. You could also use it as an example of the AI pilot not holding the flare on touchdown to bleed speed yet being able to slow down rapidly. It wasn't my best landing either This was flown from the Caucus Takeoff mission. In the pictures below I have exited the runway onto the taxiway. The wingman decided to go for a stroll in the park. null null wing_man_taxi_off_end_of_runway.trk

I was getting that. I've not done a lot of testing though since turning Bloom Effect off to fully confirm that it worked or not. However, my one test after turning it off seemed to do the trick. I will play some more... itching to fly but have family stuff to do.

Have you forgotten to turn off Bloom Effect? It's on the VR settings page in DCS.

There has been one for a while...

It seems that turning off Bloom Effect has solved the darker rectangle. Thanks for poking me / giving me a slap

Bloom effect. Missed that one. I'll turn it off and retest.

Mine is configured as per the instructions. It has been that way for a long time before the tool was released. Yet I am seeing this darker rectangle. It isn't present all the time. There are scenes where you can't see it and others where you can. I will experiment and try to pinpoint a scene where it can be seen and if possible I will capture it. For the time being though, I'm just having fun with it. I've only had a couple of short flights so far and also want to demonstrate some absolutely bizarre AI pilot behaviour to ED. Lot's to do! And no, your performance is fubar. I have the same spec system 72Hz, 4x MSAA, 1.3x (ish) PD, all DCS settings maxed out and it's pretty darn good. Moreso with the ETFR. Have to admit that I notice the FR. I'll just have to get used to it. Sacrifices and compromises. It is what it is.

Yes, with lower numbers you should be seeing a smaller image and black borders. So it doesn't appear to be activated for you.

Or just have other business-driven priorities at this time. Let's face it, it's not something they're probably going to make a lot of money doing so they go for the best bang for the buck first. For us it is personal, for them, it's business. By the way, thanks @mbucchia I appreciate your efforts.