Application crashes on start with Unity 5.3.5p2 - 5.3.5p6

I believe the dll that Unity provides for builds is still the 1.3.x or 1.4 version, so builds are probably borked because of that (though someone here said the 1.5 dlls should be in Unity shortly).

Edit: Looks like 5.3.5 p6 is out now. Try updating to that version of Unity to see if it's still an issue.

I've just realized my post made it sound like I hadn't tried 5.3.5p6 (edited post to fix). I tried this and got the same results, I'll try a few more things to confirm!

The error log reports "nvwgf2umx.dll caused an Access Violation" or "OVRPlugin.dll caused an Access Violation"

In 5.3.5p6 (which uses PC SDK 1.5), we fixed an issue with start-up where Unity sometimes tried to use the eye buffers before they were fully initialized.

Can you reproduce the issue in 5.3.5p6 with a "Developer Build" and share the full output_text.log?

vrdaveb said:

Can you reproduce the issue in 5.3.5p6 with a "Developer Build" and share the full output_text.log?

Hi I'm getting the same issue when I enable the VR the game 90% of the times crashes, sometime the VR starts but only rendering one eyes and the game crashes shortly afterwards.

Can I send you the files in private?

Can somebody at Oculus please look at my thread here in the Unity forum?

https://forum.unity3d.com/threads/build-crashes-with-win-10-64-bit-while-searching-for-oculus-plugin.441733/#post-2857026

I'm absolutely lost.   My build is 32 bit only, but I currently have a bunch of 32 bit Windows 10 users that are getting this error:  

"Initialize engine version: 5.3.5p2 (3103edb99077)'."

This started out as a problem a couple days ago with a Windows 10 64 bit user.  I tweaked some settings on the OculusPlugin.dll (totally different file) and his problems went away.  No idea why because it wasn't even the same file.   Thinking the problem was gone, I started a Steam exposure round and now have at least two other people (at least one of them on 32 bit) reporting this problem.  These people are not using VR at all, the game is simply crashing because it fails to load a 32 bit OVRPlugin.dll on a 32 bit Unity build running a 32 bit version of Windows 10.  I'm flabbergasted.

Since that exposure round is running, every hour that ticks by is just going to be racking up more refunds, so if somebody can help out here ASAP and save me a small fortune I'd really appreciate it.

I don't know what to do.  Do I have to upgrade to a new version of Unity in the middle of a Steam exposure round to try to fix this?   That's a terrifying prospect, in my experience over the last couple of years a new Unity version has about a 90% chance of introducing brand new game breaking bugs.  Would rather avoid that but if it's the only way then I'll just have to do it.

Oculus is running flawlessly as long as somebody is on a machine that happens to load the dll successfully. The reports of this problem have only been on Windows 10 (32 and 64 bit) without any VR at all, if that helps.

Nobody?

5.3.5p2 should work without crashing.

> I tweaked some settings on the OculusPlugin.dll (totally different file) and his problems went away.

OculusPlugin.dll shouldn't be in your project. It sounds like you may have updated from Unity 4. If that's the case, can you delete the Assets/OVR folder and all Oculus plugins from Assets/Plugins and re-import the Oculus Utilities to make sure you are using a pure Unity 5 integration?

Ok, thanks.   The problem is OVRPlugin.dll though, not OculusPlugin.dll.  I have no idea why changing settings on the second file did anything at all.

As far as I know I'm not using the Oculus Utilities, just the native Unity integration.  Is that possible or am I mistaken?