Forum Discussion
A few hours prior to me updating the game, I tried saving but was stuck in an endless loop. I updated the game, took out the outdated mods and still get the 135 error. Instead of wasting time and doing the 50/50 method, I disabled mods and placed the folder on my desktop and still get the error. I’ve tried double loading, repairing the game, using a different household, going to different saves, removing last exceptions and caches, and pretty much everything under the sun. I’ve seen very few people post about this issue and still one of the methods I previously mentioned normally worked for them. The only thing I can do at the moment is use cas, build mode, and save which is really weird.
- luthienrising10 months agoHero+
@allbutfaithful Please try this:
- Move/rename the Mods folder so the game creates a new one
- Delete localthumbcache - do this every time you change the content of the Mods folder or move/rename it
- Start the game
- Start a NEW save
Let me know if that works
- luthienrising10 months agoHero+
@allbutfaithful In a new save, do you get the same error?
- 10 months ago
Worked for me! Sad my save file is gone though
- luthienrising10 months agoHero+
@allbutfaithful Okay. Now copy your old save files out of the renamed/moved folder into the new one. Try loading those. Test in your regular household and a household you've never played in before. Unless you just want to start fresh, of course!
About The Sims 4 Mods & Custom Content
Recent Discussions
- 8 hours ago