218 replies to this topic

[hlidskialf]

*Points to the new forum where discussions of bugfixes can be individual instead of thread page 10+.*

Curious, hlid. Does making a infinitely-paged thread clog up anything forum-wise?

Not if the thread has good content, no.

Of course, separate topics will make it easier for people to find things provided there isn't continuous clutter about the same thing.

Bingo! It's much easier to follow bug reports, development, and issues already fixed if they are in separte threads. Here's an example:

Random Gamer 1:
- Tries BGT-WeiDU, runs into a bug involving Noober.
- Checks the BGT-WeiDU forum, sees no topics mentioning Noober, decides to post a question.
- The mod makers come in, see a new thread involving said Noober-bug. Replies, diagnosis the cause after some discussion, and posts it's fixed.
Random Gamer 2:
- Has a bug involving Noober, sees said thread. Sees it's been addressed, and doesn't post. Instead he gets the fix/knows to wait for the fix.

Now, with giant multi-content threads:
- Random Gamers 1 to 17 all have a Noober bug. They post about it in the giant thread over the course of a month, none willing to read 10+ pages to see if it's already been addressed.
- Modders get so frustrated with answering the same questions over and over they stop modding and switch to collecting pornography. (Worthy, but not modding nonetheless.)

Really, it just comes down to being able to see what's been reported, what's been addressed and what still is new easily. My 2cp anyways.

[Sir BillyBob]

This is of course making the assumption that the player will actually read a posting or two before posting a new bug about the same bug posted the day prior.

[Ascension64]

Whoa! Can your format and grammar-ise your posts a bit better? Your text is almost Spanish...!

Sry, but IMHO the forum would be then spammed with tons of new topics...tell u:
tester A find a ug with respawn..post it as new topic...u would reply tith slution of problem..
tester B find some new bug..tester C also...up to tester Z1 which find respawn bug but don't see any topic on first site ( perhaps on second?..no? maybe third...yeah...whatever) and post new topic with respawn bug...some way to avoid it is "pinned crash bugs", "pinned dialog bugs", "pinned items/spells bugs"...etc. //some categories//...and all spam/duplicated problems deleted very fast.

Well, yes and no. What I am planning to do is pin up a summary of bugs reported for version 0.99 BETA 3 and state their status as I go, except I'm quite busy with a huge theory music exam in three weeks that is threatening to detonate my brain. Therefore, people can look at the pin first, then post if a bug is not there, and as such no one should need to search a million topics or posts to see if a bug has already been posted or not.

As for now: crash area-almost fixed...it is possible from NTotSC //With NTotSC installed many area goes crash...with DSotSC it is rare bug//

Interesting that many areas are crashing? No one I believe has reported this before, although it is known that the installation is unstable. Currently, until SBB gets time to do something about it, I would still recommend steering away from these two mods for the time being.

Few dialogues are mixed...ex. Dynahair sometimes say text that should appear in Journal after completing some quest (ex. in 3rd chapter she said <not vocal and not as a dialog...just text appear with her name> text from journal about completed werewolf island quest )...however it is REALLY RARE.

Is this another BG1NPC thing? Can you post the text inside your WeiDU.log?

Also about Journal...sometimes appear only messege with Journal entries added and sometimes it displayes the whole entries (as in Tutu)...

Well, yes. If I haven't given a journal entry a title, then it appears in full. I'll probably add headers to every journal entry in the next release.

Another  (possible) bug with some loot->the Sendai team usually drop few magic items and *golden belt* and now it is gone (but DSotSC loot works normally)...as for now I am in 5th chapter...more testing today.

It could be that DSotSC rids of the Sendai team items, although this is only a punt. Any other item mods/difficulty mods installed that makes things harder, for example?

[hlidskialf]

Sry, but IMHO the forum would be then spammed with tons of new topics...tell u:
tester A find a ug with respawn..post it as new topic...u would reply tith slution of problem..

No, it's not "spam" if it's all on topic with the forum and about the mod in question. It's sorta the point of having one! However, it's far, far better for organization. Instead you'd have a bunch of threads which simply detail problems and solutions. When Ascension gets around to his buglist thread he's going to have to re-read 11+ pages of this thread to track down the bugs. Painful to say the least.
This comes from 5+ years of moderating these games. But what the hell do I know?

[Sir BillyBob]

How come no one else has posted a message about NTotSC causing area crashes?

I can't figure out the Weidu.log (not just because of the language!), did you really install the tileset parts of NTotSC and not the main part of the mod? If so, see the ass whoopin' icon above.

