Jump to content

BG3 Vortex, endless "Reading PAK Files. This may take a while..."


Nimarus

Recommended Posts

I've been unable to get mods with PAK files installed via Vortex. I set the game down for a couple of months and thought I'd update my mods and try again. While troubleshooting this problem, I did a clean install of the game and removed all my installed mods (maybe 5 mods). I try to install them via Vortex as usual, but I get an endless loop of the "Reading PAK Files" notification. Aside from that, Vortex appears to have installed the mods with them shown as "Enabled." However, none of the mods with PAK files are working. I looked around online and people suggested an issue with LSLib/Divine Tool or something that in needs. I tried rolling back to an earlier version of LSLib/Divine Tool that some said worked for them. It did not work for me. I saw on its GitHub page that installing .NET 8.0 (Got .Net SDK 8.0.204) might help, but sadly it did not.

No idea if it matters, but Vortex is installed on my C drive with my OS. BG3 is on my E: as is the Download and Staging folders. Also, no, I can't install BG3 on my C drive as it is nearly full (it's a small SSD).

Deployment Method: Symlink (only option available)

Am I making an error somewhere? Is there some requirement I'm missing? Do I just need to sit and wait patiently for something to be updated?

Thank you for your time.

  • Like 2
Link to comment
Share on other sites

Okay, immediately after posting this, I tried something. I checked the load order and got a message about E:\Vortex not being a valid command or something. I thought maybe it's having a problem with there being a space in the filepath. So, I removed any spaces in the filepath for the staging folder. So instead of it being "E:\Vortex Staging\Baldur's Gate 3" it's "E:\VortexStaging\Baldur'sGate3" which made everything start working fine. Mod Fixer installed and Vortex gave me no errors. I started a new character and tested the Level 30 mod and confirmed this mod is working.

I hope this proves useful for someone else.

Edit: I removed the spaces in the folder's name.

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

  • 3 weeks later...

@Nimarus I went into the settings and changed the location under Mods per your suggestion and it automatically moved everything over...works perfectly now!  Thanks for the insight!🌞 🍭 🌈

Link to comment
Share on other sites

On 4/22/2024 at 10:08 AM, clam4567 said:

Hello I currently have this issue but the staging folder is correct

does anyone know how to fix this?

Same problem here after todays update to 1.11.3, After update a blue message comes up spinning saying "Reading Pak Files. This may take a while..." I came back from running errands a few hours later and still going lol. Then when I tried to deploy mods it gave me a red "Failed to read" error. Not sure what to do.

  • Like 1
Link to comment
Share on other sites

@Nimarus, you are my savior.
I spent three hours fiddling with this s#*!. AND ONLY NEED TO CHANGE THE FOLDER NAME.

I installed .NET 8, and changed the path from "E:\Games\Vortex Mods\{game}" to "E:\Games\VortexMods\bg3"
it just works.

Link to comment
Share on other sites

Posted (edited)

My problem is the Folder I have to change the name of is my User Folder which in Window 10 you can't change it without making another User ...

Edit: Moved it to the Public Folder instead because it used no spaces in the folder name, now works.

Edited by Ladyrose01
Link to comment
Share on other sites

Posted (edited)

I keep having the same issue. And for some reason, my mods say .pak but the file type is .symlink

I have 560 mods installed but only 4 are showing up. I looked in the mod folder and opened a few up and some of them were either empty, had the info file or had the pak and info file. 

Using Vortex 1.11.14.

 

I have purged and deployed, deleted everything in the mod folder and reinstalled the game AND Vortex MULTIPLE TIMES and even verified integrity through Steam MULTIPLE TIMES.

I am SOO frustrated and ready to throw my computer against a wallimage.thumb.png.64afb1cd3bf64199a023ac96bb9f274a.pngimage.png.4312b9d18a30205298b0ea9ccd4c1fa3.pngimage.png.42718582591e2380bff6c03cae033217.png
image.thumb.png.e9d54309bfce4b9ddfc3f3024f0ea3af.png

Edited by DreamerQUeen3825661
Link to comment
Share on other sites

  • 2 months later...

For me the issue was that the staging folder set to a different drive/partition than the game files. Should work fine (even says so in the settings description for symlinks in Vortex), but apparently gives this reading-pak-files-forever issue.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...