Forum Discussion

Re: lot is still visible in map mode after it was bulldozed.

@missladycartier Is the issue still there if you have no Mods/CC (which you said you didn't have) while also doing do the following:

1. Make sure your game is fully updated:
• open Origin
• click ‘Game Library’
• right-click Sims 4 > Update Game.

2. Remove the following cache file: 

Exit the game. Delete the localthumbcache.package file in your “The Sims 4” folder [Documents > Electronic Arts > The Sims 4]. 

Is the issue happening anywhere else in that save, or in any of your other game saves? (if you bulldoze a lot and terrain then save and go to Worldview?

Are you able to place a different home from your library on that lot, then save, esit to the main menu, and re-enter to see if the issue remains?

3 Replies

  • Hi,

    There's no option in the library to update the game but to repair it. I already did that and it's still the same. I also deleted the cache. The problem is only with the save that I'm currently playing with. If I place a home in the lot from the map view, the game won't advance and I get stuck with the 'building lot' scene. However, if I enter the lot and place the new home there, it works, but when I exit, it's placed on top of the older one, which doesn't dissapear. Then, I exit to the menu, saving first, and enter again to see the lot still there. I exited the game and entered again, now the yellow warning sign has dissapear but the problem is still there.

    Is there a way to solve this issue?

    Thanks for answering!

  • SheriGR's avatar
    SheriGR
    Hero
    2 years ago

    @missladycartier I would try make sure the lot is unowned, then enter the lot and bulldoze the lot and then the terrain, save the game at that point, then leave the game and remove the following cache (the one you already removed plus others as directed at the link below, and then see if the same result is there:

    How to delete cache:
    • Exit your game and Origin
    • Go to Documents > Electronic Arts > The Sims 4
    • Delete the localthumbcache.package file in your “The Sims 4” folder (your game will re-create this folder next time you open the game)

    Directions on how to delete additional cache if needed:
    https://sims4.crinrict.com/eng/2014/09/delete-cache-files/

    If after all of this the save still shows the odd image in worldview but the lot is still functioning normally, I would assume the lot's bugged in that save. You could then choose to either play it as-is (if that visual glitch in worldview is the only issue and the lot plays normally) and hope that it eventually works itself out...

    or...

    Move your played households from that game save into your library taking note of their current funds and moving all Sims that you want to maintain relationships with into the same household (in the library all relationships outside of those in the saved household get severed, as does their personal inventory... if you want to save any items in their personal inventory you can first move them into a room or the home and save it into the library, but be aware that there are a small number of personal items that don't save to the library). You can also save to the library any lots in that save that you want to keep as-is. Then start a new game save and place the saved lots and households from your library. Then you can split the households into whatever separated households you want, and cheat back their previous funds and real estate. If that all works out, you can abandon/delete the save with the bugged lot.

  • Hi, just replying to ask, was this a residential rental unit? And, has it been fixed?

    I'm having a similar problem with a residential rental I placed in Forgotten Hollow.

    This residential rental lot is also having the "error code 132" issue I've seen reported elsewhere on this site (where players try to visit a lot or rental unit in live mode, and then are kicked to the world select screen, presumably due to corrupted objects) so I'm wondering if the problems are related. I plan to try to fix the problem using solutions I've seen shared in this forum.