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
Based on what?
But what crashes the game, client, and sometimes the server, is when someone tries to serialize sRGB data in a mod to store it in a variable type that is not serializable. That causes a fatal error.
Even if you remove the mod that caused the error, it might persist if the database you are using was saved with the incompatible struct in the mod, then when you remove the mod, it still tries to load data that has no struct to be deserialized.
It would be very unlikely that sRGB mentioning error would be caused by the core game, because all the structs of the native game are loaded before its values are used. Which does not happen when a mod does its own structs.
Unless the error is elsewhere, also not in the core game, but in something else interacting with game data.
But the most likely reason is either mods or some other incompatible software like drivers or etc. If you said you are running the latest drivers, the other thing that might cause crashes mentioning sRGB, it must be mods.
That's helpful to know, thanks. I'll take a look at my current mods to see what's causing it.