Forum Discussion
0.4.2 & x64 builds - OVRCamera stops working when lag occurs
This is a bit complicated to describe. Effectively, I think the x64 driver restarts when the application is unresponsive for a moment. And because of that restart, it can't find the Rift. In D...
Sorry for the late reply.
Yes! This is the same error
I were not able to get rid fo the "screen 50% dimmed" bug in my x86 builds.
Right now, 0.4.2 is just not an option for me. Either I have a dark screen (even manually disabling timewarp did not help, it had to be toggled from on to off) or my cameras stop working.
"drash" wrote:"vrdaveb" wrote:"skyworxx" wrote:
I remember seeing an error message in the lines of "nullpointer in ovrdevice.GetTrackingState".
You mean OVRDevice.HMD.GetTrackingState()? That wouldn't happen in our code because we check if OVRDevice.HMD is null before trying to use it. Can you send output_log.txt from a run with the issue?
I see the same error here, only shows up in 64-bit builds. The error is deeper than from GetTrackingState() itself though. More details can be found in my post here.
Yes! This is the same error
"vrdaveb" wrote:
For now, I would recommend sticking with x86.
I were not able to get rid fo the "screen 50% dimmed" bug in my x86 builds.
Right now, 0.4.2 is just not an option for me. Either I have a dark screen (even manually disabling timewarp did not help, it had to be toggled from on to off) or my cameras stop working.