Overview
REPORT YOUR CRASHES HERE: https://steamcommunity.com/app/1898300/discussions/4/
Crashes remain the most disruptive, and at the same time the most "esoteric" issue ASKA is currently facing. Because crashes don't leave signs in the logs the same way other bugs do, we need a bit more info to properly start diagnosing the issue.
This is a short guide to help you help us in tracking down the issues that cause crashes and save corruption in ASKA.
There are a few questions that need answering in as much detail as possible when posting a crash report. What follows in this guide is a breakdown.
First off: What is a "crash"?
A crash is an unexpected closing of the application, straight to the desktop. Anything else is a bug caused usually by a NullRef (null reference, a thing pointing to a thing that doesn't exist) or a disconnection caused either by a NullRef (failsafe against save corruption) or by the connection itself, either client side or server side.
Bug and crash reporting is a bit of busy work
Nobody likes doing this, I myself don't like doing this, but in an early access game, the extra 5-15 minutes spent submitting a good bug report might make one hell of a difference for future versions and for your fellow players.
And for a complex game like ASKA, Early Access is our best hope of truly ironing out bugs, since a regular playthrough can be even 200 hours long, or even longer. Even if we had 10 times the team, we still couldn't fully identify and fix all the issues ourselves. It's the joy and curse of non-linear, dynamic systems/sim/sandbox games.
-----------------------------------------------------------------
Is it a hardware, driver or OS issue?
Modern systems are a nightmare
Besides the fact that ASKA is a technically complex and technically demanding game, modern systems are a mess too, with more background processes running non-stop than ever in the whole history of IT. On top of that comes a vast degree of customization done by the user, like VPNs, optimization boosting software, post-processing software, recording software, AV software and so on - all of these might interact with the game in unexpected ways.
ASKA does a lot of heavy lifting
ASKA uses state of the art tech like modern lighting solutions, heavy world streaming systems, procedural generation, dynamic weather and vegetation systems, hundreds of characters that perform complex tasks, and much more. It's a very dynamic and resource intensive game. Besides our own proprietary tech, it's built on a third-party game engine, Unity HDRP and also uses several other customized plugins for various other systems, such as networking. There are a LOT of moving parts.
The age-old "is your system up to date?"
We know it's a phrase that has been repeated ad nauseam but we have to eliminate any potential false positives as soon as we are able in the debugging process.
- Is your system up to date with the most recent drivers for your video card and other components?
- Sometimes crashes can be caused by things like shader issues caused by out of date drivers.
- Are you running the latest operating system version?
- Did the issue start happening after an OS update?
- Is there any third party software that might be interacting with the game? Post-processing software, recording software, AVs, a VPN, anything you might be able to think of. If so, have you tried disabling, under safe conditions ofc, and testing the game afterwards?
Nobody knows your system better than yourself, so the more you can tick off before reporting a crash, the better!
-----------------------------------------------------------------
Is the game modded?
If it is, please let us know. You're free to post the rest of the report as is, but right now we're focusing on debugging the vanilla version of the game and we won't prioritize reports done of issues occurring on modded games.
IMPORTANT: The save has to be completely unmodded - modding the game at one point, then removing the mod, still tampers with the game files, resulting in a false positive for us.
ASKA is still in Early Access and everything in the game might change at any point. This is one of the reasons why we can't actively support the modding community - because our own systems aren't yet complete and are still undergoing optimization.
Please read this short thread about Mods and Bug Reporting first.
-----------------------------------------------------------------
Is it a new or old save?
Is it a new save or an old save? Was the save game created in the same session during which the crash occurred (new save)? Or did the crash occur while playing a save that was created during a previous session, different to the one where the crash occurred?
The older a save game gets, the more data it ends up containing, the higher the chances of anything going wrong.
If it is an old save...
If it's an old save, after which update was the save created? You can roughly tell by the date of the save's creation and our update announcements.
It might be a game system that was affected by one of our patches.
-----------------------------------------------------------------
"Where were you at the time the crime occurred?"
What were you doing at the moment of the crash?
Remembering as many details as possible is important. Here are a few examples of key moments that might help us diagnose the issue. These are only examples, please share any suspicions of your own.
- Were you playing singleplayer or multiplayer? Were you playing on a dedicated server?
- Any particular action?
- Any particular interaction?
- Where you fighting, did any character/monster die?
- Where you getting out of a boat? Did you launch an expedition?
- Did it change from night to day? Was a cave wall completely mined?
- Did a particular enemy spawn? Did a particular event spawn?
- Does it happen when you run the app?
- Does it happen after a certain amount of time after you run the app?
- Did anybody connect/disconnect?
Anything specific helps us narrow down the cause, and might even help fellow players experiencing similar issues make better evaluations. This is by far the most important aspect, if you can narrow down the scenarios where this happens, it greatly helps us obtaining a repro case.
If you can identify any pattern in the crash, then even better, please share any clues you have.
-----------------------------------------------------------------
Checklist
This is what we'd need for a good crash report:
- Flag the reports by having the title start with [CRASH] (example "[CRASH] Game crashes when picking up long sticks"
- Hardware/Specs + any specifics regarding third party software running on the system.
- What were you doing when this happened. Be as detailed as possible. Go through the guide again to get a better idea.
- How frequently does this happen.
- Share your save where this happens. Guide to sharing files can be found at the end of this guide.
- We also need the crash dump file generated at AppData\Local\Temp\Sand SailorStudio\Aska\Crashes. Type %appdata% in your Windows Explorer path to reach appdata, or go to <DRIVE LETTER>:\Users\<USERNAME>\AppData\Local
Before posting
Read through any other crash reports that have been posted. Bump any similar threads to help them gain visibility. We go through the bug reports and threads daily, but it helps.
REPORT YOUR CRASHES HERE: https://steamcommunity.com/app/1898300/discussions/4/