Quest 3 Walls or furniture saved as space settings are not visible on screen after PTC V64

[BMO382]

hello.

I have a Quest 3 and this is my first PTC update. However, I am having a problem with 'Space Settings'. I never had this problem before the PTC update.

Scanning my room, adding furniture, and adding walls or windows works fine. It was also possible to name rooms, edit rooms, and modify furniture as normal.

However, the space and furniture set up this way are not displayed on my screen in the virtual environment. Previously, when I brought the controller or Quest 3 near a wall or furniture I had set up, it would appear blue, but now nothing is visible.

The problem is that the spatial data saved in the spatial settings remains. I repeatedly deleted and recreated this space, but it did not solve the problem of not being able to see it in the virtual environment.

Borders are saved normally and are visible. The option to change the color also works fine. However, only the border is visible, and no walls or furniture are still visible.

This feature was one of the most important safety nets to avoid getting hurt in the VR environment of my room. As I moved, I could see the blue output of furniture or walls and reset the distance or move in a direction that wouldn't hurt me.

I tried everything I could to solve this problem. I repeated clearing the space and rescanning dozens of times, resetting once through the phone app, and once through the device's power options, but it did not solve the problem. I still can't see any furniture or walls and this doesn't change whether I'm in a virtual or passthrough environment. The space is saved, the furniture and wall settings are also saved, but I don't know why they don't show up on my screen.

My request for help was written through a translator, so the terminology may be slightly different and I need your understanding. I hope the meaning was conveyed correctly, and I hope this problem is fixed quickly. Now that I can't see the walls and furniture, I'm scared to swing my arms or move my body while wearing VR. This is especially true because I have been bumped into and injured a lot even in environments where walls and furniture are visible.

[kevino333tf]

I'm having the same problem since v64 too, now I'm in v67 PTC, yesterday tried a factory reset and didn't fix the issue. I also sent a bug report from the headset.

[DGB10]

Same issue here. Thinking it would get fixed months ago, sent multiple bug reports and started a support case back then. Shame to see it still persist all the way up to V66.

[Beau69]

Let’s face it guys, Meta doesn’t give a crap and it’s not going to be fixed. Period, case closed. 

[TheLegend27]

Following up from my last reply, the team still seems to be investigating, but have no updates on their end to share for the moment. They're asking those still running into issues on the newest release to please submit more bug reports for engineering to review. When submitting the bug report, please tag it with the following string: 1175432. For those who have already submitted bug reports on the latest release, thank you for your diligence!

Thank you again for your patience, and I'll be sure to check back in once I have an update.

[lordnozgot]

Today my friend bought himself a Quest 3... And you know what?) He has a problem right out of the box))) So even buying a new one won’t help you)))

[Novizokk]

NO! Let me speak for everyone Here.... Can you please provide evidence, that this Feature is present AT ALL in ANY Headset? From Reading the thread over and over again... Its reasonable to assume that the Feature we want to use IS actually scrapped... Which is "fine" If you f**ing comunicate that! My theory is, that this Feature is Not percise enough for the General Public, e.g. it May Show your cupboard Like 3 centimeters of, and If people rely on it, they May Hurt themselves, and giving the fault to Meta because they dont understand the technology. Possibly spawning lawsuits... I See that, and i would be cool With hat.... But f...ing please.....!!! Comunicate that! I really want that Feature and i will never sue the company for that. I know about the limitations of this technology and am fine With it. But jea, if you scraped the Feature, Just Tell US and Close the Ticket, everyone "wins"

[Beau69]

I think we need to all face the reality that Meta just doesn’t care about its customers. They are too busy rolling out “New“ features that will either be broken or removed with future updates. I will never buy another Meta product. I’ve had every generation of the quest since before they were bought out by Zuckerberg. They were much better company back then. I’m done. 

[Hirothefox]

Popping back in to mention that as of V68, the issue is still. Not. Fixed.

This is getting completely ridiculous, what is taking so long here? I'm extremely frustrated and disappointed, having a safety feature I relied upon taken away from me and nothing to show for it all this time later. It is crystal clear to me that this is not tasked, not roadmapped, nothing. Was the removal intentional? What's going on?

I want SOME amount of communication from someone who would actually be responsible for addressing this problem. If it was an intentional removal, say so, if it's being fixed, say so, commit to saying SOMETHING so I can decide whether I can continue using Meta's products, or move on from them. 

Thanks.

[Hirothefox]

Reminder: the problem at hand is literally a button not being present after an update. The functionality still exists, furniture and objects show just fine in the process of setting up a room, but once you finish doing so... there's no practical way to actually use what you set up.

This button, This one. Right here. It was present, and now it isn't. It should not take LITERAL MONTHS to figure out why.

[knowledge.pachi]

This is murder, Meta should go to hell