If you did install the whole mod, please tell me what areas are still crashing. DSotSC and NTotSC should be very stable in a BGT-Weidu environment now (when using the right version of course).

[Promilus]

Ok...confirmed: areas crashes only with first visit...after exploring whole map it don't crash anymore <CLUAconsole:ExploreArea(); exploring helps a little bit but still crashing sometimes>..AR3800(9700 in BGT is crashing when first visit...everytime I send there different teams to explore game crashes...however when explored before installing NTotSC the area don't crash anymore (in current game)...however when I created new game and walked there with new hero it crashes me again...
Fully history:
BG2ToB+TDD->working
BG2ToB+TDD+BGT->working
BG2:ToB+TDD+BGT+DSotSC...crashes at AR9700 (BG1 AR 3800)
BG2:ToB+TDD+BGT with NTotSC...same...
rollback to : BG2:ToB+TDD+BGT...wokring...exploring world...
installing DSotSC...no crashes with explored world
installing NTotSC...crash with not explored area
rollback to: BG2:ToB+TDD+BGT+DSotSC...no crash with that area or any else
installing NTotSC...newy created hero...crashes at AR9700 :/ :/ :/
rollback...crashes remain...unninstalling whole BGT :[
installing BGT...working (no crashes)...soon try to install DSotSC and will see if new team will crash unexplored AR9700...if yes it means that both mods are not working (or only not working for me)
I hope it will work...too much time wasted :[
EDIT: reinstalled BGT and DSotSC...the crash appear to be related with random enounter with areas listed...normally when exploring AR9700 there are some spots where in 99% player meet some monsters...encountering those monsters are causing crash <monster respawn problem? >...however game can also crash when heading south and walking road...at the end of map the game also like to crash ...I have only one way to avoid those crashes: explore this map with DSotSC uninstalled and then instal DSotSC again...however now I have to create and explore it with every team I would like to play later or uninstall/install DSotSC every time i create a hero...huh, this seemed to be no bug in BGT WeiDU...only not 100% compatibility with DSotSC as I said earlier...I can live with that..however it is annoying...I did everything with the "BGT&mods install guide" and it don't work correctly...if someone encounter the same problems and have solution for it plz post it somewhere on forum and give me a link...

Edited by Promilus, 07 August 2005 - 03:10 AM.

[Ascension64]

Sry, but IMHO the forum would be then spammed with tons of new topics...tell u:
tester A find a ug with respawn..post it as new topic...u would reply tith slution of problem..

No, it's not "spam" if it's all on topic with the forum and about the mod in question. It's sorta the point of having one! However, it's far, far better for organization. Instead you'd have a bunch of threads which simply detail problems and solutions. When Ascension gets around to his buglist thread he's going to have to re-read 11+ pages of this thread to track down the bugs. Painful to say the least.
This comes from 5+ years of moderating these games. But what the hell do I know?

Well, how do you know? I make a point of text-filing all bugs reported/fixed/questionable on my HDD exactly so that I do not have to wade through puddles of mmph in such a topic as this.

[Sir BillyBob]

BG2:ToB+TDD+BGT+DSotSC...crashes at AR9700 (BG1 AR 3800)

Yes and no on this area. The crash is probably from all the bad spawn points. The cause of the bad spawns is actually DSotSC. In DSotSC, I copy over another version of that area because of the container in the tree (where you will find a key). Since I don't have a clue on adding containers by way of Weidu (CB's tutorials aren't helping here), I had always copied over my modified version of this area.

I totally forgot about this. There are several areas that have these changes, mostly for new doorways (AR9300 -Temple, AR3200 - North of Nashkel, etc). I missed all of these during my update for BGT-Weidu.

What what you are seeing is a spawn trying to load a creature onto the map that is not in BGT-Weidu but was in BGT-BP. Crap, I will have to fix all of these and get a small patch uploaded. Luckily, this would only need to fix the ARE files, so the patch will be really small. But, it will overwrite the ARE files (same issue, don't know how to do this with Weidu and as well all know with CtB, it doesn't always work anyways).

[hlidskialf]

Sry, but IMHO the forum would be then spammed with tons of new topics...tell u:
tester A find a ug with respawn..post it as new topic...u would reply tith slution of problem..

No, it's not "spam" if it's all on topic with the forum and about the mod in question. It's sorta the point of having one! However, it's far, far better for organization. Instead you'd have a bunch of threads which simply detail problems and solutions. When Ascension gets around to his buglist thread he's going to have to re-read 11+ pages of this thread to track down the bugs. Painful to say the least.
This comes from 5+ years of moderating these games. But what the hell do I know?

Well, how do you know? I make a point of text-filing all bugs reported/fixed/questionable on my HDD exactly so that I do not have to wade through puddles of mmph in such a topic as this.

Fine, whatever. Do WTF you want. Sorry for wasting your time.

[Ascension64]

Sry, but IMHO the forum would be then spammed with tons of new topics...tell u:
tester A find a ug with respawn..post it as new topic...u would reply tith slution of problem..

No, it's not "spam" if it's all on topic with the forum and about the mod in question. It's sorta the point of having one! However, it's far, far better for organization. Instead you'd have a bunch of threads which simply detail problems and solutions. When Ascension gets around to his buglist thread he's going to have to re-read 11+ pages of this thread to track down the bugs. Painful to say the least.
This comes from 5+ years of moderating these games. But what the hell do I know?

Well, how do you know? I make a point of text-filing all bugs reported/fixed/questionable on my HDD exactly so that I do not have to wade through puddles of mmph in such a topic as this.

Fine, whatever. Do WTF you want. Sorry for wasting your time.

Meant no offense, hlid. I intend to split the bugs up later in time, but I've been too busy with RL to do it, hence the textfile. KD, if you want to start this and have time, then go for it. But right now, I'd be depriving myself of sleep if I attempted this at this present time.

[Promilus]

I totally forgot about this.  There are several areas that have these changes, mostly for new doorways (AR9300 -Temple, AR3200 - North of Nashkel, etc).  I missed all of these during my update for BGT-Weidu.

What what you are seeing is a spawn trying to load a creature onto the map that is not in BGT-Weidu but was in BGT-BP.  Crap, I will have to fix all of these and get a small patch uploaded.  Luckily, this would only need to fix the ARE files, so the patch will be really small.  But, it will overwrite the ARE files (same issue, don't know how to do this with Weidu and as well all know with CtB, it doesn't always work anyways).

About temple (if u mean a temple east of beregost...where is quest with wyvern's head and bassilus symbol ) it didn't crash for me...About more crashing areas-by MoveToArea command some of DSotSC *.are files are also crashing...i.e. dsc007 and more other dscXXX.are...the weidu DSotSC are designed for non weidu BGT+BP right? and that's why it is a little incompatible with BGT weidu...if u make a patch that corrects it I would be most happy man on whole Faerun
Ooops..i forgot: balduran ship wreck second deck is getting crash (some error with *.bam file at line 1921...GetFrame failed..or something like that)..the same error when entering island from Shandalar's quest...I believe it has nothing to do with any mod I installed....which means it is BGT bug only.
EDIT: this isn't fault of BGT or something...it is throwing dagger (+3 and poison) bug...In melee it works fine, but when throwing it crash the game...sorry for my mistake.

Edited by Promilus, 09 August 2005 - 04:57 AM.

[Sir BillyBob]

You have some other problem if DSotSC areas crash. I jumped onto every DSC map to make sure they all loaded. So if they are crashing now, either you have a bad creature file used in a spawn or some other animation is giving you problems. They all loaded for me, that doesn't mean that I walked around every corner of every map, just that they loaded without a crash.

Spawns and ambient sounds are two of the most fustrating bugs to fix. I can enter a map and sit on it all day and it will not crash. I can leave and walk back onto that map and it now crashes. Spawns are random, therefore, finding a bad one is only going to happen if you trigger that spawn.

the weidu DSotSC are designed for non weidu BGT+BP right? and that's why it is a little incompatible with BGT weidu

What you said is what you said (and what was that???). Version 1.6 is for BGT-BP and version 1.7 is for BGT-Weidu. Mix them up and you get hit with a fish. Don't do that.

If you can tell me exactly what areas crash, I will try to see what problems could be causing it. Telling me "they crash" tells me nothing. It doesn't help me and it doesn't help the BGT-Weidu gang (both of them).

[Promilus]

dsc005, 006, 007 crash when loading..few others DSC also...soon i will give full list...but they all crash when load...so what could it be? Wrong tileset? creature?

[Dunderdon]

dsc005, 006, 007 crash when loading..few others DSC also...soon i will give full list...but they all crash when load...so what could it be? Wrong tileset? creature?

My tip: Creatures. I managed to load the Citadel map after deleting all actors in the .ARE file.

[Sir BillyBob]

Okay, time to move this discussion over to DSotSC where it belongs. You will see I have a patch already posted. The Citadel map didn't cause me any problems. If you have some, post it over there.

[Ascension64]

Topic now closed. (Friday 12 August 7:08 PM).

Please post bugs in separate topics. A complete list of currently reported/fixed bugs for the next version of BGT-WeiDU will posted soon.