10 replies to this topic

[RoBoBOBR]

How to fix it?

[Jarno Mikkola]

Did you start a new game after you ran the version x of the BWP/BWS... as your savegames are totally cheesed after every run.

[RoBoBOBR]

Starting new game did help, thanks.

But now i have new problem - i can't enter Larswood, game crashes =\

[AndrewB]

most probable causes:

1. a creature's animation isn't working
2. a creature's .cre file is flawed in some way (something like a bow in the off-hand slot, or something in the offhand while a 2 hander is in use)
3. game is trying to spawn a creature it doesn't have a .cre file for
4. the area file itself is messed up



>to find out which it is, get Near Infinity or DLTCEP and open up the area. Note all of the actors in the area. You'll need to go into the game, and try spawning each of those creatures individually to see if any of them crash the game. If you go through them all and haven't reproduced the crash, you know it isn't 1 or 2.

>if it is 3, you probably would've gotten some kind of error indicating a file is missing in your baldur.err log, assuming logging is turned on.

>if it is 4, the problem will disappear when you restore a backup of the .are file.

[RoBoBOBR]

Thanks, will do.

Okay, trying to spawn Osmadi (I used CLUAConsole:CreateCreature("[monster name]") command) seem to crash the game. How can i fix him?

Edited by RoBoBOBR, 31 May 2010 - 01:37 PM.

[AndrewB]

now that you know what creature file it is, you can (*)changelog the .cre file to follow the changes back, and try to pinpoint the specific change that is causing the creature to malfunction, and which mod is introducing that change. You should probably report the bug to the mod author so that they can investigate it, and if it is something on their end, fix it. If it is the result of an incompatibility with another mod, well.. at least you and the mod author are now aware of a compatibility issue and can avoid it in the future.


*in your BG2 folder you should have a file named "changelog". Open it up with a text editor like notepad. Inside you will find sufficient instructions for how to proceed. Once you've run the changelog .bat, you'll find the results of it in a .txt file called changelog.

[Miloch]

I replaced his animation (L_CLERIC_MALE_HUMAN) with CLERIC_MALE_HUMAN and it seems to fix the problem

That was the BG1 cleric animation from Infinity Animations, but it shouldn't be a problem unless some mod has done something wacky like give him two weapons (in which case, he wouldn't've received that animation). I just tested him with that animation with both a quarterstaff (what he has by default) and a club (what DSotSC gives him) and both were fine (though the club looks like a mace but that's expected I suppose). Export your osmadi.cre from NI and attach it, I guess. Out of curiosity, does it also work if you give him the MALARITE animation? Because that's probably the proper animation for him (he's an obvious Malarite, given what he says in dialogue). Also, post the contents of your WeiDU.log in [spoiler ] tags.

[Miloch]

I couldn't figure how to attach a file to my message, but you can find the file here : Osmadi at Mediafire

Cheers - reproduced the error and posted a fix here. The problem has to do with the dsclub01.itm Osmadi is wielding from the Dark Side of the Sword Coast mod, which was missing an animation value that could cause a crash. Makes some sense that you'll encounter it more with BG1 animations than BG2 ones, since they're less forgiving about details like that in general. Should be a fairly rare error though, unless there are other odd bugged items like that lying around (guess I could run a scan but that would involve, sigh, writing some code ).

In theory, you could drop that item in your override to fix the problem but it'll just have a generic "club" description unless you (re)install it with the DSotSC mod. You can fix it yourself in either NI or DLTCEP - in NI, expand the ITM folder, open dsclub.itm, scroll down to the first Item ability (around 0x72, the "Ranged" one), click View/Edit, scroll down to Animation: Overhand swing % (around 0x9e) and change the 0 to 100 and save it. In DLTCEP, same is on the "Extended Effects" tab in the "Overhand" field.

Incidentally, you can attach files directly to your posts if you register.