Search Issue Tracker

Fixed in 1.4.3

Votes

6

Found in [Package]

1.3., 1.2.0, 1.1.0

Issue ID

1242301

Regression

No

[XR][Oculus Rift] Editor crashes on entering in play mode when Oculus Rift is plugged

Package: Oculus XR Plugin

-

When Oculus Rift is Plugged and entered play mode causes the editor to crash, refer attache video

Prerequisite: Make sure Oculus Rift is plugged to the system

Steps to repro:
1. Create a new project
2. Edit > Project Settings > XR Plug-in Management > Insall XR plugin Management
3. Plug-in Providers > Oculus
4. Hierarchy > Create > 3D Objects > Cube
5. Hit play

Actual Result:
Editor crashes on entering play mode

Expected Result:
Editor enters in play mode even if the Oculus Rift is plugged

Note: Working fine with the legacy package on Unity 2019.1.11f1 and earlier version of Unity, but with XR Management SDK scene is not loading in the device, it is getting stuck at the start of loading the scene

Occurring on:
2020.2.0a9, 2020.1.0b7, 2019.3.12f1, 2019.2.13f1

Package found version:
XR Plugin Management: 3.2.9, 3.2.4, 3.0.6, 3.0.1, 2.0.0 - preview.13
Oculus XR Plugin: 1.3.3, 1.2.0, 1.1.0

Environment:
Occurs only on Windows 10

Stack trace:
========== OUTPUTTING STACK TRACE ==================

0x00007FFEB14656CD (OculusXRPlugin) SetUserDefinedSettings
ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 00007FF6CA579E67)
0x00007FF6CA579E67 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF6CA56B504)
0x00007FF6CA56B504 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF6CBF585FA)
0x00007FF6CBF585FA (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF6CBF5FFBC)
0x00007FF6CBF5FFBC (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF6CBF603A8)
0x00007FF6CBF603A8 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF6C9E8EF80)
0x00007FF6C9E8EF80 (Unity) (function-name not available)
0x00007FFEE5837BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFEE69ACE51 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

  1. Resolution Note (fix version 1.4.3):

    This is resolved with the Oculus XR Plugin 1.4.3 package.

  2. Resolution Note (fix version 1.4.3):

    This is resolved with the Oculus XR Plugin 1.4.3 package.

Log in to vote on this issue

Comments (10)

  1. rustinlee

    Apr 21, 2021 20:26

    Make sure you have at least one microphone sound device (like Headset Microphone - Oculus Virtual Audio Device) enabled!

  2. VertigoTrevor

    Mar 12, 2021 17:12

    Did some extra digging as this topic mentions some variations that don't result in error logs for people:

    https://forum.unity.com/threads/unable-to-start-oculus-xr-plugin.913883/

    For me, going back some versions of the Oculus XR plugin managed to get it in a working state.

    1.4.0 works
    1.4.3 works
    1.5.1 crash

    We will be sticking on the 1.4.3 now so we can start using the LTS version. But there is an issue with the later Oculus XR plugins at least.

  3. VertigoTrevor

    Mar 12, 2021 17:00

    Still happens in 2020.3 LTS
    Exact same crash.

    My reproduction steps, 100% reproducable on my machine.
    - Install XR management plugin 4.0.1
    - Install Oculus XR plugin 1.8.1
    - Press play in the SampleScene

  4. pokotion

    Feb 03, 2021 15:53

    Still happening.
    Unity 2020.2.2f1
    Oculus XR Plugin 1.7.0 package.
    XR Plugin Management 3.2.17 package.

    work fine.
    Unity 2019.3.0f6

  5. mucklepaws

    Oct 29, 2020 14:55

    This is still happening for me with the latest version of unity and the oculus integration. Any new suggestions?

  6. mmarko1906

    Aug 20, 2020 11:31

    Have this issue as well on (19.4.8f1 20.1.2f1)seem that new XR manager have issue with GPUs(findout that if i plugin Oculus hdmi to primary GPU where is my monitor connected aswell its working, but if i connect Oculus to secondary GPU editor will crash) so if u have more GPUs try connect your VR hdmi to primary GPU. Also try to disable Intel integrated GPU in bios if u have one.

  7. warrenSOLID

    Aug 06, 2020 20:09

    I'm still having this problem with 2019.4.x (1f1, 6f1, 7f1). Oculus desktop software is 19.0.0.364.531.

    Unity "run" works fine initially. i import the XR Integration Toolkit (preview) 0.9.4. Go to "Project Settings..." and click the install XR button. checkmark "Oculus" on Desktop tab. Now if i press Run button it will crash (reliably).

    This is on Windows 10 Enterprise PC (64 gb ram, intel i7-7700kCPU @4.20GHz, NVIDIA GeForce GTX 1080 Ti). ... (tho i also see Intel HD Graphics 630 listed under Display Adapters in Device Manager)

    What's weird is i can go in the other room with a different PC (Windows 10 Pro) and everything seems to work. Same Unity and Oculus software versions. but the hardware is : 16 gb ram, i5-6600k CPU @3.5GHz, Nvidia GeForce GTX 970). ... (I ONLY see nvidia listed under display adapters.)

  8. HIL18001579

    May 25, 2020 14:23

    Have this issue as well, (Unity 2019.3.14f1) the VR works fine for a few hours of starting and stopping whilst developing, then either get a black screen for VR or Unity crashes. Not sure what is causing this but VR works fine on my system, albeit my system is somewhat old. It is as though memory leaks and fills up the system video memory, or thinks it has, because Oculus VR still works fine even if VR does not work with Unity (XR) - then I am not that aufait with all the technical interaction with VR and Unity - probably something I need to read up on.

  9. gemisis

    May 21, 2020 06:30

    Confirming this is still an issue on 2019.3.14f1

  10. a436t4ataf

    May 13, 2020 17:24

    Also reported on Unity 2019.3.10 ... fixed for me when Oculus Desktop completed its self-upgrade to v16 (something seemed to be temporarily messed up while Quest was on 15, Desktop on 16 - which Oculus officially supports, but ... perhaps not so well :))

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues