Forum Discussion
WaitableTimer slept too long/short (i.e. X ms)
We've recently updated our project to SDK 1.3. After doing so I've noticed these Unity Warnings being logged whenever the application is not in focus or the editor is not in focus.
Are we doing something wrong to cause this or is this a regular behavior, and if so how can we turn if off?.
I'm currently testing with the DK2 on Windows10 with a gtx 980 gpu.
Are we doing something wrong to cause this or is this a regular behavior, and if so how can we turn if off?.
I'm currently testing with the DK2 on Windows10 with a gtx 980 gpu.
3 Replies
Replies have been turned off for this discussion
- Did you update all your software as shown here?
https://forums.oculus.com/developer/discussion/32457/oculus-1-3-requires-unity-5-3-4p1-new-ovrplugin-for-unity-5 - Yes I believe we updated it all correctly.
- Also saw this in the mySim_Data\output_log.txt .
- WaitableTimer slept too long/short (i.e. 2.336418 ms)
Solution: Fixing 2 UnityException's seen only in the Executable Output_log.txtAlso,
Exceptions fixed: All were MISSING TAG's ! Why these errors only show up when running the executable and not the debug session is unclear.
Anyone know why?- UnityException: Tag: PlaneSpecificButtons is not defined. at (wrapper managed-to-native) UnityEngine.GameObject:FindGameObjectsWithTag (string) at MySettings.SetFlightButtons (UnityEngine.GameObject Plane2set, Int32 OnOneOffZero) [0x00000] in <filename unknown>:0 .....
- UnityException: Tag: is not defined. at (wrapper managed-to-native) UnityEngine.GameObject:FindGameObjectsWithTag (string) at MySettings.HideFlyThisButtons (System.String tag) [0x00000] in <filename unknown>:0
A quirk that something was amiss...- DK2 GazePoint worked in debug firing buttons off the canvas; but, DK2 GazePoint wouldn't fire when running the executable.
Check the output_log man.. DOH!
Brilliant OVR everything! Thanks for the release and all the support!
