The value of the tracking sensor may change when I start the app in the same position/ orientation.
I'm developing an Oculus Rift S app. Currently, I am having a problem. When debugging, the value of the tracking sensor may be different even if I start the app with the goggles in the same position and orientation. (Specifically, it changes by 0.2m in the z-axis and about 20 degrees in the yaw.) (It occurs when the app is restarted several times without moving with goggles on.) I think that the origin of the tracking sensor changes when setting the Guardian (setting floor height, play area). In this case, even if the goggles are in the same position and orientation, the tracking sensor value will change before and after the Guardian setting. However, the value of the tracking sensor may be different even though the Guardian setting has not been changed. What could be the reason for this?
Dash encountered a fatal error please reload dash to continue
After the update two days ago my originally working well rift s encountered this problem. it requires me to reload the dash over and over. I did some tweaks and then my left controlled suddenly lost tracking, but the message of letting me reload the dash changed from popping up every 1 second to every 10 seconds. I had reinstalled the driver and unplug the cables but those didn't work. Sorry for my bad English.
Oculus "exits" to menu, when taking of headset (Standalone application)
So I've just updated an existing standalone Unity Oculus solution, and it has been installed on a newly set-up PC. The problem is, when the app is running, if the user takes off the headset, and puts it on again, Oculus returns to the Oculus Home, and you have to go find the app again! This does not happen on three seperate other computers (Newest updates installed), only two of them developer machines. Any ideas? I've been unable to find anything on this issue...Recenter / Quit from the Universal menu
I followed the guide: https://developer.oculus.com/documentation/pcsdk/latest/concepts/dg-vr-focus/ But the associated flags in the sessions structure are always false, even when clicking on the corresponding buttons in the universal menu. ovrSessionStatus status; ovr_GetSessionStatus(m_ovrSession, &status); if (status.ShouldRecenter) // always false { ovr_RecenterTrackingOrigin(m_ovrSession); } Due to the above I failed the app submission. .HmdMounted and .IsVisible work fine. Please advise. Thanks.
DK2 runs with Runtime 0.8 but HDMI not detected with newest Oculus Setup
I have succesfully connected the DK2 with Runtime 0.8. However, when using the newest Oculus Setup, the DK2 is not recognized and the following error appears: 'You're headset's HDMI cable isn't plugged in. Please plug in your headset.'. Rebooting the DK2, the computer, and changing the settings to allow unknown sources does not help. Running the demo of the windows 1.13 SDK gives, for that reason I guess, also the error that there is no HMD found. Other information: - Windows 10 - I tried it on a laptop with NVIDIA GeForce GTX 970 M and on a computer with NVIDIA GTX 1050 Any suggestions or solutions?How to enable the rift distortion view on desktop?
I had some issues regarding rendering on oculus, is there a way to enable the desktop view like the demo app tiny room? I checked the code but I still cant figure it out, I didn't write the code originally, just did an upgrade from sdk 0.6 to 1.9, and now it seems getting into some weird rendering problems, the right eye view seems uses a different coordinate system than the left eye, and I am trying to get the rendering showing on desktop to get a clear view. Any help would be appreciated!