January - last edited January
Some users are experiencing this error message since running the January 2020 patch:
(thanks to @PaleRose_YT for the image)
If you are encountering this issue, please reply with the full spec. of your Mac. Instructions on how to find the information and what to provide here - http://answers.ea.com/t5/The-Sims-Mac/READ-FIRST-Sims-4-Mac-Help-Guides-and-Troubleshooting/m-p/4612... Please make sure to state whether you are running the Legacy Edition or the normal version of the game
Please note the exact error code for this issue is 135dec40:3fbbecd0:00000064:000000. If your error code is different please start a new thread.
Try repairing your game. Right click on the game in your Origin Games Library and select Repair Game.
One possible workaround is to change the language of your game to English. Please confirm whether this fixes the issue for you or not.
Please also hit the all important Me Too button below if you are experiencing this issue.
Using CC/Mods is at your own risk, EA are not responsible for making the game compatible with 3rd party content, the creator is.
Hey, so I have the Sims4 legacy edition (unfortunately) and everything has been okay so far, but today, I went to open my game again and it said it needed an update. Okay, I guess, do your thing. Update finished. Game isn't able to load anymore. Here's a photo of the error message. I've tried restarting both origin and my computer. Nothing has worked.
Also happening to me.
I changed the game language to english and worked just fine. Won't open if I select my mother tongue (portuguese), though.
Maybe it's the same thing that happened when we were first introduced to the Legacy Edition? :/
My game was working until yesterday's patch. This message (initialization error etc) is back again, I've changed the language to english and it's not working.
Hi I’m on a Mac and my sims 4 had just updated and now it won’t let me load onto my game only shows
Is there anything I can do ?
Same here This is the same behavior we experienced back in November. I just updated an hour ago, and it seems that this update re-introduced the issue. Can we rollback or uninstall this update somehow?