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.
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.
