Received this bug when attempting to travel to a Community Space in Eco Lifestyle. The community space has been updated to a maker space. No mods have been played with this save file, attempted a ga...
Ideas
I’m encountering a persistent Live Mode crash (error 123:35e4f805:2671b6ce) that appears when switching certain lots from Residential Rental to Residential, or when loading households into these lots. The issue began after adding items from the For Rent, Werewolves, and Laundry Day packs.
> Do you own the eco pack and get famous?
No, I don't.
Key observations:
Any new lot built from scratch with new-pack items works fine, including Live Mode and saving.
The crash only occurs after a lot has ever been zoned as a rental; changing back to Residential triggers the Live Mode crash.
Resetting the lot with forrent.resetlot and eviction does not fix it — hidden rental data appears to persist in the save.
Saving affected lots to the Tray often produces “server errors,” suggesting corruption in lot serialization, but this may be secondary to the Live Mode crash.
Sometime I can load into Live Mode on the effected lot and households. Maybe 1 out of 20 times?
Conclusion:
This appears to be a For Rent rental-unit data corruption that survives zoning changes, cheats, and even lot resets. The lot’s rental metadata seems embedded in the save, causing Live Mode to crash and Tray saves to fail. A workaround may require exporting rooms or manually stripping rental-unit components via a save editor.
Remedial Actions Taken:
Verified game files through Steam and EA App.
Performed a fresh reinstall of The Sims 4.
Attempted to save affected lots to the Tray and Library multiple times to test serialization.
Deleted all CC and mods to rule out conflicts.
Cleared localthumbcache.package.
Tested new saves and new lots with all new-pack items — confirmed they load successfully.
Incrementally added and removed new-pack interactable items (Werewolves, Laundry Day, For Rent) in small test lots.
Used testingcheats true and forrent.resetlot to clear rental data.
Evicted households from affected lots.
Switched lot types between Residential and Rental repeatedly.
Bulldozed and rebuilt rooms, saving isolated test rooms to the Library/Tray.
Hi HIMMURF
Before merging with existing thread and the same error code, do you have any LastException files in Documents\Electronic Arts\The Sims 4 ?
- Delete the ones you have
- Trigger the error again
- Check if new ones are created
- If that is the case, please copy/paste the content here. You can open the file with any text editor.
Deleting the file won't fix your issue. Posting the info is meant for troubleshooting.Do you own the eco pack and get famous ?
I didn't see a duplicate, sorry.
My newest last exception is:
<?xml version="1.0" ?><root>
<report><version>2</version><sessionid>6f8a88712a3e223068f0307e</sessionid><type>desync</type><sku>ea.maxis.sims4_64.15.pc</sku><createtime>2025-10-15 15:39:51</createtime><buildsignature>Local.Unknown.Unknown.1.118.257.1020-1.300.000.223.Release</buildsignature><categoryid>situation_scheduler_component.py:177</categoryid><desyncid>6f8a88712a3e223068f0307e</desyncid><systemconfig/><screenshot/><desyncdata>Exception raised while processing zone spin up sequence: 'SituationSchedulerComponent' object has no attribute 'object_situation_shifts' (AttributeError: 'SituationSchedulerComponent' object has no attribute 'object_situation_shifts') Traceback (most recent call last): File "T:\InGame\Gameplay\Scripts\Server\areaserver.py", line 130, in wrapped File "T:\InGame\Gameplay\Scripts\Server\areaserver.py", line 126, in finally_wrap File "T:\InGame\Gameplay\Scripts\Core\sims4\utils.py", line 157, in wrapper File "T:\InGame\Gameplay\Scripts\Core\sims4\utils.py", line 175, in wrapper File "T:\InGame\Gameplay\Scripts\Server\areaserver.py", line 383, in c_api_client_connect File "T:\InGame\Gameplay\Scripts\Server\zone.py", line 612, in do_zone_spin_up File "T:\InGame\Gameplay\Scripts\Server\zone_spin_up_service.py", line 1767, in update File "T:\InGame\Gameplay\Scripts\Server\zone_spin_up_service.py", line 399, in on_enter File "T:\InGame\Gameplay\Scripts\Server\venues\venue_service.py", line 345, in _select_zone_director File "T:\InGame\Gameplay\Scripts\Server\venues\venue_service.py", line 491, in _set_zone_director File "T:\InGame\Gameplay\Scripts\Server\business\business_zone_director_mixin.py", line 155, in on_startup File "T:\InGame\Gameplay\Scripts\Server\business\business_zone_director_mixin.py", line 43, in on_startup File "T:\InGame\Gameplay\Scripts\Server\celebrity_fans\fan_zone_director_mixin.py", line 33, in on_startup File "T:\InGame\Gameplay\Scripts\Server\venues\object_based_situation_zone_director.py", line 244, in on_startup File "T:\InGame\Gameplay\Scripts\Server\venues\object_based_situation_zone_director.py", line 261, in _start_object_based_situations_schedule File "T:\InGame\Gameplay\Scripts\Server\venues\object_based_situation_zone_director.py", line 502, in _setup_affected_objects_for_weekly_schedule File "T:\InGame\Gameplay\Scripts\Server\objects\script_object.py", line 2130, in add_dynamic_component File "T:\InGame\Gameplay\Scripts\Server\objects\components\__init__.py", line 356, in add_dynamic_component File "T:\InGame\Gameplay\Scripts\Server\objects\components\__init__.py", line 521, in __call__ File "T:\InGame\Gameplay\Scripts\Server\objects\components\situation_scheduler_component.py", line 177, in __init__ AttributeError: 'SituationSchedulerComponent' object has no attribute 'object_situation_shifts'rtim=0 Client Session Time: 18.14 Num Save Errors: 0 Num Load Errors: 0 Current Game State: 0x96d01090 LoadingScreenActiveFlag: 1 Origin Version: 13,566,0,6079 Modded: False SystemInfo: Windows 11 10.0.26100 GPU: AMD Radeon RX 7900 XT 32.0.21025.10016, GUID: ABB3CD40-DE1A-11EF-9A0D-9C6B00028FCD </desyncdata></report>
</root>
> Do you own the eco pack and get famous?
No, I don't.
Edit: I think this is the clean last exception🧾 Troubleshooting Summary – Persistent Live Mode Crash (Error 123:35e4f805:2671b6ce)
Date Range: October 2025
Status: Ongoing — clean save and never-rental lot still affectedIssue Summary
Live Mode crash (error 123:35e4f805:2671b6ce) persists even on clean saves and lots that have never been zoned as Residential Rentals.
Originally suspected to stem from corrupted For Rent rental metadata, the issue now appears to be a deeper situation scheduling or object-component failure unrelated to zoning history.Key Observations
Newly built test lots (with identical assets) still function normally.
Affected lot (Alpha 3) was never a rental, but still triggers Live Mode desync and crash.
Save file confirmed clean of rental data (no rental tuning in lot or household).
Crash reproduces consistently when placing or loading into the affected lot.
Lot placement without furniture occasionally succeeds; with furniture, it often CTDs.
Reproducible error in logs:
"AttributeError: 'SituationSchedulerComponent' object has no attribute 'object_situation_shifts'"
Indicates missing or broken situation scheduler binding to an object or lot component.
ConclusionRoot cause has shifted from rental data corruption to broken or orphaned SituationSchedulerComponent references within lot objects.
This points to a core lot-component corruption?
The component error originates in object_based_situation_zone_director.py, meaning one or more objects on the lot are still linked to invalid situation or business logic.Remedial Actions Taken
✅ Full clean reinstall of The Sims 4.
✅ Verified game files (Steam + EA App).
✅ Removed all Mods/CC and cleared localthumbcache.package.
✅ Tested affected lots in clean saves — same crash persists.
✅ Built and tested new lots using same packs — confirmed stable.
✅ Attempted placement of affected lots with and without furniture.
✅ Bulldozed, rebuilt, and isolated room-by-room to test stability.
⚠️ Desyncs remain tied to specific lots, regardless of save or mod state.
⚠️ Crash now consistently references the SituationSchedulerComponent, not rental scripts.
Current Status
A3 and other previously affected lots remain unstable even on clean saves.
No rental or mod dependencies remain.
Crash is reproducible under fully vanilla conditions, confirming core lot corruption rather than systemic save or mod interference.
Thoughts for next timeRemove vanilla bars and interact-able items? I'll think more about it later but I'm just going to give up on this lot until there is a status update and use my old megabuild.
Featured Places
