Wintershade

I had to rename the files "Setup-BDToBv175.tp2" and "Setup-BDToBv175.exe" into "Setup-BDToBv174.tp2" and "Setup-BDToBv174.exe", respectively.

It's Vlad fault. He constantly rename tp2 filename every time when he release new Baldurdash version. I might ask him to stop, but don't count for anything...

Gotcha. Although the mod has some pretty useful tweaks (IMHO), so it would be a shame to break the installation because of something so trivial.

Okay guys, I think I have another bug to report.

I just started the BiG World Setup (with update), and as one of the mods, I selected "Baldurdash 1.74 or lastest".

Since the last Baldurdash version is 1.75 (and for some reason this version did get downloaded), after starting the install, the BWS complains about "missing mod" - Baldurdash 1.74.

I extracted "BDash175.exe" manually (not sure if that was needed, but I still did), and I had to rename the files "Setup-BDToBv175.tp2" and "Setup-BDToBv175.exe" into "Setup-BDToBv174.tp2" and "Setup-BDToBv174.exe", respectively.

So far from what I see, the installation is going fine after this little rename. So, I think the fix for BWS should not cause much trouble.

Thanks in advance!

Thanks, it seems to work now!

Now I can continue setting up my installation

Hey guys, I'm having trouble with the latest BWS (pulled from GIT).

After I make my mod selection, the BWS does not complain about conflicting mods (and I deliberately selected some that I know are in conflict - e.g. all the Big Picture and SCS components). Needless to say, the installation now fails, and I have no idea which mods/components I need to deselect anymore.

I've tried a fresh reinstall of BG1 and BG2 (not the EEs), as well as downloading and running the latest BWS (with update) from GIT, and the problem still persists - it shows no conflicts whatsoever, and the installation fails miserably.

Can anyone help me with this? Is this a bug? If so, how can I get around it? If not, what am I doing wrong?

Thanks in advance!

EDIT: I have checked out the commit 6a1c850 from GIT (the last one from 2016-08-15), rather than the latest and ran the BWS without updating. This time conflicts showed correctly, and I was able to install a few basic mods. Will test further, and will try to bisect the code if anyone is interested. In any case, if this is a bug, it is introduced in one of the commits from >=2016-08-23.