5 replies to this topic

[OldVeteran]

Hello all,

I'm firstly not 100% sure whether this is solely due to BGT or possibly due to another mod, but I'll firstly list my install:

1. BG1 (5512), BG2 (24698)
2. BG2 Fixpack v1
2a. German textpatch from Mkracht
3. BGT v1.02f
4. BG1NPCv12
5. NPCFlirt 1.1
6. Tashia
7. Fade
8. Amber
9. Unfinished Business BG2 v15
10. BP v177
10a. BP fix
11. BG Tweaks v3
12. BGT-BP Worldmap v6.3
13. Imoen [right before transition to BG2]

So I transitioned into BG2, lost half my crew (Shar Teel, Yeslick, Khalid), and met Khalid's corpse with Jaheira and Imoen in my party. When Jaheira steps close to the body (onto the trigger), the game goes into cutscene mode for a second and then goes back to normal. It doesn't play the dialogue at all and only shifts the screen a bit to the right each time it tries to run the cutscene, which is pretty much as long as Jaheira stands on the trigger: so the cutscene starts, terminates, starts, terminates etc.

As I am running BG (with BGT) in German, this could possibly be the culprit, judging from the other problems I have been experiencing...but of course it could come from something else as well but I wouldn't know what...

I suppose if someone could check on the script that runs this cutscene in BGT and whether it references to some invalid dialogue file, that would be great.

As an aside, I would just like to mention that Imoen, when she frees you, tells you about Jaheira and Minsc being people you can pick up at the cages. Well, since I killed Minsc in BG1 (didn't want him in party so refused to help), he wasn't really anywhere to be found, so the dialogue could use an additional check

[seanas]

most likely suspect here is the BG1NPC project - try uninstalling it prior to meeting Khalid's corpse and seeing if the scene works correctly.

[cmorgan]

If uninstalling The BG1 NPC Project fixes this, please also PM me, so I can find out what we are doing that interferes and fix it!

[OldVeteran]

Well I just uninstalled the BG1NPC pack and lo' and behold, even my save after the botched cutscene plays the cutscene fine when I step on the trigger.

Looks like it indeed was BG1NPC causing it.

[cmorgan]

OK, hmmm -
on vanilla BGT,

IF WEIGHT #4 /* Triggers after states #: 533 534 535 536 even though they appear after this state */
~Global("ENDOFBG1","GLOBAL",2)
See("DeadKhalid")
Global("SawKhalid","AR0603",0)
~ THEN BEGIN 0 // from:
  SAY #1035 /* ~Kha...Khalid?~ [JAHEIRC3] */
  IF ~~ THEN GOTO 1
END

- DLG file is JAHEIRAJ. I can't see where we would change her DLG file...

I bet it is the stupid PID thing again. The change when BG1 NPC is installed is
IF WEIGHT #28 /* Triggers after states #: 533 534 535 536 537 541 547 569 581 592 703 706 707 708 709 711 712 719 721 722 726 727 728 729 730 732 733 821 even though they appear after this state */.

Since all the PID's are made not valid by !Global("ENDOFBG1","GLOBAL",2), this should not be happening, but it is. I will have to do some more prospecting.

Gotta find and fix this, or all that work adding the global to shut down content after BG1 is over went to waste Although it should cause no problems if you remove all of BG1 NPC after the transition, the goal was to allow folks to leave BG1 NPC on their install untouched.

Edited by cmorgan, 11 January 2007 - 06:08 PM.

[pro5]

This may just as well be caused by those incorrect dialog state numbers in v12-beta (say, if we're adding extra conditions into the wrong state - this one - it won't fire under its original conditions).

Just did a quick check - it's triggering without problems in my game, so it's possible we've already fixed this.