[DNS]

Ninety-Six, on 22 September 2025 - 07:10 AM, said:

This "fkup" is repeated by 80-90% of every other source port dev, 64 and otherwise. The list of source ports that fix the fucking bug is much smaller than the list of ones that don't. And what for what reason? "Demo compatibility." A feature so important that most people don't even realize it exists. Truly, a worthy sacrifice.


The fact is: there is only one version of Doom 64 that has guns in this first-person shooter that actually work, and that's only because it's built off of GZDoom which is one of the few ports to fix it by default.

It's just extra insulting in 64EX+'s case because it's supposed to be the successor to the original port, WHICH FIXED THE BUG, and he removed it.

64EX+ has a repo with an active dev (at least the last time that I checked). Have you filed a report to request the old EX behavior be returned? Even if the dev refuses, at least we would have a reason for the reversion of the fix.

[Ninety-Six]

ReaperAA, on 25 September 2025 - 08:26 PM, said:

just that he isn't really a part of those communities that Ninety-six was blaming.

To be specific here, I'm not blaming doomworld for this. This is an issue with the entire doom community, as a whole.

DNS, on 26 September 2025 - 11:37 AM, said:

64EX+ has a repo with an active dev (at least the last time that I checked). Have you filed a report to request the old EX behavior be returned? Even if the dev refuses, at least we would have a reason for the reversion of the fix.

Yes and it was confirmed that they removed the feature and don't intend to add it back.

[DNS]

Ninety-Six, on 28 September 2025 - 04:38 PM, said:

To be specific here, I'm not blaming doomworld for this. This is an issue with the entire doom community, as a whole.

He seems to think that the "doom community" equates to doomworld/zdoom even though there are countless individuals that can't stand either of these terrible forums. Several being on this message board alone.

Ninety-Six, on 28 September 2025 - 04:38 PM, said:

Yes and it was confirmed that they removed the feature and don't intend to add it back.

Did the dev say why the reversion was made? Seems pretty stupid to remove the corrected behavior if there isn't a technical reason behind doing so.

[Phredreeke]

Not having the blockmap fix is the vanilla behavior.

[Phredreeke]

GZDOOM HAS BEEN CLOSED DUE TO AIDS*



* AI Derangement Syndrome

[Martin Howe]

jkas789, on 09 June 2021 - 09:12 PM, said:

Fuck Doomworld.

It seems somebody finally did

[NightFright]

So did I get this correctly? Graf disappears for one year and everything goes well during that time regarding development. Then suddenly he resurfaces, uses AI in some new code and more or less tells co-devs to stay the hell away from his "sacred" project and open their own code forks?

I never thought this port would die due to an overdose of hubris, but Graf was always close to it. He may have finally snapped.

[DNS]

It's so nice to be proven right. On just the previous page of this thread I specifically mentioned that zdoom was run by a narcissist. Looks like graf and the mentally ill rachael that actively protects and runs cover for pedofiles are a perfect match for each other. And to think this is the guy that was trying to develop a "superior" port to eduke32 when he can't even keep his own house in order.

Looks like most of the dev team that contributed during grafs sabbatical before he returned and went full AIDS have moved on to fork: UZDoom

[dnskill]

[NightFright]

I think it's time to consider leaving the ZDoom forums. Either way: RIP GZDoom - and Raze as well, I guess.

[Ninety-Six]

DNS, on 15 October 2025 - 03:15 PM, said:

Looks like most of the dev team that contributed during grafs sabbatical before he returned and went full AIDS have moved on to fork: UZDoom

And the first thing they did was turn off texture filtering.


I'm sad that it took this long for the rest of the devs to fork off. Ever since zdoom ceased development, graf was granted free reign to be as much of an asshole to anyone and everyone as he wanted, with not so much as a slap on the wrist. The worst he got was mockery from the wider community.

I'm no fan of AI, but on the spectrum of flagrant AI misuse, this isn't even middle-of-the-road. It's just dumb. I'm not defending it, mind, but of all the notches on Graf's belt, THIS is what finally dethroned him?

[NightFright]

To me it looks rather like a superficial reason for finally breaking with Graf after being unbearable since ages. The fact that almost everybody fell off right away speaks volumes. I doubt the usage of AI was such a biggie that everybody had to get super butthurt about it.

[Reaper_Man]

Ninety-Six, on 17 October 2025 - 08:21 PM, said:

I'm no fan of AI, but on the spectrum of flagrant AI misuse, this isn't even middle-of-the-road. It's just dumb. I'm not defending it, mind, but of all the notches on Graf's belt, THIS is what finally dethroned him?

It has to be his attitude and response about it more than anything else. Shows up after a year to contribute broken commits, then "everyone does it", "it's not a big deal", "it wasn't important code anyway", and of course finally "if you don't like it then make your own project". Just utterly unapologetic. It's like a bingo card of the kind of narcissism seen all over fan projects of all types.

You are all right that this is a long time coming type situation, meets straw breaking the camel's back scenario. It was just too perfect of a situation for the usual suspects to keep giving him plausible deniability, so it is, finally, over.