Discovered Bugs by Jaesa

Jaesa

Potential Bug 1 - It appears that the script to spawn Parda is firing incorrectly, or on an inconsistent delay.

Jaesa said:

I came across something that I'm not really sure what to make of.

After exiting the Priests' Quarters, Parda (the man who normally approaches to inquire as to what happened to you) was delayed for varying lengths of time for some reason. I saved outside of the building before the encounter inside to test it, and this is what happened the three times I tried so far:


1. I stepped out of the building after the encounter, talked to the tutor who tells you how to open doors, spoke to two Watchmen whose pathing led them to be standing out in front of the same building, then walked past Dreppin (the man by the cow) when Parda finally appeared to ask what happened. He came from offscreen, from the direction of the Oghma Temple, possibly because the Quarters was no longer on my screen. (Delay: 30 seconds)

2. I stepped outside and didn't move for a few seconds, took a few steps forward, waited a few more seconds, took a few more steps forward and turned around to face the Priests' Quarters, then Parda appeared on the right side of the Quarters and approached me. (Delay: About 18 seconds)

3. Stepped outside again, stood still for a few seconds, then walked away towards the cow. Stopped, turned around, and walked to the opposite side of the screen. Stopped again, and as I turned around to walk by for the third time, Parda appeared from the left side of the Quarters. (Delay: 20 seconds)


I don't know if this is technically a bug, but it strikes me as odd because in 1.0.2014, Parda would appear just south of the Quarters and walk over to start a conversation with me so quickly that I'd barely have time to move more than a couple of steps without some sort of haste effect.

All the other NPC initiated conversations that I've seen so far (I just picked up Jaheira and Khalid at Friendly Arm Inn) haven't had the delay, so there's a chance that it's a weird, isolated incident. But as I said, I don't know, so I figured that I might as well mention it.

Dee

Now listed here

Parda should appear as soon as the player leaves the Priests' Quarters after killing Shank

1. Start a new game
2. Enter the building at x=2975, y=443
3. Speak to Shank, choose option 1
4. Ctrl-Y Shank to kill him
5. Leave the building
6. Notice that Parda does not appear immediately

Parda should appear at x=2938, y=796 as soon as the player emerges from the building and walk to the player to initiate dialogue.

Internal Tracking Number: 6170

Jaesa

So I figured out that it was just AVG scanning my computer that was making beta patched BGEE to lock up and crash on me in the beginning. The window went black, the mouse pointer turned into the busy cursor, and Alt+Tab wouldn't work. While I was working to figure out the problem, though, I did something I didn't try before: clicking with my mouse, even though there was a busy cursor instead of a pointer. After a few clicks, BGEE went from a black screen to a white screen, then minimized to show this "ASSERTION FAILED!" window. The game was still unresponsive and had to be force closed.

neleothesze

I have the same bug with different File error. http://forum.baldursgate.com/discussion/21696/assertion-failed-bug
It also happened once in the Black Pits with some creature file.