7 replies to this topic

[Anomaly]

I have identified something that seems to be a very serious bug (BP or WeiDU).

Testing case: pure BG2+TOB+Official Patch (French versions)

First, I install BP (all components at once): all work fine (thanks for your .tp2)
Then I uninstall BP (all components at once): this seems to work fine
Then I install BP again (all components at once): I get a lot of errors and only 8 components get installed

Errors are like this :

[BPv175/BAF/NEW_BAF/BEHHIV02.BAF] PARSE ERROR at line 146 column 20-20
Near Text: )
		Type mismatch in "ID" argument of [Shout].
		Expecting type "integer".

[BPv175/BAF/NEW_BAF/BEHHIV02.BAF]  ERROR at line 146 column 20-20
Near Text: )
		Parsing.Parse_error
ERROR: parsing [BPv175/BAF/NEW_BAF/BEHHIV02.BAF]: Parsing.Parse_error
ERROR: error compiling [BPv175/BAF/NEW_BAF/BEHHIV02.BAF]: Parsing.Parse_error
ERROR: compiling [BPv175/BAF/NEW_BAF/BEHHIV02.BAF]!
Stopping installation because of error.

ERROR Installing [Big Picture AI/Enhancement Mod, version 175 weidu (beta)], rolling back to previous state

[BPv175/GBENC/COMPILE/GBPrst1.BAF] PARSE ERROR at line 64 column 26-26
Near Text: )
		Type mismatch in "ID" argument of [Heard].
		Expecting type "integer".

[BPv175/GBENC/COMPILE/GBPrst1.BAF]  ERROR at line 64 column 26-26
Near Text: )
		Parsing.Parse_error
ERROR: parsing [BPv175/GBENC/COMPILE/GBPrst1.BAF]: Parsing.Parse_error
ERROR: error compiling [BPv175/GBENC/COMPILE/GBPrst1.BAF]: Parsing.Parse_error
ERROR: compiling [BPv175/GBENC/COMPILE/GBPrst1.BAF]!
Stopping installation because of error.

ERROR Installing [Improved Random Encounters, by Gebhard Blucher and Kensai Ryu], rolling back to previous state

[action list near line 68, column 2 of BPv175/ASCEND/D/GROMNIR.D] PARSE WARNING at line 79 column 37-37
Near Text: )
		Type mismatch in "ID" argument of [Shout].
		Expecting type "integer".

[action list near line 381, column 2 of BPv175/ASCEND/D/SOLAR.D] PARSE WARNING at line 381 column 18-18
Near Text: )
		[AddXP2DA] not found in ACTION.IDS
WARNING: cannot verify action ~AddXP2DA("Solar2")
StartCutSceneMode()
StartCutScene("cut234d")
~: Parsing.Parse_error

