Skip to main content
Up and Coming
August 23, 2014

Editor ok, Build crash

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.

    37 replies

    New Participant
    November 20, 2014
    I rollbacked my graphics drivers to 344.48 to see if it was my graphics drivers that created the issue. It didn't fix the existing project but when I created a new project it didn't crash.
    So I created a new project as well and imported my scripts and remade my scenes (they are very small) and that fixed it. I built a new build for every new scene created and took backups. When I imported a texture to use as default icon for the game the game crashed. I removed the texture and it started to work again. But I do have skybox on all my scenes so it's really strange. I haven't had time to check the texture yet (working on another project aswell).
    In my project settings I did click Default is full screen and D3D9 Fullscreen mode as FullscreenWindow.

    I'm on
    Win 8.1 x64
    Nvidia GTX 870M
    Unity 4.5.5
    Oculus SDK 4.3.1
    Leap motion SDK 2.1.6
    Participant
    November 20, 2014
    Same here.
    Ok in Editor, Crash when run.

    W7 64bit
    Nvidia GTX770 Driver 344.65
    i7-4770 3.4Ghz 16Gb RAM
    Unity Pro 4.5.2f1 but I tried others versions with the same resut
    Oculus Runtime 4.3
    Unity SKD 4.3.1
    32bit Build

    Same executable in another PC also crash.


    With Runtime 4.2 & SDK 4.2 don't crash.

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

    (0x5707BA9C) (OculusPlugin): (filename not available): ovr_WaitTillTime + 0x61cc
    (0x57083817) (OculusPlugin): (filename not available): ovr_WaitTillTime + 0xdf47
    (0x5707538E) (OculusPlugin): (filename not available): ovrHmd_GetTrackingState + 0x3e
    (0x0462E801) (Mono JIT code): (filename not available): (wrapper managed-to-native) Ovr.Hmd:ovrHmd_GetTrackingState (intptr,double) + 0x39 (0462E7C8 0462E83C) [010E4E70 - Unity Root Domain] + 0x0
    (0x0462E795) (Mono JIT code): (filename not available): Ovr.Hmd:GetTrackingState (double) + 0x25 (0462E770 0462E7B7) [010E4E70 - Unity Root Domain] + 0x0
    (0x0462E746) (Mono JIT code): (filename not available): OVRDisplay:get_isPresent () + 0x3e (0462E708 0462E763) [010E4E70 - Unity Root Domain] + 0x0
    (0x0462E4BE) (Mono JIT code): (filename not available): OVRManager:Update () + 0xce (0462E3F0 0462E5CE) [010E4E70 - Unity Root Domain] + 0x0
    (0x045CE629) (Mono JIT code): (filename not available): (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr) + 0x41 (045CE5E8 045CE67D) [010E4E70 - Unity Root Domain] + 0x0
    (0x100F00B6) (mono): (filename not available): mono_set_defaults + 0x22bf
    (0x1005D6DF) (mono): (filename not available): mono_runtime_invoke + 0x51
    (0x01275C38) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x28748
    (0x01310DC6) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0xc38d6
    (0x01310BD5) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0xc36e5
    (0x012689FB) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x1b50b
    (0x01268A71) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x1b581
    (0x01268A87) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x1b597
    (0x012DF559) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x92069
    (0x01353E4B) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x10695b
    (0x0135566B) (CarretillaDemo): (filename not available): Behaviour::Transfer<SafeBinaryRead> + 0x10817b
    (0x015BE948) (CarretillaDemo): (filename not available): AnimationEvent::Transfer<StreamedBinaryRead<1> > + 0x119b28
    (0x015F3830) (CarretillaDemo): (filename not available): AnimationEvent::Transfer<StreamedBinaryRead<1> > + 0x14ea10
    (0x7708338A) (kernel32): (filename not available): BaseThreadInitThunk + 0x12
    (0x77B09F72) (ntdll): (filename not available): RtlInitializeExceptionChain + 0x63
    (0x77B09F45) (ntdll): (filename not available): RtlInitializeExceptionChain + 0x36

    ========== END OF STACKTRACE ===========
    Joaquin Gracia ITAINNOVA - Multimedia Technologies
    Inspiring
    November 20, 2014
    I tried updating my graphics drivers to latest and turning on Vsync to see if it would make a difference, but unfortunately the application still freezes and needs to be killed from the task manager.

    Here are my system specs according to the Oculus debug logging. Could the DameWare Mirror Driver be causing an issue?

    "System Specifications": {
    "Operating System": "Microsoft Windows 7 Enterprise ",
    "Processor": "Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz",
    "Video Controller Name": "DameWare Development Mirror Driver 64-bit",
    "Video Controller RAM (MB)": 5,
    "Video Controller Name": "NVIDIA GeForce GTX 670",
    "Video Controller RAM (MB)": 4095,
    "Total RAM (GB)": 64
    },

    Other potentially useful specs:
    NVIDIA driver version 344.75
    Unity 4.6.0f2
    Oculus Unity Integration 0.4.3.1
    Project is using DX11 (crashes immediately without fail in DX9)

    Again, does not happen if I roll back the OVR Unity Integration package to 0.4.3. The exectuable crashes in Extended Mode on other PCs as well but one person was reliably able to run it in DirectToHMD.
    Inspiring
    November 20, 2014
    Turning Aero OFF (ie. switching to Windows 7 Basic theme) seems to have fixed the problem for me, which seems contrary to the advice here: viewtopic.php?f=34&t=10968&start=240
    and here:
    viewtopic.php?f=34&t=16308&p=218863&hilit=aero#p218863

    Edit: it appears I spoke too soon. I was able to run my demo once for several minutes without freezing, but now it's back to freezing again.
    Inspiring
    November 20, 2014
    @JoaquinGM: You may have an old OculusPlugin.dll in your project. Can you try removing all the Oculus stuff in the project and then re-importing the latest integration files?
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    Up and Coming
    November 21, 2014
    Just chiming in to say that I've just had the same issue trying to update a project from 0.4.2 to 0.4.3.1 (crashes on loading any build) and I seem to have got round it with the method mentioned above - ie. creating a new project, copying the assets folder to it and building from there.

    In the absence of a full solution, this was a lifesaver of a suggestion.
    New Participant
    November 21, 2014
    When I created a new project and reimported all assets and got it running it was all fine, until I copied the built files to 4 other computers with updated graphics drivers. The scenes crashed on all of the computers except the one that have rolled backed drivers.

    My other computers have
    Nvidia GTX 780 and 780 Ti with driver version 344.75
    November 21, 2014
    Switching to DX11 seems to have done it for me -- DX9 builds constantly crash, DX11 builds never do. The 'Don't VSync' fix I mentioned earlier is no longer working in DX9.
    (Win 8.1 64, i7, Nvidia 750M, driver version 344.75)
    Up and Coming
    November 30, 2014
    Add me to the list of sufferers.

    (Win 7 64, i7, AMD)

    I had upgraded from 0.4.0 to 0.4.3.1 and had a very sluggish Rift. Looked like motion blur. I went and cleaned out my Plugin directory really well and reloaded the 0.4.3.1 SDK. Now I get the working editor- crashing build about 90% of the time.

    I don't really have the option of going to dx11 or starting a new project.

    HELP PLEASE!
    Up and Coming
    December 2, 2014
    Anyone find a fix for this??? I just updated to the new unity integration and now I have game crash. If I start a fresh project its ok but I don't know how to transfer all my scenes over right. I forced dx11 and that seemed to help but a error pops up first, if you x out of the error it plays SOMETIMES. wtf!