Do i have to manually enable all mods in BG3 if I use vortex to exprot mods?

[sensei2346]

So after the new update to vortex, I an trying to export the mods to the game, but when i load the game up, they are disabled, do i have to manually check each and every mod? also is there a way to check which mod might be crashing the game specificly? 

[insomnious]

It's the problem with the game at the moment as a lot of mods aren't updated to work with Patch 7. See https://wiki.bg3.community/en/Tutorials/patch7-troubleshooting for some more troubleshooting information.

Make sure all mods are up to date within Vortex and then, unfortunately, you'll need to disable mods and see when it breaks. Sorry it's not much more helpful, but it's not something we can automate as there is a lack of information. As time goes on, and authors update their mods, it'll get easier. 

[insomnious]

When the game starts, it does some very basic checks on the modsettings.lsx file, which is normally located at C:\Users\<username>\AppData\Local\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public. There are a few things that I know of that will definitely cause a reset, which means the game isn't happy about something and it's better to remove and disable everything. Load up that file after you've exported from Vortex, start the game and if after a few seconds in it's been reset, then you've got a mod that is causing it.

[mainline]

I am having this same issue. I'm playing on patch 6. Yesterday everything was fine. Today, the only difference is the update to 1.51 on the BG3 extension. The mods appear in the load order file after I manually export to game, but the game does not load the mods.

 

I've even tried just using 1 single mod that I know was working just fine. The game will not load it.

Edited September 10 by mainline

[insomnious]

I'm assuming you swapped to the BG3 Patch 6 branch that Larian said. You might have the opposite problem, you may have a mod that is updated for Patch 7 and isn't working on Patch 6. Can you check your modsettings.lsx file (location is above) after Vortex has exported it and before the game has been run. Post it here if you like too so I can take a look. 

[mainline]

I haven't updated any of the mods to patch 7 compatible. After the game starts, it's resetting the modsettings.lsx file, removing all the mods.

 

Attached is the file exported from vortex before the game runs and resets it.

modsettings.lsx

[insomnious]

I'll take a look and see if anything jumps out

[JJStylez05]

Having the same issue as mainline. Not everyone is jumping headfirst into the stress that is patch 7. I was just playing the game on my working patch 6 modded save, logged out for a bit only to find vortex hard update (without my input) and leaving me now with a save that cant load mods. Its strange because this is a game where many hours go into a save, so to disregard this fact completely and in effect bork patch 6 modded saves is wild.

Edited September 10 by JJStylez05

[JJStylez05]

The last extension before the 1.51 one vortex wont even let me install to see if my mods would at least work with that one. Its saying "Archive not recognized as a vortex extension".

[showler]

15 minutes ago, JJStylez05 said:

Having the same issue as mainline. Not everyone is jumping headfirst into the stress that is patch 7. I was just playing the game on my working patch 6 modded save, logged out for a bit only to find vortex hard update (without my input) and leaving me now with a save that cant load mods. Its strange because this is a game where many hours go into a save, so to disregard this fact completely and in effect bork patch 6 modded saves is wild.

They didn't disregard that fact.  Insomnius' post in the stickied thread specifically mentions that the update was more complex because they had to support both patch 6 and patch 7.

Just because your game broke on an update doesn't mean anyone was negilgent.  It's the nature of modding.