I recently decided to try and playthrough all of BG1&2, and I stumbled upon SHS. The BWP seemed like a great idea, and i was able to get through the installation process pretty unscathed due to guides posted here. I have run into my first problem though, I can remove certain NPCs (Khalid, Jaheira, Viconia) without a problem. Their leave party dialogue kicks in and everything is fine, but I run into a problem with every other NPC thus far (Garrick, Finch, Minsc, Dynaheir). I kick them out of the party and their leave dialogue doesn't kick in.
I've searched a little through SHS and gibberlings3 and I thought I had found a fix (http://forums.gibber...showtopic=12134), but I can't find the offending code listed in that topic, and the SCS readme seems to suggest that that problem should have been fixed.
Thanks, Any help would be appreciated
p.s. - I wanted to add the weidu.log but I couldn't find an attachment option in the add topic interface, and I didn't want to copy/paste the massive thing in here. Silly problem, I know
Certain NPCs won't leave party
Started by
-Durandal-
, Jun 07 2011 02:02 PM
3 replies to this topic
#2
Jarno Mikkola
-
- Member
- 10911 posts
The Imp in his pink raincoat.
Posted 08 June 2011 - 03:49 AM
This topic will probably be moved to the Megamod Help forum... as it should.
Now, it's indeed curious that it's just some of the NPCs.
It might be wise to --change-log an NPC's file that has this problem and one that doesn't have it, and then compare the alterations ... darn I don't have the files to suggest the file names, if you have a NearInfinity, you can chack the save games .gam file for the .cre files names, I'll try to post them later, or someone else might suggest them too. Just so you know, the --change-log will just shorten the weidu.logs content to the mod components that altered the files... wich helps to identify the actual candidates of the bug causers.
Now, it's indeed curious that it's just some of the NPCs.
It might be wise to --change-log an NPC's file that has this problem and one that doesn't have it, and then compare the alterations ... darn I don't have the files to suggest the file names, if you have a NearInfinity, you can chack the save games .gam file for the .cre files names, I'll try to post them later, or someone else might suggest them too. Just so you know, the --change-log will just shorten the weidu.logs content to the mod components that altered the files... wich helps to identify the actual candidates of the bug causers.
Edited by Jarno Mikkola, 08 June 2011 - 03:51 AM.
Deactivated account. The user today is known as The Imp.
#3
Durandal
-
- Member
- 3 posts
Posted 08 June 2011 - 06:04 PM
Whoops, sorry. I posted a nigh identical topic in the General help forum again after registering, and added the weidu.log as an attachment. My apologies for posting it again in the wrong place.
#4
Durandal
-
- Member
- 3 posts
Posted 02 July 2011 - 07:54 AM
This topic will probably be moved to the Megamod Help forum... as it should.
Now, it's indeed curious that it's just some of the NPCs.
It might be wise to --change-log an NPC's file that has this problem and one that doesn't have it, and then compare the alterations ... darn I don't have the files to suggest the file names, if you have a NearInfinity, you can chack the save games .gam file for the .cre files names, I'll try to post them later, or someone else might suggest them too. Just so you know, the --change-log will just shorten the weidu.logs content to the mod components that altered the files... wich helps to identify the actual candidates of the bug causers.
I found a NearInfinity online so I could find the .cre file names and that wasn't difficult, I'm just having a bit of difficulty running the change-log. I edited the ########.### in notepad, removed the :: in notepad and put in the correct .cre file names (in this case *YNAHE2.cre and *MOEN1.cre). I run the change-log, and I'm faced with multiple options in the command prompt. I'm just not sure exactly what to do to get the files backed up in the change-log folder so they can be inspected to find out what's causing the bug.
Thanks Again
