Open garmasword opened 1 year ago
The temporary solution I've found is to remove the following from modsettings.lsx
after you update things in the mod manager:
from <node id="ModOrder">
<node id="Module">
<attribute id="UUID" value="3d0c5ff8-c95d-c907-ff3e-34b204f1c630" type="FixedString" />
</node>
<node id="Module">
<attribute id="UUID" value="991c9c7a-fb80-40cb-8f0d-b92d4e80e9b1" type="FixedString" />
</node>
from <node id="Mods">
<node id="ModuleShortDesc">
<attribute id="Folder" value="SharedDev" type="LSString" />
<attribute id="MD5" value="ac0a920df9ef3ee4c216ec7c04512e13" type="LSString" />
<attribute id="Name" value="SharedDev" type="LSString" />
<attribute id="UUID" value="3d0c5ff8-c95d-c907-ff3e-34b204f1c630" type="FixedString" />
<attribute id="Version64" value="36028797022598504" type="int64" />
</node>
<node id="ModuleShortDesc">
<attribute id="Folder" value="Gustav" type="LSString" />
<attribute id="MD5" value="ee61bf22405d543f221ac925992f4547" type="LSString" />
<attribute id="Name" value="Gustav" type="LSString" />
<attribute id="UUID" value="991c9c7a-fb80-40cb-8f0d-b92d4e80e9b1" type="FixedString" />
<attribute id="Version64" value="36029301681017806" type="int64" />
</node>
The temporary solution I've found is to remove the following from
modsettings.lsx
after you update things in the mod manager:from
<node id="ModOrder">
<node id="Module"> <attribute id="UUID" value="3d0c5ff8-c95d-c907-ff3e-34b204f1c630" type="FixedString" /> </node> <node id="Module"> <attribute id="UUID" value="991c9c7a-fb80-40cb-8f0d-b92d4e80e9b1" type="FixedString" /> </node>
from
<node id="Mods">
<node id="ModuleShortDesc"> <attribute id="Folder" value="SharedDev" type="LSString" /> <attribute id="MD5" value="ac0a920df9ef3ee4c216ec7c04512e13" type="LSString" /> <attribute id="Name" value="SharedDev" type="LSString" /> <attribute id="UUID" value="3d0c5ff8-c95d-c907-ff3e-34b204f1c630" type="FixedString" /> <attribute id="Version64" value="36028797022598504" type="int64" /> </node> <node id="ModuleShortDesc"> <attribute id="Folder" value="Gustav" type="LSString" /> <attribute id="MD5" value="ee61bf22405d543f221ac925992f4547" type="LSString" /> <attribute id="Name" value="Gustav" type="LSString" /> <attribute id="UUID" value="991c9c7a-fb80-40cb-8f0d-b92d4e80e9b1" type="FixedString" /> <attribute id="Version64" value="36029301681017806" type="int64" /> </node>
Those lines that you shared with me are not present in my modsettings.lsx file, so that is not the problem, and trust me, I searched for them thoroughly, but thanks for trying to help me :(
Unless I don't understand what you mean...and what you mean is that i remove every single line that shares the same format, which is like...half the file
Those lines that you shared with me are not present in my modsettings.lsx file, so that is not the problem, and trust me, I searched for them thoroughly, but thanks for trying to help me :(
Unless I don't understand what you mean...and what you mean is that i remove every single line that shares the same format, which is like...half the file
I meant those lines specifically. Make sure you also have the campaign dropdown set to Main
.
Those lines that you shared with me are not present in my modsettings.lsx file, so that is not the problem, and trust me, I searched for them thoroughly, but thanks for trying to help me :( Unless I don't understand what you mean...and what you mean is that i remove every single line that shares the same format, which is like...half the file
I meant those lines specifically. Make sure you also have the campaign dropdown set to
Main
.
Then no, those lines are not present in my modsettings.lsx :( thanks anyway, I guess I'll have to wait for an update that fixes this issue
Want to chime in and say that for me removing those lines did work.
Since the update, everytime I install a new mod, the game will be stuck at 100% in the first loading screen when you enter the game, If i remove all mods, the game will work fine, I tried with mods individually and the problem returns. I tried several things, such as deleting everything located in the larian studios file in AppData.
Looks like you don't have a campaign selected, going by your screenshot, so the campaign mod isn't being exported to the modsettings.lsx.
Make sure the Game Data Path option under Settings -> Preferences is set to the Data folder for BG3 (in the root BG3 installation folder there's a bin folder and a Data folder). Then refresh the mod manager, make sure "Main" is selected in the campaign dropdown, and then export the load order again.
Looks like you don't have a campaign selected, going by your screenshot, so the campaign mod isn't being exported to the modsettings.lsx.
It's bad that he doesn't have a selected campain but I don't think it's the case here. I have it selected and experience exactly same problem and by comparing how looks original modsettings.lsx
genrated by the game and what creates BG3ModManager I've come to the exact same solution as @garmasword provided. So every time I save a changed mod list I have to remove SharedDev
and Gustav
from modsettings.lsx
.
So every time I save a changed mod list I have to remove
SharedDev
andGustav
frommodsettings.lsx
. I'm not seeing Gustav/SharedDev get added to modsettings.lsx, even if I have a mod that has it as a dependency.
Have you edited your Resources/IgnoredMods.json
manually? SharedDev/Gustav are dependencencies of the campaign, but they're specifically omitted via the "IgnoreDependencies" list in that file.
So every time I save a changed mod list I have to remove
SharedDev
andGustav
frommodsettings.lsx
. I'm not seeing Gustav/SharedDev get added to modsettings.lsx, even if I have a mod that has it as a dependency.Have you edited your
Resources/IgnoredMods.json
manually? SharedDev/Gustav are dependencencies of the campaign, but they're specifically omitted via the "IgnoreDependencies" list in that file.
I personally haven't touched that file and I still have to manually remove those lines. I'm also running it on Linux through wine though so maybe that is somehow interfering (I wouldn't think so, but can't rule it out).
I'm also running it on Linux through wine though so maybe that is somehow interfering (I wouldn't think so, but can't rule it out).
That's an important piece of the puzzle, yes! BG3MM is using Windows-only frameworks, so nothing is guaranteed to work in Linux or Mac.
I was able to replicate this behavior you're describing by moving Resources/IgnoredMods.json
, so it appears the actual issue is that file isn't being loaded in your setup, which results in GustavDev's dependencies being added to the load order, instead of being ignored.
Thank you @LaughingLeader for pointing to Resources/IgnoredMods.json
. I'll investigate the problem further.
But now, as I know the solution (which is simple and can be automated easily with xmlstarlet
) it's only a small inconvenience.
BTW, I'm on Linux too.
Same here, Linux user, using Wine, had to remove the lines manually.
Yeah, I have to remove the lines every time. I also had the issue of accidentally copying a few folders in that caused issue. But that's no longer a problem.
I think I've found the issue, I had BG3MM in a folder called ModManager, which I placed in my BG3 directory, I was running it from the BG3 directory wine ModManager/BG3ModManager.exe
, I modified my script to have it go into into the ModManager folder, and directly launch BG3ModManager.exe. Now my UI is lightly different (there's an overrides section), some mods are orange, ignored mods are being respected, and after double checking, I found settings.json and keybindings-default.json in BG3/Data. Meaning that BG3MM was looking for it's Data and Resources folders in the folder it was started from, and not from it's own folder.
@monyarm, very good finding. It worked for me too.
So, to sum up: the problem is that under WINE the BG3MM looks for its configuration files relative to the current directory instead of relative to the executable.
Thanks, that's a great find. This should be fixed in 1.0.9.4 via 68a3a040f7b1f3c2f32b7669058975ae6d1322fc and 655a2b953ba75018d970a3a590a6cea506791de8.
I was able to replicate the issue by starting the mod manager in a different folder from where the exe is (like C:\Windows\system32), and it was indeed trying to load IgnoredMods/etc relative from the cwd.
Relative paths should now have a safeguard to ensure it's relative to the exe, even if the current working directory is somewhere else.
I can confirm that it's working properly now on Linux.
I can confirm it too.
BG3 Mod Manager Version
1.0.9.1
BG3 Game Version
Full Release Hotfix 3
Bug Summary
Since the update, everytime I install a new mod, the game will be stuck at 100% in the first loading screen when you enter the game, If i remove all mods, the game will work fine, I tried with mods individually and the problem returns. I tried several things, such as deleting everything located in the larian studios file in AppData.
The only solution that i found, is deleting all the modmanager files, and doing the entire process of creating another modmanager file and setting all my mods again, the game will run fine until I install a new mod, then, the problem will return and again i will be stuck at 100% in loading screen forever
Links