[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.