Skip to main content
molton
Up and Coming
January 6, 2015

Unity 4.6.1 build crashes

Is anyone else here having build crashing problems after upgrading Unity to version 4.6.1? Specifically I'm using 4.6.1 f1, Sometimes builds crash at what seems like the first frame, but other times it happens at random. I was using Unity 4.6.0 beta 21 before I installed 4.6.1 and did not have these problems at all.

I have to test it further, but it seems like direct-to-rift does not cause the crashes, only the non-direct executable file, but I'm not sure about that.

Also, it's happened without FRAPS up, but having FRAPS up seems to make the problem worse.
    This topic has been closed for replies.

    4 replies

    cybereality
    Inspiring
    January 6, 2015
    Can you check if Unity give you a crash log?
    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
    moltonAuthor
    Up and Coming
    January 7, 2015
    No, it actually never made one of those crash reports, I got an output.log but that's been overwritten by now. Also, I think it was something that restarting Windows fixed because I have not experienced it since a restart in Windows, I guess a restart after installing 4.6.1 would have made my problems go away. Now that I said that next time I test it it will probably crash again :) It probably didn't help that I just installed the Unity 5 beta on there right before upgrading unity 4.
    cybereality
    Inspiring
    January 7, 2015
    Yes, please check the output log if this happens again.

    It's a little difficult to trouble-shoot without more information.
    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
    moltonAuthor
    Up and Coming
    January 7, 2015
    Thanks, will do. I was thinking maybe other people were having the same problem, I honestly really didn't know about the output.log file until just now, good to know about that for sure.
    Terms & ConditionsAccessibility statement