08-13-202302:33 PM - last edited on 10-12-202310:38 AM by BlueberrieSmoothie
I was watching the quest 3 announcement trailer and I've come to a realization that I really don't understand meta's design choices of the quest 3. They've removed the 2 upper cameras yet they haven't made the controllers track themselves. As a result I imagine there will be a huge deadzone over your head. And the AI IMU tracking Andrew Bosworth brought up will in no way be good enough to replace those cameras. Any ideas why they would do this?
The controllers are the only thing about the Quest 3 that I'm concerned about.
Yeah, all 4 tracking cameras are aiming at least partly downwards. Even if they had extreme FOV, there's going to be a larger deadzone over your head than with a Quest 2 (or definitely a Rift-S).
Maybe they've improved IMU tracking so much that it can handle deadzone tracking longer (currently maybe a second or two before drift).
Or they might be thinking: "we will focus on cameras intended for hand tracking. If players want better overhead tracking they can buy Pro controllers"
I found the Pro controllers reliable up until a recent update... they connect faster now but seem to be unsettled and reset position more than they used to. I preferred the slow connection time! That's with the Pro headset though, not the Quest 2.
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
So I am not the only one that is getting this on my Pro Controllers, I know the Quest 3 Controllers I think uses a form of AI to do the tracking when not in the view of the headset, but I had so much tracking issues on my Quest 2 where my controllers would float off into the distance until it saw it again. This was why I upgraded to Pro Controllers back then. Just don't turn off Wi-Fi on the headset, the Pro Controllers get worse where their offset is like 5 inches off and the headset thinks they are further outwards than what they really are due to I can see my hands. And when you turn the Wi-Fi back on they zoom back into the correct location within a few seconds.
Their big advantage for me is when modelling in VR, you can get them as close as you like to the headset with no issues whatsoever, much better. I guess if there's a game like Iron Man where you have your hands behind your back a lot, they're probably better there too. Otherwise, for most applications I kind of preferred the standard Q2 controllers.
I use the Quest 2 away from home so it's been a week since I used the Pro, will see if they've had an update and things have improved. I remember them being better initially so it seems to be a firmware issue.
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
In games where you use attachments that have the controller facing down, when holding the attachment down, is already an issue and this was less of an issue when there were halos on the controller. This is going to ruin a lot of games.
Well to be fair, a few miss hits could be down to bugs in Beat Saber, I have hit a note spot on and the game says it was the wrong saber, whereas the replay shows that I hit it with the right one and I have also seen it allow a hit with the wrong saber. But yeah it does look better with this headset.
