13 replies to this topic

[GekkeR]

Installing BGT v1.01 thought I might as well post my findings

WeiDU install log (edit : don't worry about the morituri kit it's been rendered harmless by myself).

Warnings in DEBUGs

-BGTv1.01-
Error 1 Tele0700.BCS(from the warnings)
Got it due to the BG2 Fixpack modifying the original.

2 missing files ?
It happened after it saved the key for the bg1 areas , not sure what weidu's is trying at that point.
Most warnings can be ignored (as stated) but this one seemed odd so I thought I'd post it anyways.

Most of Jaheira and Minsc's .CRE files appeared broken after the install :
Select_Rare had a wrong string for Jaheira
The same for Minsc's .CRE files (also select_rare1+2).
Easily fixable.

All the farmers in Nashkel appear to be called Lahl.
Easily fixable in the english bg1.tra (russian is already correct).

-BPv177-
DEMNABSU.BCS was modified by BG2 fixpack so the replace didn't work obviously.
"ADD_CRE_ITEM ~MFIST4~ #0 #0 #0 ~NONE~ ~FIST~ " in Setup-BPv177.tp2 should be changed.
Don't know what the .DLG's problem is though , could use some help there (fixed the other 2 files already).
As I don't know what "weight" does , I'm stuck with the broken dlg's for now (unless it doesn't matter ?).

-BG2 Fixpack Beta1-
SPCL342.SPL (Find Familiar) was broken after the BG2 Fixpack install.

COPY_EXISTING ~spcl342.spl~ ~override~
READ_LONG 0x64 "abil_off"
READ_SHORT 0x68 "abil_num"
READ_LONG 0x6a "fx_off"
READ_SHORT 0x70 "fx_num"
WRITE_SHORT 0x70 ("%fx_num%" + 1)
FOR (index = 0 ; index < abil_num ; index = index + 1) BEGIN
READ_SHORT ("%abil_off%" + 0x20 + (0x28 * "%index%")) "abil_fx_idx"
WRITE_SHORT ("%abil_off%" + 0x1e + (0x28 * "%index%")) ("%abil_fx_num%" + 1)
END
INSERT_BYTES ("%fx_off%" ) 0x30 // new effect
WRITE_SHORT ("%fx_off%" ) 265 // set global
WRITE_BYTE ("%fx_off%" + 0x02) 1 // target: self
WRITE_LONG ("%fx_off%" + 0x04) 1 // value
WRITE_BYTE ("%fx_off%" + 0x0c) 1 // instant/perm
WRITE_BYTE ("%fx_off%" + 0x12) 100 // probability
WRITE_ASCII ("%fx_off%" + 0x14) ~tutfam01~ // variable
BUT_ONLY_IF_IT_CHANGES

The problem being :
READ_SHORT ("%abil_off%" + 0x20 + (0x28 * "%index%")) "abil_fx_idx"
WRITE_SHORT ("%abil_off%" + 0x1e + (0x28 * "%index%")) ("%abil_fx_num%" + 1)

This (probably) should be :
READ_SHORT ("%abil_off%" + 0x20 + (0x28 * "%index%")) "abil_fx_idx"
WRITE_SHORT ("%abil_off%" + 0x20 + (0x28 * "%index%")) ("%abil_fx_idx%" + 1)

Edited by GekkeR, 22 July 2006 - 12:31 AM.

[Ascension64]

Your post greatly confuses me. What applies to BGT-WeiDU v1.01 only?
Also, are the Lahl's shown in-game, or just appear in NI/DLTCEP?

[GekkeR]

Your post greatly confuses me. What applies to BGT-WeiDU v1.01 only?
Also, are the Lahl's shown in-game, or just appear in NI/DLTCEP?

Sorry about the confusion

BGT1.01 only is :
the TELE0700 part
Just found out this is due to the BG2 Fixpack (anyone who has it installed and doesn't have NeJ's Imoen should have had this warning).
Tele0700 bafs for use with BG2 Fixpack.

the 2 missing files after the bg1 area biffing(not sure if they can be ignored ?)
Found out they are FLAMINVI.BCS and XAN.BCS (don't ask me how I looked that up ).
Also XAN.BCS will exist in the end because of the EXTEND_TOP ~XAN.BCS~ in the Setup-BGT.TP2, but it will only be the extended stuff from aAliveNPC.baf

Jaheira and Minsc's CRE files have odd Select_Rare strings (BG1 CRE's).
Fixed these here (yeah I had too much time , till hex patching comes in)
Jaheira's CRE's for compat\bgt:
Fixed Select_Rare string Jaheira (BGT) BG1 CRE's.
Jaheira's CRE's for compat\nejjahei:
Fixed Select_Rare string Jaheira (NeJ) BG1 CRE's.
Minsc's CRE's for modify\cre:
Fixed Select_Rare string Minsc BG1 CRE's.

Farmers called Lahl.
Install\English\bg1.tra shows @9424 and @9425 as Lahl , this should be Farmer.
Thought LAHL.CRE was special but after looking in NI for BG1 , Lahl had Farmer as well go figure
Russian bg1.tra is already correct (shows Farmer).

(also edited my post to make more sense )

Edited by GekkeR, 22 July 2006 - 08:51 AM.

[zachD]

I came across the Lahl problem last week while playing with BGT1.01.

Lot of them in Nashkel and the Carnival area to east, they all seemed to operate fine withen the game but was a curious thing.

[Ascension64]

