soupiestking Posted April 3 Share Posted April 3 (edited) So, my mods arent working in game all of a sudden. I tried everything, even uninstalling and reinstalling BG3 and all of my mods, but still nothing. Checking Vortex, it seems as though its not acknowledging that LSlib/Divine tool is installed. Upon trying to deploy mods, or purge then deploy: see image 1. I get a 'failed to read pak' notification for every single BG3 mod. Image 2 shows that vortex thinks the divine tool is missing, despite me already installing it. So, to make it happy, I try to reinstall it. I have tried reinstalling it through the buttons on vortex, and ive tried installing it manually from elsewhere, AND i tried using a mod that automatically installs it. Which brings us to image 3, showing that I have in fact installed the divine tool, and vortex now asks if i want to replace the file or make a new one. I have tried both of these options, and both come out with the same result. Image 4 shows that it is still not acknowledging the LSLib/divine tool. I cant move or deploy mods, I cant add them to the load order and they will not import to the load order. What am I missing? Edited: When checking the options for the installed LSLib/Divine Tool mod, it gives me mod options. It defaults to the "BG3 LSLib" option, which does not deploy at all (see image 5) - despite Vortex saying that the LSLib needs to be deployed. Opening the tab, there is multiple different mod type options that do in fact deploy, just the LSLib one weirdly doesn't. (see image 6 for mod type options). I tried selecting the BG3 SE option, just to see if it would work, and it did in fact deploy (see image 7). This stopped the 'failed to read pak' notification (image 1) from popping up, but mods still cannot be moved to the load order, and the load order still says that I don't have an LSLib installed (image 4). So, I'm still stumped. Edited April 3 by soupiestking Updated investigation - still no solution Link to comment Share on other sites More sharing options...
Ckat85 Posted April 9 Share Posted April 9 Hey - I've had the same issue, was completely flummoxed but finally managed to fix it by downloading .NET framework V8.0.203 from Microsoft Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now