Quest Pro Touch controllers occasionally losing position

[Hippo]

I recently tried using the Touch controllers instead of the mouse for pushing buttons, turning knobs, etc, in the F-18.  I am not using the Touch controllers for stick or throttle, as I am using a HOTAS.

I am very impressed with how well it all works, it is far superior to using the mouse, and congratulate the team on the implementation.  Unfortunately, occasionally one of the controllers, usually the right, loses posistion so that the virtual hand appears around 20cm from where it should be.  It eventually resyncs, but it's very frustrating when it happens.

Has anyone else experienced this and have any way to deal with it?  Can anyone confirm that they use a similar setup and never see this issue?

I am using a Quest Pro, with the Meta LInk software via cable, non-steam version of DCS, and QuadViews foveated.

Thanks.

[Maddaawg]

This is exactly what I have been going through with the Pro controllers, but not in DCS. The right controller especially will lose tracking and the Quest hand will be 6 inches away from the controller. I'll also get a warning in the messages panel that the right controller isn't tracking. Turning off virtual hand controllers decreased this issue but I think your wanting that enabled.

The other issue with the pro controllers is that they constantly shut down. This can happen in as little as 5 seconds of not moving them.

Mine were brand new inside of 30 days so they are on their way back to Meta via Amazon. My replacement set have not yet shutdown or lost tracking though I have not enabled the virtual hands again. 

Edited 22 hours ago by Maddaawg

[Porkbrain]

On 10/12/2025 at 9:30 AM, Hippo said:

Has anyone else experienced this and have any way to deal with it?  Can anyone confirm that they use a similar setup and never see this issue?

I have two Quest Pro's, both bought from new in 2023, and have the same issue with both that the controllers constantly lose tracking after not being used for a while.

For DCS I only use them to get past the connection from the Meta desktop to the PC, then start DCS from the desktop with the mouse. When I exit DCS I have to wave them about & press the trigger for about 5 seconds or so until they are correctly located by the headset so that I can point the 'laser' at the quit desktop option. A few times each week either the left or right controller will just shutdown and have to be restarted if I need to use it.

I do use them occasionally when using X-Plane 11 & 12 as there are some panels and menus, which don't respond to mouse clicks, that have to be clicked with the laser or menus activated by pressing the B or Y button and I always have to press the trigger or menu button repeatedly for up to 5 seconds before the laser beam, which always appears a few inches to the left of where it should be, finally tracks to the correct place.

I haven't found a way of preventing this happening, though keeping the the front of the headset and the controllers clean by wiping with a microfibre cloth does seem to help the initial tracking connection when first powering up the headsets it doesn't stop them failing to be tracked later on.

I connect one headset via Meta air link to a PC with helicopter controls & the other via Meta cable link to a PC with aircraft controls so don't think the connection method is a factor.

Both machines are running Steam and I don't used QuadViews or any other 3rd party software. 

[Hempstead]

I, on the other hand, from day one of release, have almost never lost track of position. At the beginning when it booted up Quest pro, it takes a bit to get the controllers to sync positions. But once they are in sync, I almost never lose position.

However, recently, Meta has gotten really really aggressive in "power saving" so if you idle the controller for like 3 seconds, it sleeps. It takes about a second to wake it up. And there is no option to adjust how aggressive Zuck is. No wonder he and Musk wanted to meet in a Vegas ring. *sigh*

What I would suggest is that since the pro controller runs SLAM using two cameras, you really want your env to be bright enough for it to work. They ain't IR cameras. For instance, if you have a pit or a desk... and your joystick/throttle is down below the desk top level... what the camera see could be darker than you are aware of.