Skip to main content
Participant
Jun 24, 2015 10:53 PM UTC

Problems with the new version in U5.1.1f1

I build a scene and bring it to the test machine with the DK2. I play the file with -vrmode Oculus. It only shows the first frame and then stops working. Also the editor Oculus mode doesn't seem to work. It's on extended mode.

From what I understand reading the forums, if you don't want to use the built in Unity support, you uncheck VR support and import the runtime 0.6.0. So if you want to use the built in unity support, you should be able to just check vr support and leave out the runtime, and build as normal-well normal along with editing the shortcut to run in the Oculus.

Upon playing, I recieve the warning, and the game hangs at the first frame. Once I press a button it crashes. Please help, I'll have to revert if I can't get it to work right and I really want to make it work...
    This topic has been closed for replies.

    10 replies

    Inspiring
    Jun 24, 2015 11:14 PM UTC
    That's strange. Can you provide some log files. Start here:

    viewtopic.php?f=34&t=23521

    And the files from editor and player from here:

    http://docs.unity3d.com/Manual/LogFiles.html
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    QFGlennAuthor
    Participant
    Jun 24, 2015 11:48 PM UTC
    I can't upload attachments :<

    configLogOculus062415_437pm
    (https://drive.google.com/open?id=0B0ZOqxcNb9NsNVNpRlpEVTFmNU0)

    ServerLog_2015-06-22_13.06.33
    (https://drive.google.com/open?id=0B0ZOqxcNb9NsRXg3VHhMLVRhSG8)

    output_log
    (https://drive.google.com/open?id=0B0ZOqxcNb9NsUmYxbmxiNDFQd1k)

    The game DOES work off the Oculus. But every time I use -vrmode Oculus, it crashes either immediately or the first time I press a key.
    Co-Founder, Head of Creative Design at Quantum Forge ( http://quantumforgegames.com/ ) Game Developer and Creative Developer at NOMI Studio
    Inspiring
    Jun 25, 2015 12:39 AM UTC
    I see some errors in the logs. Specifically these lines:

    OVR Error:
    OVRTime: 183575.208044
    Time: 2015-06-24 16:05:27 [520:561:0]
    Code: -1006 -- ovrError_ServiceError
    Description: SetFullscreenState
    In OnEnterRender SetFullscreenState
    OVR Error:
    OVRTime: 183588.528541
    Time: 2015-06-24 16:05:40 [845:238:500]
    Code: -3000 -- ovrError_Initialize
    System error: -2005270523 (887a0005) -- (unknown)
    Description: Open shared fence handle


    However, I'm not totally sure what the core issue is. I'm trying to get engineering to look into it now.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    Participant
    Jun 25, 2015 12:42 AM UTC
    You may have upgraded or reset your graphics card with the service running. Have you tried restarting your service? We're aware of the bug and it should be fixed in 0.7.
    QFGlennAuthor
    Participant
    Jun 25, 2015 12:56 AM UTC
    Restarted the service, same issue :< What else can I do to help you troubleshoot this?
    Co-Founder, Head of Creative Design at Quantum Forge ( http://quantumforgegames.com/ ) Game Developer and Creative Developer at NOMI Studio
    QFGlennAuthor
    Participant
    Jun 29, 2015 6:36 PM UTC
    Uhhh, guys? Help?
    Co-Founder, Head of Creative Design at Quantum Forge ( http://quantumforgegames.com/ ) Game Developer and Creative Developer at NOMI Studio
    Inspiring
    Jun 30, 2015 10:36 PM UTC
    It appears that this issue may be known, and will probably be fixed in a future software update. However, I have asked the team if there is any work-around you can do for the time being. Sorry for the inconvenience.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    QFGlennAuthor
    Participant
    Jun 30, 2015 11:43 PM UTC
    Thanks a lot for staying with me! Anything we could do to fix it we would really appreciate it. :)

    Gotta love the Oculus support team! <3
    Co-Founder, Head of Creative Design at Quantum Forge ( http://quantumforgegames.com/ ) Game Developer and Creative Developer at NOMI Studio
    Participant
    Jul 1, 2015 12:46 AM UTC
    According to the 730's specs it's a budget card and can't drive a standard monitor and the Rift at the resolutions/frame rate needed. The service is failing because the system can go into the mode to drive VR. A more recent mid-range or high-range card is needed to scan out the signal needed for vr.
    QFGlennAuthor
    Participant
    Jul 1, 2015 1:02 AM UTC
    "DeanOfTheDrivers" wrote:
    According to the 730's specs it's a budget card and can't drive a standard monitor and the Rift at the resolutions/frame rate needed. The service is failing because the system can go into the mode to drive VR. A more recent mid-range or high-range card is needed to scan out the signal needed for vr.



    The same build works on the legacy integration. Are you saying that the new integration is a step backwards? Why wouldn't it be able to work? At least a built .exe version should still be able to work right?
    Co-Founder, Head of Creative Design at Quantum Forge ( http://quantumforgegames.com/ ) Game Developer and Creative Developer at NOMI Studio