Jump to content

ONI crashes on startup, unity error


FrankT
  • Branch: Live Branch Version: Windows Fixed


Yesterday ONI got an update via steam, the game shows unity error on startup and stops since then.

What I did:

- deinstalled game, removed all settings
- reinstalled game (ONI w/ Spaced Out DLC)
- no mods installed
- switched steam overlay off (found in another thread)

nothing helps.

Win 10 Pro & graphics driver are up to date.

Attached .zip contains:

- oni_unity_error.jpg
- crash.dmp
- OxygenNotIncluded.exe.840.dmp (from ...\AppData\Local\CrashDumps)
- DxDiag.txt
- Player.log

No current saves available, crash occurs before loading anyway.

I hope, you can help - I want my dupes back :)

Thank you in advance, Frank

 


Steps to Reproduce

Nothing but start the game and wait until the error message shows up.

No other apps running except steam client.

 




User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

I get the same thing. Sometimes it crashes on startup, but mostly it crashes when loading the most recent save, which was a few hours ago. I did the recent hotfix, the small file, and it is causing this issue 95% likely. 

 

 

Share this comment


Link to comment
Share on other sites


@EricKlei

No changes to BIOS or hardware, OS (Win 10 Pro) got updates.

After switching to public_previous_update branch and updating, ONI starts again, and I could create a new game.

I hope you can find out the reason why the current version doesn't start. If you need any more information, please let me know.

My dupes are back, I'm happy :)

Thank you very much,

Frank

 

Share this comment


Link to comment
Share on other sites


I switched back today to the default branch, and after updating ONI runs!
I'm curious: Is it the identical version as of 11/28, or did you change something?

Thank you very much,

Frank

 

Share this comment


Link to comment
Share on other sites

Changed Status to Fixed

There was a hotfix on November 29th but it contained nothing that would've fixed this. Still not sure what happened but glad it's fixed.

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...