Hey guys,
I just updated Unity to 5.1.3 and now it is crashing whenever I try to push play on the editor or do a build. It is not a Unity crash, I get the “Unity Editor has stopped working” windows error.
What is up with this? Should I rollback to Unity 5.1.2?
Try doing a clean install
I have tried 5.1.3f1, too! There seems to be a problem with VR, builds with this version does not work with the DK2 => no image in the rift, it seems both views are rendered in the normal viewport (one view is flipped and overlaying the other). Although I had many crashes with this version…
I use 5.1.2p3 again, which is working for fine for me! I hope it will get fixed soon…
Clean install was a dud, still crashing across the board with all the VR projects (3 of them) and even on a new, clean project with only VR support enabled.
I’m resisting the urge of letting Unity reps get a piece of my mind about this mess. Complete waist of time and production money on this update. My patience is wearing very thin with these guys…
Funny thing is that there are supposed to be a number of interesting fixes for VR on 5.1.3, it would be nice to see that actualy working :\
Forgot to mention Unity version, OS and hardware:
Unity 5.1.3f1 Pro, Windows 8.1 both running on:
Dual Intel Xeon E52620 V3, 64 GB DDR4 ram, GTX980 Ti, plus assorted components (SSDs and such).
Can provide windows crash log and Unity log if it helps.
No one has any ideas about on how to overcome this issue?
Same here, crash on Play, running Windows 7, DK2, Unity 5.1.3f1 Personal. Ran fine until I updated yesterday. Guess I’ll roll it back to 5.1.2. I wonder if it requires the new Oculus runtime which has been delayed… and as I write this is seems as if they just released it. Will try installing the v0.7.0.0-beta first and see if playmode works in Unity with the DK2.
Nope. Installed the new Oculus runtime and tried pressing play the 5.1.3f1 editor, and it still crashes.
Ironically, I’m rushing to get a decent build to bring to the Unity conference in Boston, but between this, the lightmap baking issues, and occlusion culling issues, I don’t think I’m going to make it. Has anyone entered a bug report?
PS: Before rolling everything back I tried to build my game, and I get the same crash while building.
Aw darn it, I was hoping the new Oculus runtime fixed it 
I haven’t entered a report yet, did you? I’ll go right on over and add my woes to yours! I’m also going to hit the Oculus forums and check for something over there. I’ll report back any findings.
Ok, according to Oculus:
“If possible, it’s recommended to use Unity 5.1.2f1 with the latest version of the Oculus Utilities.” dated 27 August (yesterday). 5.1.3f1 is officialy a dud for VR until further notice
More info from Oculus:
“The problem is with the Oculus integration inside of Unity. It has to do with texture allocation when MSAA or linear lighting is enabled. A fix is expected in a Unity 5.1.3 patch release within 1-2 weeks.”
Is there a reported problem, So we can add a vote?
I confirm… with Unity 5.1.3f1 crash on Play and Oculus On
Since this crash isn’t throwing up the Unity bug reporter, (if you haven’t done so already) could you create a crash dump file (steps here Troubleshooting the Editor - Unity Engine - Unity Discussions) and open up the bug reporter and submit it that way. Then post the bug number here so I can pass it on.
@ : I reinstalled 5.1.3, reproed the crash and submitted a dump file. I shared it in the public issue tracker and here’s the bug number…
@ Hitting the same issue reported here as well. Submitted the bug report below to pass along another crash dump
https://fogbugz.unity3d.com/default.asp?724993_a7pl31n0squkmaaa
Might also be worth noting: I’m using the NVIDIA drivers linked from the their support site for the new oculus runtime below. Version 355.84
I don’t think it makes a difference; I had the issue before and after installing the latest drivers
FYI: I just installed 5.1.3p2 (released today) and I’m able to press Play without crashing now. Build also works. And I just received an email from Unity QA confirming that the latest patch fixes this issue. :)
I certainly recommend at a minimum reading the latest patch release notes whenever they come out. It seems like the categories of fixes/improvements are alphabetically sorted so VR stuff can always be founds right near the end. It makes me happy to see how much development it going into VR in Unity these days
Close the Oculus service and try again. If it still crashes reopen and try again. Works for me.