MonkeyRobot22

After all the fixes that didn't work what DID work was what someone else suggested elsewhere. To be sure the issue was: After the recent update, the game no longer loaded mods. Going to Vortex, I got a "Cannot read .pak files" error. I reinstalled LS/Lib to no avail, continued to get the error. Updating Windows runtime to version 8 was supposed to fix this. It seemed to as I no longer got the error. However, no matter how many times I deployed the mods, the game would not load them. The fix was: Delete everything in the game mods folder (not mod staging folder). Re-deploy in Vortex. Fix any remaining issues (I have one mod that likes to uninstall somehow) by reinstalling any missing mods, then redeploy, and the game is working. I hope this fix works for you! In summary: Step 1: Download and install .Net Framework v8 for Windows (or your device) https://dotnet.microsoft.com/en-us/download/dotnet/8.0 Step 2: Delete everything from mods folder (opened using the top menu on Vortex) Step 3: Redeploy and reinstall any missing mods. Redeploy. Step 4: Play the game!

Regarding this issue, it is almost certainly an incompatible mod. This can happen after game updates. If a mod is deprecated or not updated by the author after becoming incompatible, this can happen. First step is to ensure that Vortex has found all of the updates for installed mods and that you have updated them. Once updates are verified, check that the modsettings.lsx file in C:\Users\%username%\AppData\Local\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public contains all of your mods listed after deployment. Check it again after loading into BG3, but before loading your savegame. If they disappear, BG3 has flagged a mod as incompatible and deleted your modsettings.lsx contents. The way to fix this is generally loading a fresh modded game a few mods at a time until that list doesn't depopulate AND you can load in and play with stable mods present. This is unrelated to the LS/lib issue that is the main topic of this thread. I'm hopeful for a fix on that front as the devs say they're on it . . .

Thanks for the tips, but after answering yes to the top two questions and applying the fix in the link, still getting no mods loaded, even though the "failed to read .pak" errors no longer appear.

Seconding this issue. Also followed the .net6 fix from Pickysaurus. Still no mods loading. Deployment in Vortex is suspiciously short.