8 replies to this topic

[LonerAoshi]

Basically, the Dark Horizons mod creates a new trigger for entry to a house in Central Baldur's Gate (AR7700, AR0700 in the original unmodified game). Entering the house (CM0750) causes no problems, but when you try to exit, it crashes. I had a look at the logs and the areas, and it turns out that the exit from CM0750 is still pointing at AR0700 instead of AR7700.

Attached are the WeiDU logs, ToBEx logs, and the areas themselves.

Apologies if this should be in the BGT forum or somewhere else.

EDIT: Also, I managed to fix it using Near Infinity, so just letting people know about the problem, really.

Attached Files

•  AR7700.ARE   45.23K   210 downloads
•  CM0750.ARE   6.68K   217 downloads
•  TobEx(CM0750).log   22.23K   264 downloads
•  Weidu.zip   15.49K   153 downloads

Edited by LonerAoshi, 24 February 2011 - 05:37 PM.

[Miloch]

Might want to post this on chosenofmystra.net or whatever site hosts Dark Horizons.

[LonerAoshi]

Might want to post this on chosenofmystra.net or whatever site hosts Dark Horizons.

Gotcha, sorry for posting here. Mods might want to delete this if it shouldn't be here.

[Solaufein]

Recent version fixes that. It was referencing a TUTU area.

[LonerAoshi]

Recent version fixes that. It was referencing a TUTU area.

Er, I'm running v2.05 for BGT. I'm 99% sure that's the latest version...

EDIT: In any case, I posted on the mod's forum over at TeamBG.

Edited by LonerAoshi, 25 February 2011 - 01:07 AM.

[Jarno Mikkola]

Recent version fixes that. It was referencing a TUTU area.

I'm running v2.05 for BGT. I'm 99% sure that's the latest version...

What Solafein was refering to is just that the bug was there because the mod itself was coded to use the Tutu value instead of the BGT value in the referense. And now it's corrected. And sinse he is updating the mod, it will be his update that makes...

Edited by Jarno Mikkola, 25 February 2011 - 03:27 AM.

[LonerAoshi]

Recent version fixes that. It was referencing a TUTU area.

I'm running v2.05 for BGT. I'm 99% sure that's the latest version...

What Solafein was refering to is just that the bug was there because the mod itself was coded to use the Tutu value instead of the BGT value in the referense. And now it's corrected. And sinse he is updating the mod, it will be his update that makes...

Yeah, I know. I looked at the changelog for v2.05, and I saw that. What I'm saying is that despite whatever changes were made, I'm using v2.05 and what I described still happens. Check my WeiDU log and the CM0750 I attached. There is definitely still a problem.

EDIT: Actually, looking at the discussion on the TeamBG forums, I think whatever fix was done there just pointed CM0750 at the original area of vanilla BG1 (ie AR0700) instead of the BGT area (AR7700).

Edited by LonerAoshi, 25 February 2011 - 04:50 AM.

[Solaufein]

Someone who knows BGT and the coding will have to figure it out. According to the code it should go to the BGT area.

From TP2

/* New and altered areas */
//COPY ~DarkHorizons\areas~ ~override~
COPY ~DarkHorizons\areas\CM0750.are~ ~override~
REPLACE_TEXTUALLY ~FW0700~ ~%AR2%~

From BGT TPA

OUTER_SPRINT "AR2" "AR7700"

[Miloch]

What the OP seems to be saying is the area reference points to AR0700 so replacing FW0700 does no good. I guess BGT should change AR0700 to AR7700 and the Tutu version should change it from AR0700 to FW0700.