Components that get installed are :
SUCCESSFULLY INSTALLED [Level-50 Ruleset (Code By King Diamond)]
SUCCESSFULLY INSTALLED [Kuroisan the Acid Kensai, by Westley Weimer]
SUCCESSFULLY INSTALLED [Red Badge, Poison-Based Encounter, by Westley Weimer]
SUCCESSFULLY INSTALLED [Gebhard Blucher's Lich in the Docks]
SUCCESSFULLY INSTALLED [Kensai Ryu's Gnome Fighter/Illusionist in the Docks]
SUCCESSFULLY INSTALLED [Kensai Ryu's Improved Crypt King]
SUCCESSFULLY INSTALLED [Improved Kangaxx Encounter, by Kensai Ryu]
SUCCESSFULLY INSTALLED [Improved Small Teeth Pass, by Kensai Ryu]

This happens also when you try to uninstall a mod installed before BP-WeiDU ; BP-WeiDU is uninstalled, then reinstalled and I get the same errors and I got only these 8 components installed.

This also happened with the original .tp2 shipped in the archive, onto my BGT-WeiDU installation.

And even if I uninstall BP, then remove the BP folder and install a fresh copy of BP from the archive, the problem persist. I have tried several times on fresh installs of BG2 : it seems that BP (or BP uninstallation) corrupts game installation.

I have a 650K .DEBUG file if you like.

[horred the plague]

I have identified something that seems to be a very serious bug (BP or WeiDU).

Testing case: pure BG2+TOB+Official Patch (French versions)

First, I install BP (all components at once): all work fine (thanks for your .tp2)
Then I uninstall BP (all components at once): this seems to work fine
Then I install BP again (all components at once): I get a lot of errors and only 8 components get installed

This happens also when you try to uninstall a mod installed before BP-WeiDU ; BP-WeiDU is uninstalled, then reinstalled and I get the same errors and I got only these 8 components installed.

This also happened with the original .tp2 shipped in the archive, onto my BGT-WeiDU installation.

And even if I uninstall BP, then remove the BP folder and install a fresh copy of BP from the archive, the problem persist. I have tried several times on fresh installs of BG2 : it seems that BP (or BP uninstallation) corrupts game installation.

I have a 650K .DEBUG file if you like.

No, please save your debug file...

Hmm, I repeated the "wax-on, wax off" procedure at least 6 times (likely more), with no such issue. The problems sounds like an ongoing issue with weidu, about parsing IDS files. Most of the time it works, sometimes not.

Maybe hold onto the debug file, just in case The Bigg needs to see it. Post about this on the weidu forums. Make sure he knows there is "no biffing" in BP-weidu, cause it's his catch-all phrase for "problems with our mods".

[Anomaly]

Strange... I am not the only one who got this problem.

I will post at WeiDU forums. Thanks for helping !

[horred the plague]

Strange... I am not the only one who got this problem.

I will post at WeiDU forums. Thanks for helping !

Alright, i just got it too. I have evidence that SHOUTIDS.ids was NOT parsed when redoing BEHIV02.baf; so as soon as you're posted, i'll post.

[horred the plague]

Strange... I am not the only one who got this problem.

I will post at WeiDU forums. Thanks for helping !

The Bigg confirms it's a weidu issue, that should be corrected in weidu v 191.

Offhand, I'd say cut/paste your script compiler folder to another location, and try reinstallation again. Also, delete all referrence to BP-weidu from your weidu.log file. This is just a guess...which I will test momentarily.

EDIT: Absolutely no luck! I even tried to revert back to weiduv189; KD's GUI-switcher code makes this impossible.
I'll keep working on a way to cheat this ABSOLUTE buzz-killer.

Edited by horred the plague, 20 March 2006 - 02:28 PM.

[Azazello]

Hey horred!

I got some install weirdness.
While installing [Big Picture AI/Enhancement Mod, version 176 weidu (beta)] I got the following error:

[BPv176/BAF/NEW_BAF/BPLICH01.baf] PARSE ERROR at line 387 column 26-26
Near Text: )
		[Class] argument [LONG_BOW] not found in [Class.IDS]

[BPv176/BAF/NEW_BAF/BPLICH01.baf] PARSE ERROR at line 521 column 34-34
Near Text: )
		unknown object CLASS specifier [LONG_BOW]

CLASS value of 'LONG_BOW'? Umm, no.

Turns out that the following files all had LONG_BOW listed within some of the commands (I'll keep updating the list):
[BPv176/BAF/NEW_BAF/]

BEHHIV02.BAF
BPALLY.BAF
BPBOUNTY.BAF
BPELFMAG.BAF
BPELFPRE.BAF
BPLICH01.baf
BPLIZPRE.BAF
BPSUELF.BAF
BPSWSPID.BAF
BPTHIEF.BAF
BPWDALLY.baf
FGMAGE.BAF
GB-SMage.BAF
GB-Summ.BAF
PLANEVIL.BAF
SAREVTOB.BAF
SPSEQ16B.BAF
WBARSGT.BAF
WBASIGHT.BAF
WGARSGT.BAF
WSARSGT.BAF

[BPv176/BAF/RE-BAF/]


My bad luck, I have no tool to search all the BAF files that contained this string, so I have to keeping reinstalling to flag all the bad files. I'm right in the middle of doing that now.

I replaced LONG_BOW with MAGE_ALL.

Replaced
See([EVILCUTOFF.0.0.LONG_BOW.0.ILLUSIONARY])
with
See([EVILCUTOFF.0.0.0.0.ILLUSIONARY])

Hope these changes are correct...


BTW more funkiness... My Class.IDS has a LONG_SWORD entry in it? Has anyone heard of this before? Here the tail-end of my file:

198 ZOMBIE_NORMAL
199 FOOD_CREATURE
200 HUNTER_CREATURE
255 NO_CLASS
201 LONG_SWORD
202 MAGE_ALL
202 MAGE_ALL
203 FIGHTER_ALL
204 CLERIC_ALL
205 THIEF_ALL
206 BARD_ALL
207 PALADIN_ALL
208 DRUID_ALL
209 RANGER_ALL
210 WIZARD_EYE

Edited by Azazello, 20 May 2006 - 08:20 PM.

[seanas]

My Class.IDS has a LONG_SWORD entry in it?

in case you haven't solved this one yet...

re: LONG_BOW and CLASS.IDS, from IESDP:

202 LONG_BOW
Detects mages, including single class, kits, multi-class, and dual-class, as well as sorcerers (due to this value sharing the number 202 with MAGE_ALL, below).

202 MAGE_ALL
Detects mages, including single class, kits, multi-class, and dual-class, as well as sorcerers .

as for why some mod had changed LONG_BOW top LONG_SWORD, i have absolutely no idea, but this trascription is the cause of the errors you were seeing, eg:

[Class] argument [LONG_BOW] not found in [Class.IDS]

changing LONG_SWORD back to LONG_BOW in CLASS.IDS would also have fixed the problem (and faster than editing all the scripting references to LONG_BOW)