The missing files during BIFFing will not affect the game at all. The Xan could be restricted to the situation where you don't have NeJ installed prior to installing BGT-WeiDU.

For the BG2Fixpack, BG2Fixpack should be isntalled after BGT-WeiDU, just like all other mods that are not part of the mega-modification.

Edited by Ascension64, 22 July 2006 - 04:00 AM.

[GekkeR]

The missing files during BIFFing will not affect the game at all. The Xan could be restricted to the situation where you don't have NeJ installed prior to installing BGT-WeiDU.

For the BG2Fixpack, BG2Fixpack should be isntalled after BGT-WeiDU, just like all other mods that are not part of the mega-modification.

I thought the BG2Fixpack was going to replace BDash in the order ?
Or am I mistaken at installing BDash after BG2+ToB+Patch ?

Also had the Beregost bug going from High Hedge to Beregost into the Burning Wizard , I saved after I entered the Burning wizard, locked Zhurlong into a corner and tried repeated attempts to pickpocket him (after giving him the boots).
After about the 6th reload the game CTD'd.

Edited by GekkeR, 22 July 2006 - 09:09 AM.

[ronin]

The missing files during BIFFing will not affect the game at all. The Xan could be restricted to the situation where you don't have NeJ installed prior to installing BGT-WeiDU.

For the BG2Fixpack, BG2Fixpack should be isntalled after BGT-WeiDU, just like all other mods that are not part of the mega-modification.

I thought the BG2Fixpack was going to replace BDash in the order ?
Or am I mistaken at installing BDash after BG2+ToB+Patch ?

You are correct, I think Ascension64 meant the BG2Tweak pack.

ronin

[Ascension64]

I don't think so. It depends on how KD works it out, though I'd think he'd like it to go anywhere in any installation order.
BDash went before BGT-WeiDU only because it was shown to work before BGT-WeiDU. Although BG2Fixpack is designed to replace BDash, I am not entirely certain that it will work before BGT-WeiDU, hence it goes after BGT-WeiDU. And as a note, BDash isn't considered part of the mega-modification at all.

[pro5]

I don't think so. It depends on how KD works it out, though I'd think he'd like it to go anywhere in any installation order.
BDash went before BGT-WeiDU only because it was shown to work before BGT-WeiDU. Although BG2Fixpack is designed to replace BDash, I am not entirely certain that it will work before BGT-WeiDU, hence it goes after BGT-WeiDU. And as a note, BDash isn't considered part of the mega-modification at all.

Damn

A64, can you elaborate on what problems arise from installing the fixpack BEFORE bgt 1.01? I may be able to fix it myself for my game, which I'm already playing and I don't want it to be buggy.

[GekkeR]

Damn

A64, can you elaborate on what problems arise from installing the fixpack BEFORE bgt 1.01? I may be able to fix it myself for my game, which I'm already playing and I don't want it to be buggy.

Nothing except TELE0700.BCS should be a major problem (as far as I've seen).
If you haven't installed NeJ prior to installing BGT then you will have a bad TELE0700.BCS and that will give you a headache later in BG2.

-Only replace it when you haven't installed NeJ prior to BGT (and installed BG2 Fixpack before BGT) click-
If you have NeJ installed and still replace the file you will break Continuous Imoen with it.
On the same note that if you didn't install NeJ Continuous Imoen and don't replace the file you will break BG1 Imoen somewhere in BG2 (probably Irenicus dungeon).

Try opening SPCL342.SPL in NI , if it gives you error 250 then it's bugged as well (spell itself might still work though , unsure).

-Only replace it when SPCL342 fails to open with NI with a 250 error click-

Both fixable by replacing the files with the ones posted.

Don't forget though that the BG2 Fixpack IS beta and there have been ALOT of fixes after it's release (for examples look up their forums).
So you might want to switch out BG2Fixpack with BDash if you just want a simple game of BG.

Edited by GekkeR, 24 July 2006 - 03:23 AM.

[Ascension64]

Thanks GekkeR. I haven't tested BG2Fixpack at all, but since it includes Ease-Of-Use, G3Tweaks, Baldurdash, and Rogue Rebalancing Pack, all of which have been checked against BGT-WeiDU (see the compatibility thread), the compatibility information is combined integrally. For the other mods, I can't say, since I've been a bit lazy on the compatibility front lately.

[Father of Imoen]

Just a little off-topic, but:

In your wieud.log you mention: Morituri kit version 5.
I thought the latest version number was 3.

Is this a typo or is there indeed a version higher than 3?

Thanks for your time.
A morituri-fan.

[Vivi]

From my understanding, when you import a BG1 character into BG2, if you have a few certain items on your character then they will be imported as well and you end up finding them in Irenicus' Dungeon. If you don't have any of the certain items, then you end up finding Mail of the Dead and Helm of Balduran. Is that correct?

Anyway, when I finished BG1, I had a Helm of Balduran and a Chainmail +3 on my character. When I ended up in Irenicus' Dungeon, I found the Chainmail +3 in the dueregar room, but I also found a Mail of the Dead on the named dwarf. Also, there were 2 Helms of Balduran in the fireplace room instead of just the one I was expecting.

Not that it's a critical bug or anything, just thought I would let the maker know about it I certainly didn't mind getting a couple pieces of "extra" armor to start BG2 with though, heh. Oh, and props to the makers of this, it's truly an awesome mod. I probably would have never played BG1 if it wasnt for BGT.

[Ascension64]

Thanks for reporting that, I'll have a look at it.