Well, I tell ya'. There are a lot of reasons for lots freezing/crashing with custom content in them. I find the larger the lot, the more frequently this occurs. I've also been fighting with EA forever about a problem with the game either writing illegal/incorrect instructions to graphics cards with DirectX, or mishandling older custom content. EA won't verify either, they blame nVidia who says there is a memory leak and BV asks for the driver-version in the wrong way, but it took too much energy to fight them when this problem got out-of-hand with Pets. I had to threaten them with negative publicity, so nVidia helped EA out and created Beta 162.18 during Seasons. When BV came out, this problem was alive and well all over again
, and now ATI-users have problems but less often than nVidia-users. I have to use
boolprop useshaders off to play without all lots crashing within 5 minutes, and that takes away seeing lots of details in the game. Some of my lots don't crash at all, but the commonality with the ones that do is that they are large, and have a fair amount of custom content. I know it's not my CC, because I know what I've added since Seasons, and 100% worked perfectly fine after the 162.18 nVidia patch. Since I practically got the crap beaten out of me by EA, and ended up shunned by the Sr. Developer, I'll not tackle them alone again. So, if only 1 lot is doing this, most likely it is a CC object (or hack that isn't working correctly). My guess is the all-famous graphics problem caused by this game which affects previously-working CC, and nobody knows what it really is!