I can’t set my boundary with my device owner account.
This may be the worst bug i’ve encountered on this headset and is the sole reason why the meta quest 3 is the buggiest headset ive ever used. So I have two accounts on my quest, the device owner and an additional one. On the additional one, I can set my room scale or stationary boundary, as well as my floor level. But on the device owner, when i click boundary and click either option, it just doesn’t work and takes me back to the settings. This makes that account almost unusable in standalone mode, because as you all know, you kind of need a floor level to play vr. Please fix this meta, it’s been broken for almost a year now.
Won’t let me set up boundary, won’t let me go to passthrough
This happened out of nowhere, I suddenly couldn’t get to set up my boundary and that stops me from playing my games and even straight up removes it from my library and only shows me apps that can be played without a boundary. I keep clicking to set up a room scale boundary and literally nothing happens, doesn’t even go to the passthrough. I tried rebooting multiple times but it didn’t change anything. And for some weird reason when I take my head off my headset it goes black even when it’s on. My controllers act like there’s a boundary set up but i can’t even play my games without it crashing the apps because I don’t have a boundary set up… which is not letting me do. Can someone help? I’m starting to think my oculus is a lost cause.UE5.3: Roomscale and stationary boundaries break my Player Start! Why?
Hello, I'm having some strange problems. While I try out my test level with the Meta Quest at my workplace and in the Unreal Engine, everything works fine. Now I have created an APK file and installed it on the quest and have the following problem (see also the picture): 1. in the editor "PlayerStart" is at the position and rotation as shown in the picture (see number 1 in the picture). This also works when I test it in the engine and with Meta Quest. 2. However, if I start the level natively on the quest (at a different place in my room), then I start somewhere else in the level and not at the set "PlayerStart" (see number 2 in the picture). And my triggers etc. no longer work. If I reset the position ingame (via menu button), then the player jumps back to the spawnpoint set in the editor (see number 3 in the picture), but the triggers etc. do not work either. If I start the "game" on my workplace, then the spawn position is correct and everything else also works. The spawn point should always be the same, no matter where I start the game from. I don't know why this won't work. New Update: I have found that when I have a stationary boundary (3x3 feet), it works as it should. But as soon as I set Roomscale (or when I am standing), I have the behavior as described above. I'm trying to create a game like "Moss", for example. I have a stationary VR character (first person) where I can interact with my hands and at the same time I control a 3rd person character. And with triggers etc. I then "teleport" the VR character to a different position. This works, but not as soon as I stand or activate Roomscale. And if I'm not in the center of the stationary boundary, then the rotation and position where I "teleport" the VR character is no longer correct. Does anyone have any idea?
VR in moving vehicle Rendering issue
I am working on a project which involves using meta quest 3 in Rift mode while inside a moving vehicle. We are attempting to display lidar information as a customer demo and visualization tool. We have run into the usual suspects while doing this (e.g. motion of vehicle is seen as player movement.) In an attempt to temporarily solve for these issues we have disable the safety boundary and limited tracking to just rotation. This handles most of the issues at least for a temporary internal demo. The issue I'm here for is that with this setup if we move/drive more than roughly 100 ft the rendering in the headset for lack of a better word breaks. The simulation/Unity is still running fine but the visual information is torn and frozen. If in this situation we stop the vehicle and recenter the view the rendering returns to normal and we can move another 100ft before it happens again. Has anyone had this result in another other situations? Is the distance thing a floating point issue? What can we do other than recent the view every few seconds automatically. This is not a solution we want to use. FYI. We are going to eventually attempt to use the IMU data of the vehicle and blend that data with the headset tracking but we are not their just yet and want to show something in the mean time.
