Forum Discussion
OVRManager.boundary returns Null
Hi! I'm using Unity 2018.4.19f1 and the latest available Oculus integration package v17.0 and Oculus Android SDK v1.38.6.
I've been trying to access the guardian boundary on my Oculus Quest in order to mark the outline, but haven't gotten it to work so far. So I've tried to identify the problem using Debug and found that both OVRManager.boundary.GetConfigured() and OVRManager.boundary.GetGeometry(OVRBoundary.BoundaryType.OuterBoundary); returns "NullReferenceException: Object reference not set to an instance of an object".
In the end I ran Debug.Log(OVRManager.boundary) which simply returns Null, which explains the above NullReferenceException. So the question is why does this return Null, when I most definetly have set the guardian boundaries on the Quest? Has anyone had any similar issues? I've run Debug.Log from both Start and Awake, but got the same result regardless.
I run the script from an empty GameObject, should I maybe be running it from somewhere else? The project itself is a new empty project, with the VRTK 3.3 SDK Manager setup for the OVRCameraRig and not much else, except for the controller alias objects and the VRTK simulator camera rig.
I've been trying to access the guardian boundary on my Oculus Quest in order to mark the outline, but haven't gotten it to work so far. So I've tried to identify the problem using Debug and found that both OVRManager.boundary.GetConfigured() and OVRManager.boundary.GetGeometry(OVRBoundary.BoundaryType.OuterBoundary); returns "NullReferenceException: Object reference not set to an instance of an object".
In the end I ran Debug.Log(OVRManager.boundary) which simply returns Null, which explains the above NullReferenceException. So the question is why does this return Null, when I most definetly have set the guardian boundaries on the Quest? Has anyone had any similar issues? I've run Debug.Log from both Start and Awake, but got the same result regardless.
I run the script from an empty GameObject, should I maybe be running it from somewhere else? The project itself is a new empty project, with the VRTK 3.3 SDK Manager setup for the OVRCameraRig and not much else, except for the controller alias objects and the VRTK simulator camera rig.
1 Reply
Replies have been turned off for this discussion
- Solved: In case any one else has a similar issue, I added the script to the OVRCameraRig, where the OVRManager script is a component and now it works! Except for the y-axis boundary point being off by -1.6, but that's another issue!
