CODEWITHSUNDEEP
unity-game-engineoculus
Emy
Emy

Reputation: 977

Unity3D is crashing when hitting play – and when Oculus is on

I am using Unity 5.2.2f1 with the Oculus Rift and Windows 7. Everything was working well till... one hour ago. I first ran a build that played smoothly. I then moved away from my computer; when I came back, it was shutting down. Upon turning the computer back on, Unity started to crash anytime I hit play and the Oculus is on. If the Oculus is turned off before I start Unity, everything works perfectly. This is the link to the Unity Editor log.

This is part of the log, where the crash happens:

Completed reload, in 0.636 seconds Initializing Unity.PackageManager (PackageManager) v5.2.2 for Unity v5.2.2f1

(...)

Native extension for OSXStandalone target not found Native extension for WindowsStandalone target not found Native extension for LinuxStandalone target not found Native extension for WebGL target not found Native extension for SamsungTV target not found Native extension for Tizen target not found Native extension for Android target not found

04/22/16 19:07:47: [CAPI] LibOVR module is located at C:\Windows\system32\LibOVRRT64_0_7.dll

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

Crash!!!

SymInit: Symbol-SearchPath: 'C:/Program Files/Unity/Editor/Data/MonoEmbedRuntime;.;C:\Users\vcladmin\Documents\maze;C:\Program

(...)

Upvotes: 0

Views: 1527

Answers (1)

Emy
Emy

Reputation: 977

@Programmer, I have used System Restore as you suggested. The suggested restore point was at an install of "Dell update", right at the time of the crash. Proceeding with the restore, I realized that the NVIDIA driver was being restored from an old version (266), to the newer version (358) (that's the version I need to make the Oculus work). After the restore everything went back to normal. Then I tried to install Dropbox. After the install, the computer turned off again and, like before, once restarting, the Oculus was not working anymore. I checked the Oculus setup and it said it needed a new NVIDIA driver. So something is happening that makes the NVIDIA driver go from 358 to the old one. I don't understand why. What would you suggest?

A friend told me that probably the "Dell Command update" thinks that the new NVIDIA driver is the wrong one, so it restores it to the old one every time it updates. We have disabled automatic Dell Command updates.

Thanks for the help.

Upvotes: 1

Related Questions