Search Unity

OVR Error : Code -1003

Discussion in 'AR/VR (XR) Discussion' started by BigB, Jun 11, 2015.

  1. BigB

    BigB

    Joined:
    Oct 16, 2008
    Posts:
    672
    I can't get my Oculus to work (DK1), I have the Oculus runtime 0.6 installed.
    I couldn't get anything VR to work until I disabled DX9 and enabled only DX11.
    Now it recognizes the Oculus , but I get this on the console :

    OVR Error:
    OVRTime: 2453.223440
    Time: 2015-06-11 07:46:09 [883:513:900]
    Code: -1003 -- ovrError_Timeout
    Description: Semaphore WaitForSingleObject

    Oculus image is all black.
    Any clues on what the problem is ?

    Thanks,
    Bruno
     
  2. BigB

    BigB

    Joined:
    Oct 16, 2008
    Posts:
    672
    Somehow the error went away.
     
  3. DARKCORTEX

    DARKCORTEX

    Joined:
    Oct 22, 2012
    Posts:
    2
    same error here!.

    what do you do?
     
    Last edited: Jun 11, 2015
  4. BigB

    BigB

    Joined:
    Oct 16, 2008
    Posts:
    672
    I enabled DX11 api, disabled DX9, disabled VR, re-enabled VR, restarted Unity, and eventually started working.
     
  5. DARKCORTEX

    DARKCORTEX

    Joined:
    Oct 22, 2012
    Posts:
    2
    I tried that but not work for me :(
     
  6. HappySlice

    HappySlice

    Joined:
    Nov 3, 2014
    Posts:
    22
    I am getting the error and that processes did not work for me either.
     
  7. Piflik

    Piflik

    Joined:
    Sep 11, 2011
    Posts:
    293
    Restarting the Oculus Runtime Service fixed a Time-Out Error (Code 1003) for me
     
  8. Dance_M

    Dance_M

    Joined:
    Aug 17, 2014
    Posts:
    15
    I have same problem.

    DX11&VR mode enable/disable did not help.
    Service restart did not help.

    Empty scene with several transparent spheres.

    OVR Error:
    OVRTime: 24995.840077
    Time: 2015-07-14 21:53:25 [690:399:500]
    Code: -1003 -- ovrError_Timeout
    Description: Semaphore WaitForMultipleObjects

    (Filename: C:/buildslave/unity/build/Runtime/VR/Oculus/VRDeviceOculus.cpp Line: 52)



    Windows 8.1 x64
    DK2, DirectHMD mode
    Oculus Runtime 0.6.0.1
    Unity 5.1.1p4 / 5.1.1p3 /5.1.2f
    Nvidia 353.30 / 350.12
    GTX Titan x3 (SLI off)

    Unity profiler showing PlayerEndOfFrame > OculusWaitForGPU 99.7% 1002ms

    All becomes normal if change app windows focus to any other window, and switch back to app after. But I should do this on after every app launch. Also, on Alt+F4 app is freezing for minute or so.

    Would be glad to hear any suggestions and ideas.

    PS: I think, all this happens because of that bug:
    https://forums.oculus.com/viewtopic.php?f=34&t=24298
     
    Last edited: Jul 22, 2015
  9. Yasei_no_otoko

    Yasei_no_otoko

    Joined:
    Nov 25, 2013
    Posts:
    13
    What GPU?
    I have the perfectly same problem.
    My environment is following.

    Windows 8.1 x64
    DK2, DirectHMD mode
    Oculus Runtime 0.6.0.1
    Unity 5.1.1p4
    Nvidia 350.12
    GeForce GT650M (Macbook Pro Retina Mid2012 / without Optimus)

    Unity5.0.4 + Oculus Plugin 0.5/0.6 have not this problem.
     
  10. bfloch

    bfloch

    Joined:
    Jan 4, 2013
    Posts:
    24
    Had this with:
    Unity5.1.2f1 + Oculus Plugin 0.6.1.
    Win7 64 with Geforce GTX 700 (v350.12)

    Solved by trying following steps:
    - Disable DirectX 9.
    - Disable / Enable VR.
    - Restart OVR Service.
    - Disable/Enable Dual Monitor
    - Restart Unity

    Works again.
     
  11. Dance_M

    Dance_M

    Joined:
    Aug 17, 2014
    Posts:
    15
    GTX Titan x3 (SLI off)
    Older Unity versions, before v.5.1, have no own integrated VR-mode, and are using the Oculus Integration Asset, so there definitely no such problem, as it completely different way to use VR.
    That is only thing I left to try.
    PS: did not helped...
     
    Last edited: Jul 23, 2015
  12. vvander

    vvander

    Joined:
    Jan 18, 2011
    Posts:
    72
    We are seeing the same issue. 980Ti here.

    By following these steps it seems to work again for a bit, but as soon as focus changes away from the game window (even still within the Unity Editor) the issue reappears.

    Anyone submitted a bug report for this yet?

    EDIT: Just noticed OP is using a DK1, but we're seeing the same problem on our DK2s.
     
    Last edited: Jul 27, 2015
  13. magic9cube

    magic9cube

    Joined:
    Jan 30, 2014
    Posts:
    58
    I had the problem also. I restarted this service and the error was gone.The error for me initially came after i'd enabled VR on a large existing project.
     
  14. Incendiary-Games

    Incendiary-Games

    Joined:
    Mar 24, 2015
    Posts:
    18
    I'm having the same issue on a Nvidia GTX 780. It comes and goes and it's totally blocking development.
     
    Last edited: Aug 4, 2015
  15. bfloch

    bfloch

    Joined:
    Jan 4, 2013
    Posts:
    24
    Just as update. I did not get this error so often anymore.
    Whenever it does appear a restart of Unity seems to fix it.

    Did anyone try with the latest PatchRelease?
     
  16. aseiden

    aseiden

    Joined:
    Jul 14, 2015
    Posts:
    2
    I'm still having this problem intermittently with 5.1.2p3. The only thing that seems to reliably reset things for me is re-installing the Oculus Runtime. That may be voodoo, though...
     
  17. aseiden

    aseiden

    Joined:
    Jul 14, 2015
    Posts:
    2
  18. bfloch

    bfloch

    Joined:
    Jan 4, 2013
    Posts:
    24