Lot is black/blue and can't be entered

[Keev]

I don't know if this is a download or technical problem really but anyway, here we go.

I downloaded the Build Mode - Stairs - ))) The Square Stair ((( mod (http://www.modthesims2.com/showthread.php?t=212664&c=1) which includes use of boolprop commands and entered the game. The mod showed up and it worked with no problem. I then left the game, answered yes to save and the next time I entered the game, the lot was messed up. It just shows a black area (blue when viewed from some angles), but the green icon indicating a family is still there. (Screenshot can be seen at: ). When I click on it, nothing happens (the cursor doesn't even change). I can't move the lot or the family or even bulldoze the lot. The cursor just acts as if there were no lot and nothing happens. I have no problem entering other lots, it's just this one.

I have tried to remove the download as well as all other downloads, but the result is still the same. I also followed the guide http://www.modthesims2.com/article.php?p=1110057 - It didn't help to patch the expansion packs or remove the cached files and thumbnails.

I tried to enter another lot and use the same commands and the download. I then exited/saved and reentered the game. The test lot was still working so I'm not sure wheater the corrupted lot is due to the download or it just happened at the same time by coincidence.

I'm running the game with all expansion packs and (by now) all patches installed. The only custom content used besides the stairs is the official Maxis content from www.thesims2.com.

Does anyone have an idea on how to fix it? It would be greatly appreciated.
Thank you in advance.


Kevin

[simsample]

Sounds like the savegame got corrupted- I've never experienced this myself but from what others have found, it seems that your only option is to either delete the whole hood, or else live with the hole in the terrain. Unfortunately there isn't a way to recover the lot that I know of, but the family possibly could be saved if the character files are intact... you would have to set their lot instance (in their family description) to 0 using SimPE.

[Keev]

Thanks for the suggestion, but I managed to solve the problem last night without any loss. I guess the problem was caused by my reckless use of the "boolprop constrainFloorElevation false" option. For guidance if anyoe should experience the same problem and find this post, here is what I did:


I first tried running SimPE, opened the lot .package file and then ran a Tools -> Object Tools -> Fix Integrity on it. There were about 12 errors. This caused the lot to look empty when I entered the game. The net worth was equal to the money I had so it seemed like the house was gone. When I entered the lot, the game crashed. I could however move the family out and bulldoze the lot.

This however was not acceptable so I went back, restored a backup of the Sims data files, entered SimPE again and opened the lot. This time, instead of using the Fix Integrity tool to repair the objects, I just used it to list the damaged objects. I then deleted the corrupted objects through SimePE's interface.
When entering Sims again, the lot still looked empty from the hood. However the full amount of money was back. i managed to enter the lot and everything was back to normal. I then undid my reckless elevations, saved and reentered the hood. Now the lot was back and the house was normal... so everything is fixed again.

Perhaps one of the hints can help if anyone experinces something like this.

[rogue_psyche]

Thank you so much, Keev! I went into my lot and made a sloped driveway with the "boolprop constrainFloorElevation false" cheat and when I saved and left the lot the lot had turned blue. I didn't have the time to investigate it until now, and although I don't know if your fix will help since I can't get to my computer with Sims 2 installed, it definately makes me have hope that it will! I am kind of sad that I will have to lose the sloped driveway.

EDIT: Here's detailed instructions for fixing this problem for anyone who has this problem in the future.
THE FIX

First back up your neighborhood (http://www.modthesims2.com/article.php?t=46152). Sure, it's messed up now, but you can accidentally mess it up a lot more with SimPE.

Now that you're all backed up, open your lot up in SimPE. You can find it in Sims 2 --> Neighborhoods --> N00# --> Lots. (In these instructions, #=the number for your neighborhood). If you installed all the EPs before playing, your lot should one of the files toward the end. You can make sure you have the right one by clicking "jpg/tga/png Image (IMG)" on the resource tree, clicking on the listed files, and viewing them in Plugin View.

Once you have the damaged file opened, click "Texture Image (TXTR)" and find "N00#_Lot###!terrainLmap_txtr" (again, the #s represent your specific neighborhood and lot numbers). Under Plugin View you should see an aerial view image of your lot in grey scale, with the buildings as dark shapes and the terrain represented in detail. This is the file that is creating the problem. Delete it.

Save your changes, close SimPE, and load The Sims 2. Open up your neighborhood. Your previously blue lot should now look empty, but still have the same value or inhabitants.

Enter the lot and make the necessary changes to your terrain. I can't tell you how much is enough as I just leveled my previously sloped driveway. All I can say is that if you want to keep repeating the steps list above until the slope no longer turns your lot blue, go ahead, but if you want to be 100% sure your lot will be playable in the future, undo any features that required you to use the "boolProp constrainFloorElevation true" cheat.

Save your lot in game, not by clicking Exit to Neighborhood or Exit Game and clicking Save on the dialog box that pops up. I've read around here that it may prevent the corruption of save games.

I hope this helps anyone who experiences this problem in the future.

[Keev]

Hey rogue_psyche

Glad the hint worked :) I see you have written a much more detailed guide. I didn't think the problem was common so I just wrote that short description, but it is a good idea that you expanded it (and corrected my assumption about the need to delete all the listed files) since it seems it's not that uncommon a problem.