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
Best is to unsubscribe from all custom assets - or at least those ones which have not been updated since the last patch or even since the last 2 patches.
My assumption is based on those two lines:
* Colossal.IO.AssetDatabase.PrefabAsset:Load()
it literally says that the problem occurs in the asset/prefab loading routine
* NullReferenceException: Object reference not set to an instance of an object
at Colossal.IO.AssetDatabase.PrefabAsset+PrefabReferenceResolver.TryResolveReference
here it's the same, there is something off with your asset database, it has resolving problems,
Theory:
It seems that something has been changed ingame recently regarding assets. Maybe because of the region packs. Therefore all mods which have not been updated to those recent changes might have become more or less incompatible and should no longer be subscribed to.