Forum Discussion
Application crashes on start with Unity 5.3.5p2 - 5.3.5p6
We recently upgraded to Unity 5.3.5p2 & updated the Oculus platform settings & utilities. Our application now crashes on startup when running from a build. it runs fine in the Unity editor, I've tr...
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.
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)
Failed to load 'C:/Program Files (x86)/Steam/steamapps/common/......./....._Data/Plugins/OVRPlugin.dll' with error 'The specified module could not be found.
'."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.