5286 replies to this topic

[Nightfarer]

That's okay! I appreciate you pointing me towards it at least! That would be this, I think? https://kerzenburg.b...loads.php?id=49

 

With BWS, it should be downloaded from the Github Repository automatically

 

https://github.com/B...hive/master.zip

[Samael]

Ugh, even on the Recommended set up, I can't get it to go. I've doubly made sure the FixPack is in the downloads folder, but once again I get the following:

 

"I:\Games\Black Isle\BGII - SoA>
Area Patcher (Nightfarer's Area Patcher) was installed successfully.
Fix AR2300 Script (solution for a bug in the original game files) (Nightfarer's Area Patcher) was installed successfully.
Fix AR0701 Script (solution for a bug in the original game files) (Nightfarer's Area Patcher) was installed successfully.


##### Nightfarer's Item Patcher #####
The mod was not found.
After the mod is present, the install may be started another time.
Enter [r]etry, [c]ontinue or [e]xit."

 

It feels like its looking for something besides the Fix Pack but I don't know what. I'm going keep the setup open until someone familiar with the setup can weigh in. Thank you for pointing me to towards the file though, Nightfarer, I appreciate the help it even if it didn't work.

 

Current iteration of the selection is here if needed: https://www.dropbox...._clear.ini?dl=0

[agb1]

The item patcher and cre patcher are included in the Fixpack download, in Big World Fixpack/_Item_Patcher and Big World Fixpack/_Cre_Patcher.

BWS is supposed to copy the contents of those folders into the BG2 game folder at the beginning of the install process and create corresponding setup-item_patcher.exe and setup-cre_patcher.exe at the end of the install (when it reached the install step for those). If you manually copy Weidu.exe and rename it to those setup exe names, it might work. I'm not sure why this isn't working automatically. I only added those to BWS recently.

[Tzarnal]

Tried a test install of a modified EET Standard selection ( less npc's, a number of Tactical mods and components added ). Installation was smooth, literally did not have any problems during install at all which is frankly the first time thats happening to me, usually there is a conflict somewhere that needs to be adjusted.

 

The only problem was that it did not run the final EET setup step, but it warned me to do so when starting BG2:EE. It ran fine and afterwards the game at least put me through chargen and into Candlekeep as normal.

 

I can't see any reference to why it was skipped in my Install Debug log though.

Edited by Tzarnal, 06 December 2016 - 05:49 AM.

[agb1]

Another change you can make to get past this is to remove the F (if it is there) from the Type line in Big World Setup/Config/Global/item_patcher.ini and cre_patcher.ini and then restart BWS with the "no update" bat file. The F tells BWS that the mod is mandatory. I don't recall putting that there but the fact you can't continue past the error is a strong indicator. I will check these in 20 minutes or so.

 

There is no F in the ini file.  Strange - it therefore should be skippable.  I've added a command before the install step to copy weidu.exe since the built-in one seems to be not working.

Edited by agb1, 06 December 2016 - 06:46 AM.

[agb1]

Tzarnal, we had another report of EET_End being skipped yesterday. Please upload your weidu.log and I'll see if I can reproduce the skip.

[Tzarnal]

Sorry, I've deleted the installation already it was only a test run. I do  have the BWS-Selection.ini though. And I've got the standard logs that BWS keeps if you want them.

[agb1]

The ini file should be sufficient. Thanks.

[Tzarnal]

Tried a much smaller Minimal setup same issue. Weidu.log. BiG World Install Debug.txt

 

Going to just preemptive dump some system information and other details here I case its related to that.

 

Spoiler

Windows 10 - Insider preview

Steam version of BG1:EE, SOD, BG2:EE, installed outside of C: drive.

Ran BWS through the Without Update.vbs ( manually updated myself through a git client becuase i like to read the commits )

[agb1]

Is there an Item_Patcher.tp2 file in the game folder?

[agb1]

Oh, that's sneaky.  Well-spotted, Guest!  I see it now:  BWS actually reads the tp2 file and checks if the folder specified in the tp2's "BACKUP" line exists...!

 

I've modified that code in BWS to allow a setup tp2 without a corresponding mod folder, with a message box pop-up to tell you it's not happy but is going ahead anyway.  I'll also add a mod folder for Item Patcher in the Fixpack to make it happy in this particular case.

 

... or maybe not.  This doesn't explain why it didn't complain about Area Patcher, which also doesn't have its own mod folder in the Fixpack and yet was installed successfully.

 

Mystery solved.  "CMD;IF EXIST Setup-Area_Patcher.tp2 MD ".\Area_Patcher" in the BWS script is why this wasn't a problem for Area Patcher.

Edited by agb1, 06 December 2016 - 01:46 PM.

[Samael]

Awake now - does that mean if I update BWS it should be able to install it without issue there now or will it require me to manually set up something?

[agb1]

I think it will work now but I haven't tested...

[zonx]

Did you use the wrong comment delimiter in your most recent commit? It errors out (see pic). Editing comment to ; seems OK.

[agb1]

Yes. Thanks - fixed.

[Samael]

I was working today so I had to postpone giving it another shot until now. Today, I keep seem to be getting messages along the lines of the following:

 

"Found I:\ (location of file) \BGII - SoA\name of mod but did not find a corresponding mod folder (BWS reads the t2p and looks at the BACKUP line to determine the mod folder)". Judging by the fact it moves on after 60 seconds as mentioned in the patch notes, I guess thats the failsafe method of finding that file and that its meant to be doing that?

[agb1]

Yes and no... I wasn't expecting it to actually find any mods to complain about. This is happening for a lot of mods?

[Samael]

Yeah, during the Extraction phase it was happening constantly. I'm into the installation phase now, I'll probably leave it running whilst I sleep and see how it handles things.