cancel
Showing results for 
Search instead for 
Did you mean: 

PTC - V66 Quest 3 problems with room setup, alignment and orientation

Michaelpro
Explorer

Ever since my headset has updated to v66 I have noticed the following new problem

Hardware: Quest 3 with pro controllers.

 

Problem 1

However many times I setup me room I'm always 1 foot off the ground.

No matter how many times I set it up I'm always floating.

Problem 2

Menus out of aliment/on an angle.

Holding down the menu button to Re-align the system helps but only sometimes.

Most of the time the menu will angle to the other side..

Problem 3

What's being displayed in the headset starts to lose orientation

For example. being in my home space in my headset.

If I turn my head the scenery will start to rise up like I'm sinking.

 

I also have the Known problem with the proximity sensor.

On v65 I never had any of these problems and the has made the headset unusable.

1 ACCEPTED SOLUTION

Accepted Solutions

Well I have found the solation!

I would have appeared to have enabled Laydown mode in the advanced setting!
Turning that off has fixed all the problems apart from the proximity sensor problem.

However I would subject that they make that a button in the menu the same way that Travel mode has a button so its easier to get too and see that its enabled.

Thanks Mike

View solution in original post

6 REPLIES 6

TheAntiSocializer
Meta Quest Support
Meta Quest Support

[Not a Solution] - Simply marking for visibility, we do not have another way to pin

Hey @Michaelpro! Thanks so much for reaching out to flag this with us, I'd love to get this over to our internal team for them to review. To make sure they have all the right information, could you please provide the following:

  1. What's the full version number of your headset? (66.0.0.####### or likewise)
    • Quick Settings > System > Software Update
  2. What's the current firmware version of your controllers?
  3. What version is your Meta Quest app running?
    1. Menu > Scroll all the way down
  4. To confirm for our team, do you currently have Quest PTC enabled?
  5. What all have you attempted already?
  6. Any potential workarounds found?

As for the proximity sensor, could you elaborate a bit further on your issue? I haven't seen many people mention a proximity sensor issue but I'd be glad to have our team look into it if this also started with the v66 PTC. 

Thanks again!

Sometimes it's okay to be a little Bing Chilling

1. What's the full version number of your headset? (66.0.0.####### or likewise)

66.0.0.547.370.604713589

2. What's the current firmware version of your controllers?

1.39.2

3. What version is your Meta Quest app running?

268.0.0.10.109

4. To confirm for our team, do you currently have Quest PTC enabled?

I do

5. What all have you attempted already?

Multiple room setups and re-orientations by pressing the menu button

6. Any potential workarounds found?

None found, I have stopped using the headset due to this making me sick.

Oh man I don't know how I missed that, thanks for linking me to it and getting all the information over. I'll be passing it over for our team to review.

In the meantime, let's try and get a couple basics out of the way:

  1. Double check that 6DoF tracking is turned on in your settings
    •  Click on the clock on the left side of the universal menu
    • Select Settings
    • Select System from the Settings panel
    • Select Headset Tracking from the left side panel
    • Make sure Headset Tracking is ticked
  2. Clear your Guardian History
    • In the settings panel, select Boundary
    • Select 'Clear Boundary history'
    • Redraw your Guardian
  3. Reboot the headset by powering it off for roughly a minute then turning back on

I did also want to ask if you could try to see if the issues still happen outside of the PTC. You'd need to opt out and Factory reset for it to go back to v65. I understand this isn't an ideal testing method but it's the best one I can provide since I can't personally repro the issue myself.

For the proximity sensor issue, it does look like one of my buddies mentioned our team is currently working on a fix that should be available at the public release of 66, so for this thread we'll want to mainly focus on your alignment/orientation.

Sometimes it's okay to be a little Bing Chilling

Well I have found the solation!

I would have appeared to have enabled Laydown mode in the advanced setting!
Turning that off has fixed all the problems apart from the proximity sensor problem.

However I would subject that they make that a button in the menu the same way that Travel mode has a button so its easier to get too and see that its enabled.

Thanks Mike

Oh wow, I'm glad to see that you didn't have to factory reset the headset! I'll let our team know that disabling laying down mode seems to help out with your alignment/orientation issues. As for making a button that'd make it easier to know if its on, I'd definitely recommend posting that in our Ideas board. That's usually where our team will look for any hardware and/or software suggestions from the community that they'd want to bring to life in a future update.

If you run into any other issues, feel free to either update this one or create a new thread with the PTC v66 title and we'll jump in to check it out! (As I'm sure you're aware of haha.)

Sometimes it's okay to be a little Bing Chilling
Still need help?

Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.

If you need an agent to help with your Meta device, please contact our store support team here.

Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.

Check out some popular posts here:

Getting Help from the Meta Quest Community

Tips and Tricks: Charging your Meta Quest Headset

Tips and Tricks: Help with Pairing your Meta Quest

Trouble With Facebook/Instagram Accounts?