Crashing on Loading a Saved Game

August 9, 2021

Branch: Live Branch

Version: Windows

Fixed

Just like the title said, loading a saved game and it crashed. I try to disable all mods and still got the exact same error info:

-----------------------------------------------------------

Assert failed: Implementation does not support multiple components with optional components, type OrbitalMechanics, 1, 0

at UnityEngine.Debug.LogError (System.Object message) [0x00000] in <9fe2cbebfa394c8da6af069ec8cc9ef4>:0
at Debug.LogError (System.Object obj) [0x00000] in <7110358c02a14df2a7a2562defcc57da>:0
at Debug.Assert (System.Boolean condition, System.Object message) [0x00000] in <7110358c02a14df2a7a2562defcc57da>:0
at SaveLoadRoot.LoadInternal (UnityEngine.GameObject gameObject, IReader reader) [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at SaveLoadRoot.Load (UnityEngine.GameObject prefab, UnityEngine.Vector3 position, UnityEngine.Quaternion rotation, UnityEngine.Vector3 scale, IReader reader) [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at SaveLoadRoot.Load (UnityEngine.GameObject prefab, IReader reader) [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at SaveManager.Load (IReader reader) [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at SaveLoader.Load (IReader reader) [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at SaveLoader.Load (System.String filename) [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at SaveLoader.OnSpawn () [0x00000] in <34596b94026340528c5a12b9fac008f1>:0
at KMonoBehaviour.Spawn () [0x00000] in <7110358c02a14df2a7a2562defcc57da>:0
at KMonoBehaviour.Start () [0x00000] in <7110358c02a14df2a7a2562defcc57da>:0
Build: U33-473720-SD

-----------------------------------------------------------

No idea what it means but I think you guys may need it to dig into the issue

Steps to Reproduce

-open up oni from steam

-resume game

-the error info shows up

Med Game 004.sav

Followers 0

Go to bugs

User Feedback

3 Comments

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.