Game crashes when I try to start it.
Tried uninstalling the game, installing it again in the same and different locations on my harddrive.
Unsubscribed all the mods and tried launching game clean.
Nothing worked. If that's something mod-related, I'd appreciate hints how to clean the files.
Below the error log:
BadReadException: Could not read block - no data! (position 0x008B8A06)
Ionic.Zip.SharedUtilities._ReadFourBytes (System.IO.Stream s, System.String message) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.SharedUtilities.ReadInt (System.IO.Stream s) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.ZipEntry.HandleUnexpectedDataDescriptor (Ionic.Zip.ZipEntry entry) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.ZipEntry.ReadEntry (Ionic.Zip.ZipContainer zc, System.Boolean first) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.ZipFile.ReadIntoInstance_Orig (Ionic.Zip.ZipFile zf) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.ZipFile.ReadIntoInstance (Ionic.Zip.ZipFile zf) (at <c5d6b36976e845b59baec1498be897f9>:0)
Rethrow as ZipException: Cannot read that as a ZipFile
Ionic.Zip.ZipFile.ReadIntoInstance (Ionic.Zip.ZipFile zf) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.ZipFile.Read (System.String fileName, System.IO.TextWriter statusMessageWriter, System.Text.Encoding encoding, System.EventHandler`1[TEventArgs] readProgress) (at <c5d6b36976e845b59baec1498be897f9>:0)
Ionic.Zip.ZipFile.Read (System.String fileName) (at <c5d6b36976e845b59baec1498be897f9>:0)
KMod.ZipFile..ctor (System.String filename) (at <ad882e55d8ac49379773540ee16f428f>:0)
KMod.Manager.LoadModDBAndInitialize () (at <ad882e55d8ac49379773540ee16f428f>:0)
Global.Awake () (at <ad882e55d8ac49379773540ee16f428f>:0)
UnityEngine.Object:Instantiate(GameObject, Vector3, Quaternion, Transform)
Util:KInstantiate(GameObject, Vector3, Quaternion, GameObject, String, Boolean, Int32)
Util:KInstantiate(GameObject, GameObject, String)
LaunchInitializer:Update()
Build: U48-568201-S
N/A
Happens when I try to launch the game.
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.
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 accountSign in
Already have an account? Sign in here.
Sign In Now