Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Askot Bokbondeler]

Alright. We got some bugs out the way and will make a big bug crunching push after this next release. But now! The caravan arc begins in earnest.

bugs are addressed regularly, features are added regularly, the toad has no weekends and no holidays besides the month end break to work on the secret project, which he often postpones to crush the most serious issues... i'd say we're lucky we have such an active developer, stop whining because the toad wont implement your pet feature or clean the crap your text editor did when you modded the game, he's busy implementing my pet features.

[Frogwarrior]

Me, the one-bar-per-job makes my teeth ache, but at least I can edit the raws to fix it for armor. (Just multiply all the MATERIAL_SIZE tokens by 150.) No such luck on barrels and furniture, but that's just the way the cookie crumbles.

[MrWiggles]

well, he's asking for money, i'm asking for getting the bugs fixed.

The money is optional. I've been playing steadily for years, and I havent donated. Though that mostly due to the fact, that I've been unemployed.

As for yer requests to fix bugs.

He is fixing bugs.
http://bay12games.com/dwarves/mantisbt/changelog_page.php
Again, I present the change log, showing constant items on the bug tracker being dealt with. From the inconsequential "quick fix" typos, to the more infamous and awesome bugs, like rain melting the fat off on everyone.

Bugs of all type are getting fixed, quite regularly.

Which, now makes me confused what your original post was complaining about and the suggestion to resolve the complaint. I think we've dismissed your notion that Toady is only concentrating on Adventure mode. (Even though this last release also contained bug fixes for Fort Mode.)

Bugs get fixed. The community does not know what it takes to get a bug fix. Therefore the community, shouldn't be really in charge of dictating which bugs should be fix, as we do not know what it entails.

[anallyst]

Did you just suggest a "simple fix" involving revamping the very underlying structure behind all of the code?

it could come down to something simple like

Code: [Select]

BloodSplatter splatters[MAX_BEINGS * MAX_SPLATTERS_PER_BEING];
class Being {
public:
     BloodSplatter * carriedblood; // points to splatters[beingID]
};
instead of

Code: [Select]

class Being {
public:
     BloodSplatter * carriedblood = malloc(MAX_SPLATTERS_PER_BEING * sizeof(BloodSplatter));
};
not too much effort, isn'it ? now you have all splatter mem in one big region, so caches misses are minimized.

[MrWiggles]

Did you just suggest a "simple fix" involving revamping the very underlying structure behind all of the code?

it could come down to something simple like

Code: [Select]

BloodSplatter splatters[MAX_BEINGS * MAX_SPLATTERS_PER_BEING];
class Being {
public:
     BloodSplatter * carriedblood; // points to splatters[beingID]
};
instead of

Code: [Select]

class Being {
public:
     BloodSplatter * carriedblood = malloc(MAX_SPLATTERS_PER_BEING * sizeof(BloodSplatter));
};
not too much effort, isn'it ? now you have all splatter mem in one big region, so caches misses are minimized.

This is just speculation. Probably baseless.

It maybe that simple, but we don't know.

[3]

I don't suppose you know that the spatter-tracking issue was fixed sometime in the late stages of 40d, and resurged with .31. The only guesses I can make as to why it's now an issue are either that it was left out of the merge for whatever reason, or that some part of the materials rewrite has made fixing it more complex than you think.

[Frogwarrior]

Did you just suggest a "simple fix" involving revamping the very underlying structure behind all of the code?

it could come down to something simple like

Code: [Select]

BloodSplatter splatters[MAX_BEINGS * MAX_SPLATTERS_PER_BEING];
class Being {
public:
     BloodSplatter * carriedblood; // points to splatters[beingID]
};
instead of

Code: [Select]

class Being {
public:
     BloodSplatter * carriedblood = malloc(MAX_SPLATTERS_PER_BEING * sizeof(BloodSplatter));
};
not too much effort, isn'it ? now you have all splatter mem in one big region, so caches misses are minimized.

So are you suggesting that he only rewrite the underlying structure for just this one particular issue while leaving it the same for everything else? I.... don't think that's better?

[anallyst]

So are you suggesting that he only rewrite the underlying structure for just this one particular issue while leaving it the same for everything else? I.... don't think that's better?

my tests have shown that this is the main source of FPS drop, so yeah, it would suffice to focus on that particular construction.
see http://bay12games.com/dwarves/mantisbt/view.php?id=3532, http://bay12games.com/dwarves/mantisbt/view.php?id=3267

[3]

So are you suggesting that he only rewrite the underlying structure for just this one particular issue while leaving it the same for everything else? I.... don't think that's better?

If you're referring to only blood being fixed and not other materials, it's almost certain that spatter tracking is somehow universal (I'd guess that all "spatter" objects are in the same class, and the game just looks for objects of that class, if you excuse my ignorant terminology). Well, at least I'd hope it'd be implemented in a manner resembling that if Toady was in any way competent.

[AngleWyrm]

Holy shit, look how many people are defending bugs! Bugs, people! They are something to be stamped out and eradicated at every turn. What's wrong with a bug-of-the-week complaint thread? If it annoys you, say so.

The one that annoys me is "No seeds available for this location," when I clearly have the seeds.

[Lord Shonus]

You have a perfect place to say so. It's called the bug tracker. You do NOT know how spatter is calculated. NOBODY knows for certain what all the FPS drop comes from. You DO NOT, therefore, have any basis whatsoever for declaring anything a "easy fix." Not to mention all the "bugs" that are not bugs at all, but partially-implemented features that are waiting on some other feature to be added before they can work right.

[vadia]

There is a place to vote for bugs getting fixed -- it won't (As has been mentioned before) be a silver bullet, but just put your vote on the bugs in the voting on suggestions mantis site.  Some bugs are on there and I have voted for some of them.  Some have gotten fixed, some may not for a while -- but if you want to put your request via numbers that's the place.

[anallyst]

You have a perfect place to say so. It's called the bug tracker.

yeah, i'm a heavy user of it and frustrated from seeing the ignorance from toady's side.

You do NOT know how spatter is calculated. NOBODY knows for certain what all the FPS drop comes from.

did you click on my link ? that report is from me. i used cheating tools to remove the blood and dirt, and FPS got from 8 up to 33.
that was in a time frame of 15 minutes, in which i sent all dwarfes through water and cleaned the water from the contaminants. there is no doubt that nothing else could have improved FPS so drastically in that time.

[ZebioLizard2]

You have a perfect place to say so. It's called the bug tracker.

yeah, i'm a heavy user of it and frustrated from seeing the ignorance from toady's side.

You do NOT know how spatter is calculated. NOBODY knows for certain what all the FPS drop comes from.

did you click on my link ? that report is from me. i used cheating tools to remove the blood and dirt, and FPS got from 8 up to 33.
that was in a time frame of 15 minutes, in which i sent all dwarfes through water and cleaned the water from the contaminants. there is no doubt that nothing else could have improved FPS so drastically in that time.

I'm honestly a bit sick of having wooden blocks unable to go into the BLOCK PILE, along with not able to place underground plants onto Soil without mud myself

There's bugs on that tracker that have been over six months without a fix.. But can't complain, it is free afterall, although one shouldn't defend one with such zeal regardless, Considering the amount of bugs still to be fixed, or hasn't been fixed in so long. You don't make your case look good at all, but neither does the one declaring that toady should do a bug fix every week.

[Shurikane]

OP makes me almost want to switch carreers.

At least the replies made the read worth it...