Fatal Errors

[Demonslayer93]

Since updating my game I've had issues getting onto any servers, both with official and private my game keeps crashing during the initial server loading screen. This issue has persisted for the last 3 hours almost.

Any help on how to fix this? I have already attempted restarts/verifying files.

Edit: This was initially only referring to online servers, however have experienced the same with single player too.

Edit 2: Going on 5 and half hours now, multiple PC restarts, game relogs, verification of game files, troubelshoots... Still getting fatal error and crash when trying to load into any server/single player game.

[AnubisMe]

same problem. I will wait a week and see if this has been fixed.

[Amber]

If you haven't already Always Verify Integrity. I have to do it every single time a update hits lol.

[Demonslayer93]

Originally posted by Hexi:

If you haven't already Always Verify Integrity. I have to do it every single time a update hits lol.

As mentioned before, I have already done this along with numerous restarts/relogs.

[WebAugusto]

same problem.

[Demonslayer93]

Originally posted by AnubisMe:

same problem. I will wait a week and see if this has been fixed.

Originally posted by WebAugusto:

same problem. :witch:

Did either of you manage to get a fix for this? I am still having issues even after re-installing the game itself multiple times and redoing verifications etc.

[Cosmic Cat]

What kind of error message do you guys get when it crashes?

[Demonslayer93]

Originally posted by SLM:

What kind of error message do you guys get when it crashes?

fatal error:
[file:c:/B/tech_exiles/code/engine/source/runtime/coreuobject/private/serialization/asyncloading.cpp] [line: 3485]
could not find superstruct useSRGB to create useSRGB

That's what mine says when trying to load into official server, or any other server for that matter

[His Left Tentacle]

same here. 3 fatal errors in 1 h.

OMG FUNCOM! Not again... dont you guys test???

[Demonslayer93]

Originally posted by His Left Tentacle:

same here. 3 fatal errors in 1 h.

OMG FUNCOM! Not again... dont you guys test???

I'm on my third re-install and file checking of the last 24 hours, hopefully it's worked this time

[Demonslayer93]

Still having the issue after three re-installs, clearing cache, repairing files, many many verifications

[Demonslayer93]

It took a lot of time and retries with installations verifications and file checking, but managed to get on guys! Just have to keep at it so it seems... Good luck to those still trying.

[pwillie]

had this error three or four times yesterday. Verified game files and re-logged steam client seemed have fixed. Fingers crossed.

[Mofo]

My fatal errors are so random it's so annoying.

Using admin teleport, crash.
Ordering my thralls to drink aloe extract, crash.
Outfitting my thralls, crash.
Poking exiles with spear, crash.
Dead? Crash indeed.

[SuperNinja705JPS]

same problem happens randomly

[Estevan Valladares]

That error has nothing to do with "Funcom".
That error happens when a non serializable type is used in a serialized variable, and that happens ALWAYS when a mod does it, because Funcom's own variable types are serializeable because they are declared BEFORE the content is loaded. When you have a mod, the game has already loaded the DB before loading your mod, so you cant use direct serialization with custom types made by you.

This problem often occurs when you use a mod that store data customized, which is common for mods using custom classes, custom appearances that are not originally in the game (instead of using the character layout type, they create one of their own).

This specific error often occurs when you use a mod that creates new character colors (skin, eyes, etc) and store it, then during an update, the mod cant rebuild that correctly before being updated itself, and then it triggers that error.

That is one "case", but the specific serialization error ALWAYS occur when a mod uses custom types. Again, Funcom types are not "custom" so they dont trigger that specific error.