Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Start by posting your system specs and then the complete crash report.
If you're using any mods, then post the mod names (the names, not the workshop ID numbers) and their loading order.
Also a small tip, when you see a crash report that mentions specific files I recommend you NOT delete them. As someone on here frequently says, crashes are symptoms of something else, not causes. If you had a problem with a car, you wouldn't open the hood up and just disconnect a random engine part and throw it away. Those files are there for a reason.
Nothing really leaps out. The crash reports are just a blow by blow recounting of what the game was trying to do, before something happened. Doesn't really tell you what actually happened.
One thing I do see is repeated mentions of "tick". One possible cause of the crash might be corrupted data on something that the game is trying to load. The problem is that it won't list what it was loading... just that it was trying, and it crashed. It could be a corrupted creature, a building part, anything.
If it's corrupted building parts, that's very hard to fix. As soon as you get withing render range, and it tries to load it, the game hits the corrupted information and it will crash. Basically if it "sees" it, it dies.
Corrupted creatures are slightly easier to fix. You can use admin commands like "playersonly" to turn off the AI process of some creatures. The creature will be rendered, but frozen. It won't move, act normally, etc. This often allows you to get close enough to use admin commands to delete it. The problem is that you still need to determine which creature (if any) is causing the problem.
The last one I ran into was a corrupted mosasaurus. Soon as I came within render range, it instantly crashed my game. I could zoom all over the map, but getting within sight of this one mosa was a crash. I could approach the nearby base from the west, south, and north. But approaching from the east (passing over the water) crashed my game. There was only a single tame in the water, being the corrupted mosa. I used playersonly to freeze the ai, and then I remember this one mosa had something weird: it showed no imprinting. at all. Not imprinting at 0%. The entire line where imprinting would be mentioned was just absent. I deleted that mosa. problem solved.
But often times, it's going to be quicker to just load an older snapshot save and see if it eliminates the corruption. Since we don't know that corruption is even the issue (that's just a guess by me), and then there's the difficulty of trying to find out what specific item is causing it.
1. Deleting the files you mentioned wasn't wise. They're integral parts of the game and you're just ensuring more issues. Seeing a crash at that point in the loading is not equal to it being the source of your crash. In other words the perceived correlation does not equal causation.
Due to that you first should verify the integrity of local game files to ensure all files are properly installed for play.
2. Next, crashes are symptoms, not causes and yes, your management of how you play is one of the more common sources of why you can crash but it can also be to other reasons OR even a recipe of them both.
To that end:
--Go to the steam help menu, click system information and then copy paste all that information here so we can see specifically what steam detects for your rig and any potential discrepancies that may have diagnostic relevance.
-- If you are using mods, list all mods by name and in the specific load order.
-- If you are using any launch parameters, remove them, most these days are obsolete and can cause issues also.
3. As you surmised, yes even once we pinpoint the potential source(s) for your issue and any possible solution(s), it may not rescue your game save as they can often be corrupted beyond repair(especially due to mod use). In such cases you would need to make a fresh new save, being more mindful of your mod choices/load order if deemed bad, settings etc.
Best of luck.