37 replies to this topic

[Thauron]

Can you post the contents of your weidu.log - without it it's near impossible to diagnose your problem - I don't think BGT changes anything to the Copper Coronet (at least I think it doesn't) so it must be some other mod.

[ronin]

Couple of things:

1. Does it crash while saving game or while loading area?

2. Did you clear your cache and then try again?

3. Can you CLUA to the area or does it also crash?

4. Do as Thauron says and post your weidu.log so we can see what exactly you have installed.

ronin

[Thauron]

There is nothing wrong with your log, as far as I can see. - I don't know anyone else who reported a crash in the Copper Coronet with only these mods installed.

Maybe some of the experts around can help you.

[ronin]

Your log is right, try the things I posted above and let us know.

ronin

[Thauron]

AR0406

IESDP has a list with all BG2 (and BG1) areas + similar lists should be available on the internet.

[ronin]

Make sure you have: Debug Mode=1 in your baldur.ini then in the game shit ctrl+space to bring up the console then type: CLUAConsole:MoveToArea("ar0406")

ronin

[Miloch]

Make sure you have Logging On=1 under Program Options in your baldur.ini file, reproduce the crash and then post the text contents of the resulting baldur.err file.

[Miloch]

Hmm, usually that means a creature is referenced in the area file or script but doesn't exist (or is a typo). The usual way of solving is to hack around the area and script (ar0406.are and ar0406.bcs) with an editor (NI or DLTCEP) and see if any CREs referenced in them are missing. But google around a bit first - I think this has come up in other threads and maybe someone has already done that.

[Turambar]

Does it crash after the area is completely loaded, or when it's still loading? I mean, do you see the area for a moment, and then it crashes, or don't you?

[Turambar]

I added 3 polygons to door 14 and then to 25 and the check button stopped complaining at me, however it wouldn't let me save the file... Also the script didn't have a problem according to the check function, weather that means anything or not however is another matter. I will give it another stab later methinks.

Dave

DLTCEP often complains about polygons without a real reason, and it appears to be related to something else.
If it was a script problem, it would crash after the area has completely loaded.
Could be some animation already present in the area. Try spawning all actors one by one, or disabling and loading the area; if it loads like that, try re-enabling them one by one.

[Miloch]

That's a fairly common message in DLTCEP, and also one in the unmodded Copper Coronet, so it's unlikely to be the problem. The error message suggests it's a creature issue.

Try installing this and entering ar0406 when it prompts for an area. Then post the contents of the resulting arealog.txt. If there are any creatures marked UNKNOWN that's a dead giveaway of a problem. If not, then go down the list and CLUAConsole:CreateCreature() each one - most likely at least one will cause a crash (if it's not caused by one not existing).

Note you can use this utility on any area, and if you type 'all' it will report missing creatures in all areas. Though that may report false positives, as there are a few areas like this in unmodded BG2 that don't get used anywhere. You can run it as often as you like without uninstalling as it doesn't make changes to your game.

Edit: utility updated to v2 here

Edited by Miloch, 17 April 2011 - 04:53 PM.