@SummerSloane Please clear the EA App's cache:
https://help.ea.com/en-us/help/faq/clear-cache-to-fix-problems-with-your-games/
restart your computer, and repair the game: open your App game library, click Sims 3, and select Manage > Repair. Then see whether your packs show in the launcher.
The repair will undo the effects of the Alder Lake patch, so if you've applied it by necessity (i.e. you have an affected 12th-gen or newer Intel processor), you'll need to do so again. Let me know how it goes.
I think it would be best to address the missing content issue first, then the crashing. But as an example, if you have NRaas Cupcake installed without the Bakery store set, or the set isn't loading properly, the result would be an immediate crash. And your store content could have stopped working for account-related reasons at the same time as your packs disappeared.
@puzzlezaddict I have installed Alder Lake Patch again, and my packs are now showing in the launcher. Thank you!
Unfortunately, I am still crashing on startup. I took all of my packages out of my folder, to see if it was a mods issue in order to do a 50/50, but even without mods I still crashed on start up.
What do you suggest I do?
@puzzlezaddict I have also attached my dxdiag file.
@SummerSloane Did you specifically apply the Alder Lake patch to TS3.exe? I ask because the errors in your dxdiag are all from the Alder Lake issue. Just to make sure this isn't still the problem, please try the Task Manager workaround described here:
If it helps, that means this is still the reason for the crashes. If not, please look for new errors in the Reliability Monitor. Hit Windows key-R and enter "perfmon /rel" without quotes, and you'll see a chart of errors and updates with a column for each day. Today is on the right.
Look for an error that happened at exactly the time of your most recent attempt to launch Sims 3, specifically while using the Task Manager method. If you find one, double-click it to see more details, then copy that info and paste it into a reply here. If you don't see a new error, check back in an hour or so—the Reliability Monitor doesn't always update right away.
