When I tried looking into artifacts just now in Q1-296878 (I never saw them mentioned by anyone yet), ONi stopped responding when I wanted to debug land it. Since it is not a crash ONI seems to report itself, I wanted to upload the output log but it turns out I can not find it in all of \Steam\steamapps\common\OxygenNotIncluded (and for sure not the _Data folder either).
I even removed all of my mods (reinstalled) which all should never interfere with rockets (I even made the bottom corners of the map into Neutronium) but alas, while it successfully brought back nothing of interest, the second time it still stopped responding.
This is what Windows says, maybe it helps, probably not but it is worth a try (please excuse my French, er, German):
Problemsignatur:
Problemereignisname: AppHangB1
Anwendungsname: OxygenNotIncluded.exe
Anwendungsversion: 2018.2.7.48424
Anwendungszeitstempel: 5b87f546
Absturzsignatur: 92cb
Absturztyp: 0
Betriebsystemversion: 6.1.7601.2.1.0.256.1
Gebietsschema-ID: 1031
Zusätzliche Absturzsignatur 1: 92cb6d0b4059fcac6b452d35d4e3c700
Zusätzliche Absturzsignatur 2: 6361
Zusätzliche Absturzsignatur 3: 63615b6018cc06a816909dfe3c459133
Zusätzliche Absturzsignatur 4: 92cb
Zusätzliche Absturzsignatur 5: 92cb6d0b4059fcac6b452d35d4e3c700
Zusätzliche Absturzsignatur 6: 6361
Zusätzliche Absturzsignatur 7: 63615b6018cc06a816909dfe3c459133
Noteworthy is that it a save made while the rocket is in space will not determine if the game will stop responding. During several successful landings I got no artifacts (that's my humble guess unless I need a research module but it also stops the game). The game stopped responding like every 1st or 2nd time, I have yet to be able to launch it thrice. Incidentally force landing a rocket after loading is not possible for some time.
Changing destination does not help and neither making the solid cargo a research module. Last but not least, waiting normally and still the same.
The save game for what's it worth: Grounded.sav
Launch the rocket in the provided save a few times.
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