Unity Crashing on Oculus Integration

Unity Engine
1

Hey, I have a project that requires Oculus. I can’t open it without Unity “quitting unexpectedly” before opening. I found a work around is to delete the Oculus assets and then Unity will open, but when I go to reimport from the asset store Unity crashes and I run into the same issue.

I’ve tried:

  • importing Oculus onto a different existing project and it crashed as well.
  • opening in 2018.1.5f1, 2018.2.21f1, 2018.3.9f1, 2019.1.0f2
  • Switching Player Settings to .NET 4.x then installing Oculus
  • deleting lock file

This first bit of the error message:

Process: Unity [12971]
Path: /Applications/Unity/*/Unity.app/Contents/MacOS/Unity
Identifier: com.unity3d.UnityEditor5.x
Version: Unity version 2018.1.5f1 (2018.1.5f1)
Code Type: X86-64 (Native)
Parent Process: Unity Hub [350]
Responsible: Unity [12971]
User ID: 501

Date/Time: 2019-04-25 20:41:43.820 -0600
OS Version: Mac OS X 10.13.6 (17G5019)
Report Version: 12

Time Awake Since Boot: 76000 seconds

System Integrity Protection: disabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [0]

Application Specific Information:
Assets/Oculus/Spatializer/Plugins/AudioPluginOculusSpatializer.bundle/Contents/MacOS/AudioPluginOculusSpatializer

4471678–410857–UnityCrashReport.pdf (114 KB)

3 Likes
2

Having the same issue. Did you end up finding a fix?

3

Yes, it turned out the previous dev already had oculus assets partially set up in the app. If I remember right, I was causing the crash by having imported what was already imported. Once I realized this I just had to restart and find out where they left off.

4

I am having the same problem and also tried it out on a brand new file, it is really frustrating… Wonder if someone found a solution yet…

5

Hi,
I’m having the same problem and the workaround I founded is not import the AudioPluguinOculusSpatializer.bundle for Macosx. Then the import finishes with no crash but I don’t if it is necessary or not, so amb newbie.

2 Likes
6

Not sure if this will help, try using the Unity XR Plugin:

7

Yes, this is what had been recommended me, and following the setup seems I got it running.
But then what happens with the oculus plugin?

8

I’m just getting started using the XR toolkit so I could be wrong but I’m pretty sure the Oculus XR Plugin is replacing the Oculus Integration.

9

I had the same issue today with 2020 M1 MacBook Pro:

  • Unity 2019.4.18f1
  • 2020 M1 MacBook Pro
  • Oculus Integration version 23.1

Unity would just crash while importing and would crash when reopening.

I was able to avoid the crash by deleting the Oculus folder and reimporting the Oculus Integration without the Spatializer folder, but because that caused other issues which made me suspect audio wouldn’t work well.

In the end, I went with Unity’s XR Plug-in management feature under Edit > Project Settings, basically by following the instructions here:

10

Any news on fixing Oculus integration crashing on play?
Deleting Oculus folder and reinstalling Oculus Integration doesn’t do anything. Version 37 now.

11

It seems a problem with unity xr plugin management.See this video maybe help you.
Unity XR - Unity crashes on Play exit with Oculus Integration - YouTube

1 Like
12

Thank you, this worked. I can’t believe I wasted hours on this simple thing.

1 Like