Search Issue Tracker
Fixed in 5.4.3
Votes
0
Found in
5.4.0f2
Issue ID
818159
Regression
No
[OpenVR | CV1] 5.4.0f2: UnityEngine.VR.VRDevice.isPresent is inconsistent with OpenVR + Rift CV1
[OpenVR | CV1] 5.4.0f2: UnityEngine.VR.VRDevice.isPresent is inconsistent with OpenVR + Rift CV1
2. How we can reproduce it using the example you attached
1) Setup CV1
2) Ensure Open VR is the preferred SDK in the VR SDKs list in Player Settings
3) Now hide the CV1 from the tracking camera so that SteamVR reports "Headset not tracking" and "Not Ready"
Note: Getting SteamVR in this state can be a little finicky so be patient and if it doesn't get in that state for a while after hiding the headset, try rebooting Oculus Home and SteamVR. Also see the attached screenshot for the expected SteamVR state.
4) Once the headset is hidden and not tracking enter playmode.
5) Observe that VRDevice.isPresent is reported as false in both the Awake and Start functions
Expected result:
UnityEngine.VR.VRDevice.isPresent shouldn't return false if the HMD is connected and merely occluded from the view of the basestations/cameras.
More details.
http://forum.unity3d.com/threads/5-4-0f2-unityengine-vr-vrdevice-ispresent-is-inconsistent-with-openvr-rift-cv1.418393/
License type: Pro
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment