Forum Discussion
Game crashing with Unity 5.3.5p5 and Oculus Runtime 1.5
Hi !
Since the last update of the Oculus Runtime to 1.5, our game is crashing in builds (everything is fine in the editor).
We're using Unity 5.3.5p5 and the latest nvidia drivers. Is there any way to rollback to the previous runtime version (1.4) so we can test and compare our Unity logs ?
Also, we have this error spamming in the console/log : "VR: Error setting active audio output driver. Falling back to default." . We're using Wwise, and we know there's some issues in redirecting the audio output to the HMD, but even by doing it manually in the code (selecting Rift Audio as the output device in the Wwise settings), the error is still there, and I don't know if it was there with the previous runtime.
Thanks in advance,
Robin
Since the last update of the Oculus Runtime to 1.5, our game is crashing in builds (everything is fine in the editor).
We're using Unity 5.3.5p5 and the latest nvidia drivers. Is there any way to rollback to the previous runtime version (1.4) so we can test and compare our Unity logs ?
Also, we have this error spamming in the console/log : "VR: Error setting active audio output driver. Falling back to default." . We're using Wwise, and we know there's some issues in redirecting the audio output to the HMD, but even by doing it manually in the code (selecting Rift Audio as the output device in the Wwise settings), the error is still there, and I don't know if it was there with the previous runtime.
Thanks in advance,
Robin
32 Replies
Replies have been turned off for this discussion
- Hopefully this week's patch release will add 1.5 runtime support (Unity does patch releases weekly on Friday). If not, would be really nice if we could have another interim solution where we manually put the OVRPlugin files into the Unity directory like we had to do with 1.3.
- 5.3.5p6 does use PC SDK 1.6 (and Mobile SDK 1.0.3). Can you share output_log.txt from one of the crashing runs? It will probably be easier to debug if you can reproduce the issue enable "Development Build" and "Script Debugging" in the build settings.
would be really nice if we could have another interim solution where we manually put the OVRPlugin files into the Unity directory
Now that Unity is on a weekly release cadence and all our SDKs are public, the plan is to ship new SDK support inside of Unity with <1wk latency after each new PC SDK. This allows us to build most of the goodness into Unity instead of relying on vendor-specific scripts and plugins. The drop-in OVRPlugin solution was actually providing access to functionality we had already built into Unity that wasn't accessible to the 0.8 stack. - Ah, thanks for the explanation! Updating to p6 now. Looks like op was on p5 as well, so let's see if there is still an issue with p6.
- Sounds similar to my problem, interested in hearing any updates.
- We still have the same issues on p6 : / . Does anybody else is in the same situation ?
- Can you share output_log.txt from one of the crashing runs?
- Sure !
- I notice you still have OculusInitPlugin.dll in your project. This is extremely old and should be removed from your project. Not sure is that could be causing the issue.
vhamm said:
I notice you still have OculusInitPlugin.dll in your project. This is extremely old and should be removed from your project. Not sure is that could be causing the issue.
I have no such dll in my project and I get the same error- This looks similar to an issue we've seen reported by several other people. Basically, there seems to be a race condition between our texture setup code and a data copy that happens after rendering. We're looking for a fix, but the best solution in the meantime is probably to stay on 5.3.5p3 or earlier.
