Up and Coming

Editor ok, Build crash

37 replies
10231 views

Hi,

I have a project setup with the following:

- DX9
- Forward rendering
- Linear colour space
- TImeWrap On
- Playing in extended mode

Playing in the editor is absolutely fine and the build was working with this setup previously but now I get a crash as soon as the game starts. I have tried numerous times.

The stack trace is as follows:

========== OUTPUTING STACK TRACE ==================

(0x687318A0) (OculusPlugin): (filename not available): (function-name not available) + 0x0
(0x687316AD) (OculusPlugin): (filename not available): (function-name not available) + 0x0
(0x68732A4D) (OculusPlugin): (filename not available): UnityRenderEvent + 0x4d
(0x00E4FDE7) (PE_Demo): (filename not available): Behaviour::Transfer<StreamedBinaryWrite<0> > + 0x93587
(0x00DCDEFC) (PE_Demo): (filename not available): Behaviour::Transfer<StreamedBinaryWrite<0> > + 0x1169c
(0x0110731B) (PE_Demo): (filename not available): AnimationEvent::Transfer<StreamedBinaryRead<1> > + 0xf10cb
(0x01109DD2) (PE_Demo): (filename not available): AnimationEvent::Transfer<StreamedBinaryRead<1> > + 0xf3b82
(0x00EBA04D) (PE_Demo): (filename not available): Behaviour::Transfer<StreamedBinaryWrite<0> > + 0xfd7ed
(0x75B1338A) (kernel32): (filename not available): BaseThreadInitThunk + 0x12
(0x771A9F72) (ntdll): (filename not available): RtlInitializeExceptionChain + 0x63
(0x771A9F45) (ntdll): (filename not available): RtlInitializeExceptionChain + 0x36

Any ideas or has anyone seen similar?

This topic has been closed for replies.

Show previous replies

C

cybereality

Inspiring

@CBsGames: Can you provide a diagnostic log from the Oculus Config Util (Tools->Advanced)? Also, do you have multiple monitors or are they are strange (lower than 1080P) resolutions?

X

xhonzi

Up and Coming

I haven't seen this again on my own system, but one of my fellow devs is getting it now.

We're a little off the map, so there's a good chance no one can help us.

We are stuck with Unity 4.3.3f1. Yep.

I had been using Oculus Unity Integration 0.4.4 and everything had been going really well. I decided to upgrade to 0.6.0 for a couple of reasons- which did mean removing the UI code from the OVR package. It seems to be working fine, except for the following problems.

It works just fine in editor on all systems.

However in build it doesn't run on my buddy's 640 (win7x64) or my test pc's 740 (Win8x64). It runs just fine on my dev PC's AMD 7870, and my Laptop's intel gpu. Another fellow dev has a higher end nVidia 7XX (Win7x64) and it runs fine there.

All have different monitors doing different resolutions, but we swapped out a 1080p monitor to the 640, and even ran the Rift as the only monitor. Always the same "couldn't switch to monitor resolution" error. Actually Win8 just crashes (no specific errors), but I suspect it's for the same reasons.

Have tried V Synch both on and off.

EDIT: Came down to Vsync. Our game sets it at launch, but apparently too late for OVRManager to care.

I'm going to be doing some more testing with Unity 5 and the 0.6.0 SDK and the same machines, and a lot of combinations of things. But curious if anyone already solved this one.

Thanks!

C

cybereality

Inspiring

It could just be that old version of Unity. It's recommended to be on the latest 4.6.x version. Unity 5 can work (with some small changes) but there are a couple of outstanding issues so it's not as solid as 4.6 right now.

X

xhonzi

Up and Coming

I figured that would be the first answer. We don't have the option of moving forward to a later version of Unity. Either I'll figure out the issue with SDK 0.6.0, or I'll fall back to an earlier SDK.

X

xhonzi

Up and Coming

I created a branch of our project on 4.6.5 to see if these errors would go away. They didn't. (I did remove my hacked SDK and replace it with a fresh copy of OVR Unity 0.6.0)

In fact, I now get the resolution errors on my dev PC as well. So that didn't work. (Editor is still great everywhere, it's just builds that won't run)

EDIT: Okay, I found my problem with Unity 4.3- In our settings, we allow users to choose between 4 Quality settings- and VSync was only defaulting to ON in the highest. Game defaults to second highest setting, and only Devs with nicer cards were setting it higher. Even so, users can override Vsync settings from our settings menu too, but apparently that setting was too late to prevent Rift from having resolution errors at startup. I can fix that.

However- I have the problem where I don't get a DirectToRift exe from 4.6 (as documented here: viewtopic.php?f=37&t=23400) or I copy one from a previous build (exe names are still the same)

How do I get it to appear on the Rift in Unity 4.6.5 and SDK 0.6.0?

---

A little about how my project is set up:
Game loads a scene called EntryPoint. This loads settings and sets up the top level stuff, before loading a new scene called MainMenu. If riftMode was true, it added the OVRCameraRig at that point (and all later scenes).

MainMenu used to have a page with the option to turn VR mode on/off. This combined with DirectToRift worked 100% of the time (prior to 0.6.0). We thought it would be better if the game could detect Rift and auto-enable Rift mode, so I tried to use Ovr.Hmd.Detect during our EntryPoint scene, but had some issues with it. That was with SDK 0.4.4. I figured I wanted to move to 0.6.0 anyways, so I did that- still had Detect issues. Realized it was because I was calling OVRManager when no such thing existed yet (in EntryPoint). Added an empty game object and added OVRManager to it.

Eureka! This makes my Detect code work! In the Editor and in the builds on my dev box. As described earlier, however, this made it not work on about half of the other PCs we tried. Turns out adding the OVRManager at this point was early enough that it was checking for VSync before our code was setting it to 1.

X

xhonzi

Up and Coming

Okay, here's the gist of what we want to do:
1· Force VSync on
2· Wait for verification VSync is enabled (usually next frame)
3· Create the OVRManager

I can't find a way to verify #2. Checking the bool just tells me that I've set it- not that it's taken affect. Any ideas?

I know I could just set VSync to on for all Qualities, but I'm being overridden. Lead Programmer thinks this way is better.

B

blenderpedia

Up and Coming

Hi There,

I have a strange crash that appears sometimes, not always. I have a build of my game that runs fine, but sometimes it crashes when launching the game,it displays the following error( bottom page). It also happens that my computer simply not recognize the HMD, i have to reboot my system for that.

I use the 0.4.4 SDK reason i'm not working with 0.6.0 is integration issues with some of my unity assets that not support 0.6.0. yet.

I have seen the 'ovr_WaitTillTime' crash multiple times in this topic, so thats why i post this here.

and also:

Unity Player [version: Unity 4.6.4f1_99f88340878d]

OculusPlugin.DLL caused an Access Violation (0xc0000005)
in module OculusPlugin.DLL at 0033:9bb67ca8.

Error occurred at 2015-06-18_100536.
C:\GVR\GVR_2.08\GVR_2.08.exe, run by Oculus.
12% memory in use.
8121 MB physical memory [7139 MB free].
9401 MB paging file [8295 MB free].
134217728 MB user address space [134217551 MB free].
Read from location 00000000 caused an access violation.

Context:

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO