163 replies to this topic

[ronin]

I wouldnt want to even try to troubleshoot problems with that.

ronin

[Azazello]

Veeeerrrry impressive list. Gluckwunsche!

I am fascinated - just how much storage space is needed for that?

As for helping troubleshooting...As ronin goes, so goes my nation: I won't even begin to pretend that I'll help with the bughunting.

Still, if you have questions about one mod at a time, perhaps can give some advice. For example, I hope you made the tooltip fix mentioned here. But honestly, that would be the very least of your challenges!

[Kulyok]

XAN:
3 times warnings like this :
WARNING: I_C_T2: the interjection point (GAELAN 66) has multiple exit transitions that have different actions!

Don't pay attention to the warnings like these. It only means that, if Xan is in the party, an extra variable will set after his comment. It is a WeiDU feature, and it doesn't lead to any bugs - and all interjections have been extensively tested, so you're safe here.

[berelinde]

Stuff like the following is just bad typing, and it will probably be buggy, as variables aren't being set. All it is is a few missing quotation marks.

KIARA_ZAYA:
WARNING: cannot verify trigger ~!InParty("Zaiya)~: Failure("lexing: empty token")
3 times warnings like this :
WARNING: cannot verify action ~SetGlobal("KiaraChallenge",LOCALS",1)~: Failure("lexing: empty token")

Should be

KIARA_ZAYA:
WARNING: cannot verify trigger ~!InParty("Zaiya")~: Failure("lexing: empty token")
3 times warnings like this :
WARNING: cannot verify action ~SetGlobal("KiaraChallenge","LOCALS",1)~: Failure("lexing: empty token")

You would be amazed how hard it is to spot stuff like this when you're flipping back and forth between your debug file and your open mod file, trying to find what, exactly, the problem is. I've stared at a SetGlobal("B!Whatever,"GLOBAL",1) forever and not spotted the missing quote (it's after B!Whatever).

Edited by BGhead, 31 January 2007 - 04:15 AM.

[seanas]

crazy install leo: i'm impressed that you've had as few errors as you report. i'd love to know the total install size too (and how it runs: if there's no lag or stutter i'm even more impressed).

some observations

WARNING: cannot verify action ~SetGlobal("KiaraChallenge",LOCALS",1)~: Failure("lexing: empty token")

and all similar warnings:
what BGHead said - this is an error (a typo) by the mod's author. the block its part of will fail in-game.

WARNING: I_C_T2: the interjection point (GAELAN 66) has multiple exit transitions that have different actions!

and all similar warnings: what Kulyok said - it's advice to the mod author, and will work normally in-game.

WARNING: REPLACE specifies no WEIGHT for state 109 and DLG uses non-trivial weights. Using weight from DLG (39). [65]

and all similar: these can be ignored. more advice to the mod author from weidu; will work normally in-game.

WARNING: cannot find block matching [BGTTweak/3/xKAGAIN.BAF]

and similar: the block that is attempting to be patched here has been changed by a previous mod. in this case, it was probably altered by the BG1NPC Project first. the Fixpack throws a few of these up, as it corrects lots of (broken) scripts, and mod which refer to those broken scripts to fix (in which case: no issue) or add content to (in which case: content not added - this will be the cause of the Raziel failure) won't install.

whether these are trivial or not depends upon which block is being altered: the BP warnings will mean that some of BP's scripting isn't installed in those four instances, but the creatures will still have a script (just not as smart); in others (the NEJ warnings) there may well be major in-game failures.

Warning: cannot find block matching [redemption/bcs/ AR6200asc.bcs]

a special case of the previous: redemption and longer road are not merely looking for specific script blocks, but scripts blocks from files in the override. if biffing has occurred, then they'll fail. it's also possible that BP alters the scripts they're looking for in different (non-broken) ways - and as they haven't been updated for a non-broken Ascension, they fail to install.

WARNING: EXTEND_TOP #position 1 out of range 0-1

and all similar: i have no idea what this means. anyone have more of an idea?

WARNING: cannot verify trigger ~CheckStatGT(Player,12,CHR)~: Not_found

and all similar: they're typos, as far as i know. the affected script blocks will fail in-game.

WARNING: Fast SET_2DA_ENTRY failed, falling back on old method...

and similar: can be ignored. it worked, just not the first way weidu tried. may well be advice to mod author (or weidu author).

[trigger list near line 3, column 24 of raziel/dlg/Raziel.d] PARSE WARNING at line 3 column 20-20
Near Text: )
Not enough arguments to [NumTimesTalkedTo]. Recovering.

and similar: typo in the mod. affected script or dialogue block will fail in-game.

[action list near line 5, column 56 of TTSQ\d/METBAE2.d] PARSE WARNING at line 5 column 52-52
Near Text: )
[Global] not found in ACTION.IDS
WARNING: cannot verify action ~Global("freebae","GLOBAL",1)~: Parsing.Parse_error

and similar: likewise, these are typos in the mod. the affected script or dialogue blocks will fail in-game.

WARNING: [questpack/wilbur/d0nosnd.wav] is a 0 byte file

can be ignored: this is harmless and intended.

not all of these failures are going to be harmful: the fact that a couple of demons and a vampire aren't as smart as they might be because BP couldn't find a matching script block isn't much drama; likewise, the fact that a mod fails to check charisma correctly won't be noticed - unless you deliberately created CHARNAME with a low charisma to avoid the Ariena romance.

i don't know what the out of range errors mean, nor what they mean in-game; hopefully someone else will know, cos i'm curious to find out. i'd be more than a little concerned about these:

WARNING: cannot find block matching [NeJ/sExt/oCUT01.bcs]
WARNING: cannot find block matching [NeJ/sExt/oCUTD1.bcs]
WARNING: cannot find block matching [NeJ/sExt/oCUT01G.bcs]

cos they're crucial parts of the game - the exit from chateau irenicus' sequence. if this scene goes horribly wrong, you know why. they could also be related to why Ulcaster crashes; certainly the Ulcaster crash will relate to NEJ, altho whether it relates to these is another matter.

Edited by seanas, 31 January 2007 - 05:19 AM.

[zodden]

Holy s#%t!

I don't know know what to say. First off I too got the errors you received with Redemtion/Longer Road. I have read someplace that they are not show-stopping errors and you should be able to complete either one. Its trying to account for something that does not need fixing post BP177 and so you should have no problems. My friend's install order is similar to mine with longer road right after install of BP177 and he played longer road without problems.

As for all that other stuff I can say you should PM Cmorgan for the latest BG1 NPC Mod as it solves your problems with Jaheira, among other bugs. Its not publically releasaed so you have to PM him for it. I doubt he will want to help you troubleshoot too much of that monster though. In fact it would be madness to even attempt it. I am impressed though at your determination! I don't even know and never heard of a bunch of the mods you installed.

I would also mention that BG2 fixpack version 2 is out and somebody testing your megas should try it.

It would be helpful if somebody could translate that monster thread thats in German to English and then post it here because frankly it does not help us much when we can't read your explanations as to how you did or did not do certain things.

Its very impressive though! I will look for any fixes that I have researched and will post back to this thread. Again that list would be great translated as well as the big thread thats in German. May help others with ambitious installs.

As to Kits I can't understand why they would go before BGT1.02 or BP177 or BGtweaks. I have always put them last or near last and then tested them and they worked fine for me. Of course I don't have a monster install like you have attempted.

Edited by zodden, 31 January 2007 - 01:41 PM.

[cmorgan]

I am afraid that I am absolutely, thoroughly unqualified to help troubleshoot on anything but a Tutu install or a straight clean BGT-WeiDU install (and the BGT only insofar as I can beg some of the heavy-hitters here at SHS to help my logic and answer my questions). I will say, though it pains me to say it after seeing the 24hour+ install time you sunk into that impressive monster, that you should check your PMs and use the new in-testing pro5-2 version of BG1 NPC v12. I can guarantee that with that much going on, the relatively small (!) I_T_Cs into incorrect states and several larger issues will contribute some nastiness. The good news is that the Jaheira bug (and several other odd occurrences) have been ironed out, so you should not have to uninstall after BG1.

I would be very interested to hear a progress report on how playing this one went. With that much content and tweaking, you may be in for the first 385 consecutive real-time day gaming runthrough of the entire story!

/edit - you will have to register here or send me an email address (don't post it!) so I can send you the link. It is worth it to register here (it's free!) - this is the home of many/most of the big mod folks

Edited by cmorgan, 31 January 2007 - 07:51 PM.

[Azazello]

@Leonardo Watson:

Do you use a (semi-automatic) install script? I hate to think that you or someone is pressing 'I' or 'Y' over 180 times!

[dragonian]

Oh dear god... And i thought my install was big.
I would realy like to see the transalated topic about instalation of this monster.

[pro5]

Can i ask what mod is this?

~SETUP-DRIZZT.TP2~ #0 #0 // Drizzt

This TP2 name will conflict with Drizzt Saga weidu version when it's out.

[seanas]

WARNING: EXTEND_TOP #position 1 out of range 0-1]

this warning, i learn from ronin's reply to a post on G3, is saying that amber is not patching a script because a third-part mod is not installed - wihch means that this warning, and all similar warnings, can be ignored: they're just telling you that no action was taken because none needed to be taken.

and a few more of the easy ones, from yr unsolved list:

WARNING: cannot verify trigger ~CheckStatGT(Player,12,CHR)~: Not_found

and all similar should be:
~CheckStatGT(Player1,12,CHR)~

WARNING: cannot verify action ~SetTokenObject("DORCNAME",<PLAYER1>)~: Failure("lexing: empty token")

and all similar should be:
~SetTokenObject("DORCNAME",PLAYER1)~

WARNING: cannot verify trigger ~=InParty("Kiyone") InMyArea("Kiyone")~: Failure("lexing: empty token")

should be, i think:
=~InParty("Kiyone") InMyArea("Kiyone")~

WARNING: cannot verify trigger ~!InParty("Zaiya)~: Failure("lexing: empty token")
WARNING: cannot verify action ~SetGlobal("KiaraChallenge",LOCALS",1)~: Failure("lexing: empty token")

and similar should be:
~!InParty("Zaiya")~
~SetGlobal("KiaraChallenge","LOCALS",1)~

and this one

WARNING: cannot verify action ~Global("freebae","GLOBAL",1)~: Parsing.Parse_error

i'm reasonably sure, should be:
~SetGlobal("freebae","GLOBAL",1)~
because it's giving an error in ACTION.IDS.

Edited by seanas, 03 February 2007 - 04:10 AM.

[ronin]

The Amber mod uses extend_top on 3 area scripts with OnCreation and doesnt add the Continue(). You will have to edit the scripts yourself and add the continue's

The three files are: m#ar1000.baf, m#ar0700.baf and m#ar0400.baf. Just add Continue() in each of the script blocks.

ronin

[Leonardo Watson]

Thank you for your help! Now I was able to repair some other files. You can get them here: http://www.mkracht.d...te/complete.php

Silly as I am, I was not logged at my postings, therefore I cannot change them.

Now the to do list is much shorter:

Amber:
WARNING: EXTEND_TOP #position 1 out of range 0-1

BGTTWEAK:
WARNING: cannot find block matching [BGTTweak/3/xKAGAIN.BAF]

BPv177:
WARNING: cannot find block matching [BPv177/SNIP/oAR2601.BCS]
WARNING: cannot find block matching [BPv177/SNIP/oDEMNAB1.bcs]
WARNING: cannot find block matching [BPv177/SNIP/oDEMNAB2.bcs]
WARNING: cannot find block matching [BPv177/SNIP/oVAMPIR1.bcs]
WARNING: ADD_CRE_ITEM: Unknown slot FIST. Default to INV15 for placement.

CTB:
WARNING: EXTEND_TOP #position 10 out of range 0-9
WARNING: EXTEND_BOTTOM #position 4 out of range 0-4
WARNING: EXTEND_BOTTOM #position 5 out of range 0-5
WARNING: EXTEND_BOTTOM #position 6 out of range 0-6
WARNING: EXTEND_BOTTOM #position 7 out of range 0-7
WARNING: EXTEND_TOP #position 3 out of range 0-1
WARNING: EXTEND_TOP #position 4 out of range 0-2
WARNING: EXTEND_TOP #position 3 out of range 0-1
WARNING: EXTEND_TOP #position 4 out of range 0-2
WARNING: EXTEND_TOP #position 3 out of range 0-1
WARNING: EXTEND_TOP #position 4 out of range 0-2
WARNING: EXTEND_BOTTOM #position 4 out of range 0-2
WARNING: EXTEND_BOTTOM #position 5 out of range 0-3
WARNING: EXTEND_BOTTOM #position 6 out of range 0-4

EDWINROMANCE:
WARNING: cannot find block matching [edwin/bcs/EDWIN_DEGARDAN.BCS]

IMOEN:
WARNING: EXTEND_TOP #position 2 out of range 0-2

KIDO:
WARNING: EXTEND_TOP #position 3 out of range 0-3
WARNING: EXTEND_TOP #position 3 out of range 0-3
WARNING: EXTEND_TOP #position 3 out of range 0-2
WARNING: EXTEND_TOP #position 3 out of range 0-3
WARNING: EXTEND_BOTTOM #position 5 out of range 0-4

LONGERROAD:
WARNING: cannot find block matching [LR/bcs/lrtext1.baf]
WARNING: cannot find block matching [LR/bcs/lr6200asc.baf]

NEJ2:
WARNING: cannot find block matching [NeJ/sExt/oCUT01.bcs]
WARNING: cannot find block matching [NeJ/sExt/oCUTD1.bcs]
WARNING: cannot find block matching [NeJ/sExt/oCUT01G.bcs]
WARNING: cannot find block matching [NeJ2/sFix/o2Aerie.bcs]
WARNING: cannot find block matching [NeJ2/sFix/o3Aerie.bcs]
WARNING: cannot find block matching [NeJ2/sFix/o1Edwin.bcs]
WARNING: cannot find block matching [NeJ2/sFix/o3Minsc.bcs]

RAZIEL:
[trigger list near line 3, column 24 of raziel/dlg/Raziel.d] PARSE WARNING at line 3 column 20-20
Near Text: )
Not enough arguments to [NumTimesTalkedTo]. Recovering.

[action list near line 28, column 53 of raziel/dlg/Raziel.d] PARSE WARNING at line 28 column 49-49
Near Text: )
Type mismatch in "Area" argument of [SetGlobal].
Expecting type "string". Recovering.

TDD:
WARNING: cannot find block matching [TDD/SNIP/oANOM25.BAF]

THALAN:
WARNING: EXTEND_TOP #position 2 out of range 0-2

TSUJATHA:
WARNING: cannot find block matching [Tsujatha/Scripts/DPLAYER2_ORIGINAL.BCS]


Respective Amber (v24) I made the changes as you told me, but the warnings are the same

Could LUVNALIA be installed before fixpack (then there is no warning) or would this cause other problems?

The warnings of Raziel remain the same, even on a clean install. Kick it out?

@ pro5
Please use annother name for your upcoming Drizzt Saga, because as I told you this name already exists

[ronin]

Respective Amber (v24) I made the changes as you told me, but the warnings are the same

Those changes had nothing to do with the warnings. Those warnings you can ignore as seanas said. The changes are needed because when you extend_top an area script that contanis an OnCreation you need to put Continue() at the end of each script block before the OnCreation.

ronin

[zodden]

Thank you for your help! Now I was able to repair some other files. You can get them here: http://www.mkracht.d...te/complete.php

Silly as I am, I was not logged at my postings, therefore I cannot change them.

Now the to do list is much shorter:

Just curious how many people do you have working on this project? It seems like a lot of people are involved over there. My dad spent a few years in Germany when he was in the army but he stinks as a translator and that thread is dying for a translation

Also I just noticed you installed BP Asseccsion and then the other version. What is the reason for that?

Also has any of you played from beginning to end yet with all the mods installed? Have you figured out the problem with installing kits? I have a fairly big mega but havent had many problems installing kits at the end.