over the past few days I have been dealing with regular complete freezes of the game. I am still able to ctrl/alt/del out of it and have been slowly figuring out what's causing it; but this has been a lot more tedious than a usual half by half because the freezing isn't immediate. Nonetheless I believe I have found my culprit and it's the BSC regional counter.dat. It resides in my regular plugins folder (not datpacked), and has previously been working fine. I guess I'll have a go with a fresh copy but just thought I should mention it... I certainly don't want to lose it from my setup.
this post of theteacat's I found in the CAM general discussion thread sounds similar...:
Quote from: TheTeaCat on August 11, 2007, 09:39:32 AM
I have been experimenting with the CAM over the last few days and often the game stalled for want of a better word. Not even ctrl+alt+del worked. A complete reset was required. I figured out what was causing it though.
It only happened in a region that is being tracked by the BSC regional counter. It didn't matter even if was the very last file to load in its own "zzzzzzz folder" yes that many z's to make sure ;) Once the population reached above 30,000+ it was more likely to happen. If you tracked one city and none else it was a guarantee to happen.
this I did on over 20 attempts with the mod included and 20 without. Each time building the city from scratch
Without the tracker installed in the plugins folder (and its location in the plugins folder didn't matter even if loaded before the cam or not ( this too tested to death ::) ) ) the game runs fine if you are using the cam.
But once you start playing with it and you do use CAM the game would freeze. Has any one else encountered this?
@thingfishs
Was it the regional counter.dat freezing the game. My game is also freezing usually 10-15 minutes into playing. This also after I installed a clean setup of NAM May 2010, NWM, Tulep and other NAM toys on May 26 2010. Funny thing though, the music still plays as if the game is still playing.
sorry for the late reply, I must have missed this one. Yes it was the regional counter doing it, but I'm sure you've figured it out by now.
Actually it was my motherboard capacitors bursting from the heat of a faulty heatsink.