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
Start a new map with only a very few obvious terrain changes then save quit and restart editor with new map to check editor.
If that doesn't work it's likely a conflict or memory issue and you should try holding out for someone who has a better suggestion. OR consider doing a file backup and clean reinstall to correct the problem. Not a happy thing to think about I know.
The Mod D:\Steam\steamapps\workshop\content\255710\497439640 [RandomTerrainGenerator.dll] has caused an error [ModException]
Details:
System.NullReferenceException: Object reference not set to an instance of an object
at RandomMap.Loader.OnLevelUnloading () [0x00000] in <filename unknown>:0
at LoadingWrapper.OnLevelUnloading () [0x00000] in <filename unknown>:0
- Under the General tab click the Set launch options... button.
- Enter the launch options you wish to apply (be sure to separate each code with a space) and click OK.
- Close the game's Properties window and launch the game.
As for the error, I recommend you remove the Random Terrain Generator mod. It hasn't been updated in 5 years and seems like it's broken.
Crashing could very well be your game running out of RAM. And easy way to test that is to also add the launch option -noWorkshop so the game runs as complete vanilla. If it runs fine then, the crashing is likely due to running out of RAM from having too much workshop content.
If you haven't already set a nice large pagefile, then I recommend doing that. Setting it to 32GB helps the game run much smoother and results in less crashing. This guide explains how to change the pagefile.
https://steamcommunity.com/sharedfiles/filedetails/?id=2114415052&searchtext=pagefile
Depending on the amount of RAM you have, you might also want to lower the amount of workshop content you have. Here are some average numbers for what you are expected to be able to run with different amounts of ram:
4GB: 0-10 assets
8GB: 100-400 assets
12GB: 400-800 assets
16GB: 800-1200 assets
24GB: 1200-2000 assets
32GB: 2000-2800 assets
64GB: 2800-6000 assets
If you have any of the major DLC's or content creator packs, reduce the asset count by another 400 each. Each DLC adds about 250-400 assets to the game.
thank you this worked, I was able to start up the game, save it, and load it without corruptions. About the asset thing I was wondering if there was any way to find specific mods and workshop assets that cause the problems because I dont know if I can play the game with houndreds or thousands of deleted assets.
It isn't really about a few problem assets or mods though, it's about the amount in total. You can look for unoptimized assets or remove ones with larger textures/filesizes - then you'd have to remove less. The mod MeshInfo lets you sort assets by their texture size, and textures are what account for most of the filesize.
Ofc larger buildings use larger textures, and sometimes it might be worth keeping something more detailed. That's all up to you and what you need the most in your city. I have some general guidelines to give you an idea of what sort of texture sizes are considered optimized for different types of assets - it's a bit old and we have since had the ability to add subbuildings to make very large buildings, so unique buildings can go above this just fine if they're large and consist of multiple parts.
https://i.imgur.com/2qeSaR7.png
Even though the game is working for you now with the pagefile, it still might be good to take a look at assets. Just getting rid of stuff you subscribed to but have never used and probably won't use is a good plan. Sometimes I end up with stuff that I have newer and better options for, but I forgot to remove the old. A little spring cleaning of assets from time to time is good. :)