The fact that you only crashed once doesn't necessarily mean it's fine afterwards. Originally posted by ElanaAhova:BTW, it crashed first time I quit to menu (to get a different start map), after that it doesn't - go figure. Old mods don't go away by themselves, which is part of the problem. There should be one ModEnabled and one ModIndex line for each mod you have used. In my Win 10 64 bit set up the Banished section of the Registry is under HKEY_CURRENT_USER\Software\Shining Rock Software LLC\Banished. That seems to clear out any cobwebs in the program's brain. If you are comfortable editing your registry and know enough not to screw up your Windows installation, it is often good if you are changing mods to use regedit to delete the ModEnabled and ModIndex lines from the Banished entry in the registry.
But those crashes mainly come when you "quit" a map and try to go immediately to a new map, not on start-up. I don't get near as many crashes from CC as from other map-altering mods, but that might be one issue. Over the years I have found that the mods that most consistently lead to crashes are those that alter map perameters. On Steam I think you have to set Banished to download betas to download it automatically. If the current version of CC won't work, check to see that you have version 1.0.7 of Banished. Some old mods won't work with 1.0.7 and some new mods won't work with 1.0.6 and older. It does require the 1.0.7 version of Banished. I've never had a problem with Colonial Charter. Then I can start Banished without doing a restart for the whole computer. Everytime Banished crashes (not as often as it once did, but it happens) I fire up Process Hacker and terminate the executable. With the process manager you can terminate a program that won't behave-be careful that you know what you are terminating. Currently I use the freeware program Process Hacker. Since I've been gaming (longer than I care to tell) I've used a process manager.
0 kommentar(er)
