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?
Getting boundary points
I've been banging my head against Unity's TryGetBoundaryPoints and OVR's OVRManager.boundary.GetGeometry with zero luck. I've tried building directly to the Quest to bypass the issues I'm reading about with regard to the Link cable and this data but I'm still stumped. Any ideas on how to get the points of a user's boundary to work? Thanks!
Whitelisting for CONTEXTUAL_BOUNDARYLESS_APP tag.
Hello, I am working on a commercial application that would benefit greatly from being able to disable the Boundary guardian permanently while the application is running. Is there any information on how to get apps whitelisted for this feature when using the CONTEXTUAL_BOUNDARYLESS_APP tag mentioned in the v57 changelog?Unable to read the proper boundary info via Airlink
If you are using Airlink, you are unable to read proper boundary info. ie. what runtime provides you (doesn't matter if you use OpenXR or Oculus SDK) is incorrect. Here's a video of me recording three cases https://youtu.be/0RAaA14LYus And copied the description from the video about parts/cases: Recorded on Quest, the game uses VRAPI (OpenXR gives the same result but with VRAPI I am able to render the actual boundary) Recorded on PC, Quest 2 is connected via Airlink, the game uses Oculus SDK. Note that there is an offset for the play area centre here. Recorder on PC, Quest 2 is connected via Airlink, the game uses OpenXR. Note there's no offset and I am standing closer to the apparent play area centre. I also moved my arms behind me to show where the boundary ends. The most interesting bit here is that Oculus SDK (2) read boundary points properly but still provides incorrect play area info. It almost encloses the whole play area (GetBoundaryDimensions can accept values for boundaryType, I use ovrBoundary_PlayArea, but it kind of looks like ovrBoundary_Outer). Another thing is that I might have at an angle when I started to setup guardian and maybe there's something that makes the boundary off. When I setup a boundary before, it was more aligned on PC with what I had on Quest but for ovrBoundary_PlayArea it still was enclosing the whole boundary tried it. OpenXR was off as well. This is something that has been happening with Airlink since day one. I know that it was reported not only by me and hasn't been fixed yet. I provided steps to replicate the bug, examples, as much info as I could gather only to learn that support has closed my tickets and now I am even unable to create new ones 😄 I started the thread here as it is a general issue and can't really tell if it's more PCVR or Quest related as it seems that PCVR runtime is unable to cooperate with Quest via Airlink.
