Blog Post
v2.3 after factory reset, Quest Pro
- the interface propose to scan my surrounding, while it's a Quest3 feature, the depth sensor is disabled on the QuestPro, I can't scan my furnitures
- huge stuttering that disappeared after some times (but at some point, the frame rate was below 20 fps)
- losing WiFi regularly for one second or more when using Steam Link
- Quest Pro controller is getting an offset every 30s that doesn't resolve itself (I have this issue since day one, on three different controllers so it's not hardware related) as before where I was putting the drifting controller in my back a few seconds to make the headset/controller line of sight occluded, then bringing the controller in front my face/the headset, it used to recalibrate after a few seconds. This issue makes the headset useless when randomly one of your controller is multiple meters away from your actual hand...
Note I tried to leave PTC, performed a factory reset : I haven't been rollback to 2.1, I'm stuck on 2.3...
Edit : After thousand hours of VR, it's just today I found a way to force the quest pro controller to reset its tracking : I bring the controller inside a pocket/below my t-shirt for a few seconds, then bring it in front of the headset -> it resets the tracking... At least I can use my Quest Pro without restarting my controller every few minutes
Edit2: Using Virtual Desktop, I don't experiment the Wifi/PC streaming connexion issues (losing stream for a few seconds from time to time) so it totally can be a Steam Link/SteamVR issue
Since PTC 2.3, my controllers have also been going offset more frequently than before. Similar to the message I'm replying to, previously the controllers would auto correct after a while, but now they just stay in their offset positions, making them unreliable and unfit for daily use.
I have to cover all 3 cameras with my fingers in order to force them to resync. But this is not a solution, considering it happens so frequently.
I think we should be able t rollback any update that changes controller tracking behavior, as it is a crucial part of how we as users interface with the device. I hope this gets resolved soon.