Forum Discussion
shaunnortonAU
6 years agoExplorer
Quest+Link OVRManager.boundary problem
The OVRManager.boundary object is not getting configured and outputs useless information.
Unity version: 2019.3.0f6
Oculus Integration version: 13.0 (Feb 7th 2020)
Oculus Android Package: 2.38.6
Oculus Desktop Package: 2.38.4
Not using any of the new/legacy XR packages.
Not using any Steam stuff.
OVRManager is in a fresh scene, fresh project, on the CameraRig prefab.
Virtual Reality supported is ticked. Android is selected in build settings.
Play in editor runs in the Quest fine.
void Update()
{
Debug.Log("GetConfigured is " + OVRManager.boundary.GetConfigured()); // False
Debug.Log("GetDimensions(Outer) is " + OVRManager.boundary.GetDimensions(OVRBoundary.BoundaryType.OuterBoundary)); // Fluctuates between around (4.6,0,0) and (6.4,0,0)
Debug.Log("GetDimensions(Play) is " + OVRManager.boundary.GetDimensions(OVRBoundary.BoundaryType.PlayArea)); // Fluctuates between around (7,0,0) and (14,0,0)
Debug.Log("GetGeometry(Outer) Length is " + OVRManager.boundary.GetGeometry(OVRBoundary.BoundaryType.OuterBoundary).Length); // Array length is always 0
Debug.Log("GetGeometry(Play) Length is " + OVRManager.boundary.GetGeometry(OVRBoundary.BoundaryType.PlayArea).Length); // Array length is always 0
{
Debug.Log("GetConfigured is " + OVRManager.boundary.GetConfigured()); // False
Debug.Log("GetDimensions(Outer) is " + OVRManager.boundary.GetDimensions(OVRBoundary.BoundaryType.OuterBoundary)); // Fluctuates between around (4.6,0,0) and (6.4,0,0)
Debug.Log("GetDimensions(Play) is " + OVRManager.boundary.GetDimensions(OVRBoundary.BoundaryType.PlayArea)); // Fluctuates between around (7,0,0) and (14,0,0)
Debug.Log("GetGeometry(Outer) Length is " + OVRManager.boundary.GetGeometry(OVRBoundary.BoundaryType.OuterBoundary).Length); // Array length is always 0
Debug.Log("GetGeometry(Play) Length is " + OVRManager.boundary.GetGeometry(OVRBoundary.BoundaryType.PlayArea).Length); // Array length is always 0
}
3 Replies
Replies have been turned off for this discussion
- m2kHonored GuestI have the same issues. Do you find any solution for this?
- MVRKDEVHonored GuestThis is a confirmed bug. I can't post a link to it but you can find it if you search "OVR_CAPI functions for Boundary info don't work with Quest + Link"
- kriversunHonored GuestI also want this problem to be solved
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 2 years ago
- 3 months ago