by Gez » Thu Oct 26, 2023 3:15 am
JasonUK wrote: ↑Thu Oct 26, 2023 2:12 am
Version 4.10 of GZDoom ran/recognised my WL6/SOD/SD2 & SD3 files as the full paid versions of Wolfenstein 3D/Spear of Destiny but all versions of 4.11.x have so far just recognised them as shareware/demos. The WL6/SOD/SD2 & SD3 files were all taken from v1.4 DosBox versions of these games.
Trying to record GZDoom's loading screen I see that there are red errors for gamemap files having an incorrect hash? I'm not sure what that means or why these were fine for 4.10 but not 4.11 though? Any help/advice would be appreciated.
To make this less confusing because GZDoom does not support any Wolfenstein game, it's about
this mod. The issue is a duplicate of this one:
GAMEMAPS.XXX on 4.10-stable vs 4.11-dev
You can read that thread to get an overview of the problem, and why the hashing method stopped working. TL;DR is there was a bug that was fixed but revealed another bug that was also fixed but the hashing code already corrected for the second bug so now it overcorrects and fails.
A new version of the TC should fix this eventually:
AFADoomer wrote: ↑Mon Sep 25, 2023 6:09 pm
Thanks... This was an internal GZDoom fix that unfortunately isn't fully backward compatible with the hashing code I use. I will be pushing a 3.1 release soon to patch this and to resolve a few other issues.
[quote=JasonUK post_id=1246713 time=1698307976]
Version 4.10 of GZDoom ran/recognised my WL6/SOD/SD2 & SD3 files as the full paid versions of Wolfenstein 3D/Spear of Destiny but all versions of 4.11.x have so far just recognised them as shareware/demos. The WL6/SOD/SD2 & SD3 files were all taken from v1.4 DosBox versions of these games.
Trying to record GZDoom's loading screen I see that there are red errors for gamemap files having an incorrect hash? I'm not sure what that means or why these were fine for 4.10 but not 4.11 though? Any help/advice would be appreciated.
[/quote]
To make this less confusing because GZDoom does not support any Wolfenstein game, it's about [url=https://forum.zdoom.org/viewtopic.php?t=4608]this mod[/url]. The issue is a duplicate of this one:
[url=https://forum.zdoom.org/viewtopic.php?t=78201]GAMEMAPS.XXX on 4.10-stable vs 4.11-dev[/url]
You can read that thread to get an overview of the problem, and why the hashing method stopped working. TL;DR is there was a bug that was fixed but revealed another bug that was also fixed but the hashing code already corrected for the second bug so now it overcorrects and fails.
A new version of the TC should fix this eventually:
[quote=AFADoomer post_id=1245374 time=1695686968 user_id=11]
Thanks... This was an internal GZDoom fix that unfortunately isn't fully backward compatible with the hashing code I use. I will be pushing a 3.1 release soon to patch this and to resolve a few other issues.
[/quote]