Zenon wrote:I see there's been a GZDoom update since I reported this bug, and it hasn't been fixed.
Did I report it incorrectly?
Is it not fixable?
Did you lose interest in fixing it?
Have you not been able to recreate the bug?
There's been a severe lack in communication in this thread and in the threads I've made in feature suggestions and I cannot for the life of me imagine why.
Have I done something wrong?
-Did I report it incorrectly?
-Is it not fixable?
-Did you lose interest in fixing it?
-Have you not been able to recreate the bug?
haven't tried (not me personally)
Keep in mind that GZDoom is powered purely by volunteers. While it is our goal to reduce bugs as much as possible, there's several things that determine if it ever gets fixed - most notably, how it gets triaged is a big one - i.e. how does it affect gameplay, does it crash, is it a regression, other things like that. Don't take it personally if *your* bug happens to be the one not getting fixed. It's not personal at all. It's just that we often have a lot of other things we have to deal with and we have absolutely no manpower. Either way though, bumping the topic really doesn't help, it just annoys.
Like I said, it's a volunteer project. We have no "minimum activity requirement". We do not "pay by how many bugs get fixed" (or even at all, for that matter). There is no board that says "you must fix __ bugs before release!" We also do not get paid as I said, which means we have to do something *else* - other than GZDoom - where we do, in order to keep a roof over our heads. And even in our free time we don't do GZDoom 24/7 because that would be insane and would lead to burnout so quickly.
So like I said - don't take it personally.