This object is in archive!
Crash on every startup
Solved
I bought the ultimate bundle from steam on the 26th, and from the first attempt the game crashes immediately after showing the splash screen.
I've reinstalled twice, verified several times, unchecked all the dlc's, reinstalled my gpu drivers. There never was a spaceengineers.cfg to delete. I've deleted the entire appdata\roaming\spaceengineers folder several times. I've reinstalled the MS visual c++ distributables.
I'm working my way back through the betas. Currently at 1.192 and getting the same error.
I've attached the 2 log files & minidump. (From up-to-date version attempts)
Files:
SECrashes.zip
I have the same bug
FIXED
Somehow steam was defining my game library folder as "c:\progra~2", rather than "C:\Program Files (x86)". None of my other games have a problem with it, but SE did. I simply stopped steam and changed every reference from 'c:\progra~2\steam' in my registry to "C:\Program Files (x86)\steam". (There are also some using the opposite slash, ie "c:/program files (x86)/steam" that I changed as well.
SE then loaded and ran properly.
FIXED
Somehow steam was defining my game library folder as "c:\progra~2", rather than "C:\Program Files (x86)". None of my other games have a problem with it, but SE did. I simply stopped steam and changed every reference from 'c:\progra~2\steam' in my registry to "C:\Program Files (x86)\steam". (There are also some using the opposite slash, ie "c:/program files (x86)/steam" that I changed as well.
SE then loaded and ran properly.
At version 1.191 the error has changed from "Exception occured: System.NullReferenceException:" to "Exception occured: System.InvalidOperationException:"
At version 1.191 the error has changed from "Exception occured: System.NullReferenceException:" to "Exception occured: System.InvalidOperationException:"
I'll discontinue the updates after this, but 1.190 seemed to run longer, produced a different log and complained about a specific file:
2020-12-28 16:36:44.347 - Thread: 1 -> DEFINITION_CRITICAL_ERROR:
2020-12-28 16:36:44.347 - Thread: 1 -> in file: C:\Program Files (x86)\Steam\steamapps\common\SpaceEngineers\Content\Data\MainMenuInventoryScenes.sbc
2020-12-28 16:36:44.347 - Thread: 1 -> MOD PARTIALLY SKIPPED, LOADED ONLY 2/6 PHASES, Following Error occured:
Object reference not set to an instance of an object.
I verified the install again, but got the same error on the same file.
I'll discontinue the updates after this, but 1.190 seemed to run longer, produced a different log and complained about a specific file:
2020-12-28 16:36:44.347 - Thread: 1 -> DEFINITION_CRITICAL_ERROR:
2020-12-28 16:36:44.347 - Thread: 1 -> in file: C:\Program Files (x86)\Steam\steamapps\common\SpaceEngineers\Content\Data\MainMenuInventoryScenes.sbc
2020-12-28 16:36:44.347 - Thread: 1 -> MOD PARTIALLY SKIPPED, LOADED ONLY 2/6 PHASES, Following Error occured:
Object reference not set to an instance of an object.
I verified the install again, but got the same error on the same file.
Hello, Chris,
Thank you for your information, SpaceEngineers.cfg should create in your Space Engineers Roaming file. I see that you are using Windows 7 as OS. Could you please check if it's fully updated? Any additional information will be greatly appreciated.
Thank you.
Kind Regards
Keen Software House: QA Department
Hello, Chris,
Thank you for your information, SpaceEngineers.cfg should create in your Space Engineers Roaming file. I see that you are using Windows 7 as OS. Could you please check if it's fully updated? Any additional information will be greatly appreciated.
Thank you.
Kind Regards
Keen Software House: QA Department
Yes, it's fully updated. The only updates for quite a while now have been for windows defender definitions.
Yes, it's fully updated. The only updates for quite a while now have been for windows defender definitions.
I'm wondering why this is still flagged 'need more information', despite me having answered.
I'm wondering why this is still flagged 'need more information', despite me having answered.
FIXED
Somehow steam was defining my game library folder as "c:\progra~2", rather than "C:\Program Files (x86)". None of my other games have a problem with it, but SE did. I simply stopped steam and changed every reference from 'c:\progra~2\steam' in my registry to "C:\Program Files (x86)\steam". (There are also some using the opposite slash, ie "c:/program files (x86)/steam" that I changed as well.
SE then loaded and ran properly.
FIXED
Somehow steam was defining my game library folder as "c:\progra~2", rather than "C:\Program Files (x86)". None of my other games have a problem with it, but SE did. I simply stopped steam and changed every reference from 'c:\progra~2\steam' in my registry to "C:\Program Files (x86)\steam". (There are also some using the opposite slash, ie "c:/program files (x86)/steam" that I changed as well.
SE then loaded and ran properly.
Replies have been locked on this page!