Forum Discussion
Thanks. Great you didn't use AI. Unfortunately it's a growing trend with some reporting issues and makes it more difficult to help, simple copy/pastes without any really helpful info. Thanks for the further info, really helpful. A couple of things:
SincerelyGhostt wrote:Reset my game by pulling out the mod, save, and tray folders for those attempts, clearing cache, restarting my computer, then opening the game. I made one sim (whatever was randomly generated first and unaltered), saved that one, then attempted to add another sim to the household. Every time I created one and went to play, the game would loop the loading screen.
This is not properly resetting the game. A proper reset is starting with a whole new clean folder as described here - [INSTRUCTIONS] How to troubleshoot and test a broken game | EA Forums - 11864548 Please give that a go and see what happens.
I can see in the Activity Monitor screenshots that TS4 looks fine but Google Chrome has multiple processes running. Whilst I don't think this is causing any issues with your game it wouldn't be a bad idea to quit Chrome and kill those processes if they don't quit when you're not using it. Chrome is pretty greedy and resource heavy for no reason and you don't want those processes to keep multiplying.
Thank you, I started the troubleshooting process by renaming the folder (and I made sure no mods changed or added files), opening a new save, creating a house and placing the sim. That worked until I got to the third sim where it got stuck.
The problem is, this happens with any sim, it's not just at a certain number of them that it gets stuck! I screen recorded the process this time, it's a google drive doc. ( 1:41 is the problem)
I've also had this freeze happen when simply trying to go into manage worlds from live (as mentioned in the previous reply). There are no lastcrash or lastexception files from this happening. I tried to add more sims after the initial recording, and was successful up until the fifth sim. I recorded this instance as well, problem occurs at 0:38.