MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004459Zandronum[All Projects] Bugpublic2025-02-05 14:152025-02-27 20:20
ReporterIlyStr 
Assigned To 
PrioritylowSeveritytextReproducibilityalways
StatusacknowledgedResolutionbackport later 
PlatformASRock B550, AMD Ryzen 5 56 x64OSWindows 10 LTSC EnterpriseOS Version21H2 (19044.357)
Product Version4.0-beta 
Target VersionFixed in Version 
Summary0004459: The STCFN-STGNUM standard fonts have very strange coloring
DescriptionI checked, everything seems to be fine in the gzdoom.

In a nutshell, the font in Truecolor PNG format is standard for SLADE conversions. Gradient between top and bottom [253, 253, 253, 255] - [230, 230, 230, 230, 255] [R, G, B, A]. This is NOT seen in gzdoom (However, the font is still a bit more contrasty in gzdoom).

Also in the mod there are two copies of the font - one small resolution (about 8x9 pixels) in Graphics\Small Font the other with a higher resolution (21x32) in Hires\SmallFont Hres, all this is done to correct the scale of the font and its behavior, because if you keep only the hires folder with the font, the font will be similar to the message written during a drug-trip.
Steps To Reproduce● Open UDFC or his alternative name DFG - Koreans, generate font with gradient for Console Font from font RetroVile NC.
● Generate both small(size 7) and hires(size 24) versions of font in .pk3
● Extract via 7-Zip
● Open a self-developed C# program that copies files and renames them to the STCFN-STGNUM standard (it does nothing else with them)
● Place the resulting files in the desired folders in .PK3
● Convert to TrueColor PNG in Slade
Additional InformationZa build - 3.2-241030-1744
Mod that contains font'https://drive.google.com/file/d/16ptEzq6G1jubrtWZgFQs5Fxqi2G59gxa/view?usp=sharing [^]'
TagsNo tags attached.
Relationships
Attached Filespng FontTranslation1.png (172,204) 2025-02-05 14:15
/tracker/file_download.php?file_id=3182&type=bug
png

? HEX_Doom_Char_To_STCFN.exe (59,904) 2025-02-05 14:18
/tracker/file_download.php?file_id=3183&type=bug
? HEX_Doom_Char_To_STCFN.exe.config (189) 2025-02-05 14:19
/tracker/file_download.php?file_id=3184&type=bug
Issue History
Date ModifiedUsernameFieldChange
2025-02-05 14:15IlyStrNew Issue
2025-02-05 14:15IlyStrFile Added: FontTranslation1.png
2025-02-05 14:18IlyStrFile Added: HEX_Doom_Char_To_STCFN.exe
2025-02-05 14:19IlyStrFile Added: HEX_Doom_Char_To_STCFN.exe.config
2025-02-05 14:21IlyStrNote Added: 0024212
2025-02-05 14:22IlyStrNote Edited: 0024212bug_revision_view_page.php?bugnote_id=24212#r14462
2025-02-27 20:20unknownnaNote Added: 0024217
2025-02-27 20:20unknownnaStatusnew => acknowledged
2025-02-27 20:20unknownnaResolutionopen => backport later

Notes
(0024212)
IlyStr   
2025-02-05 14:21   
(edited on: 2025-02-05 14:22)
Font is also compatible with the Russian language
(0024217)
unknownna   
2025-02-27 20:20   
I tested your mod by making it compatible with GZDoom 1.8.6 that Zandronum 3.x is based on, and the same issue also happens there.

It seems to be a GZDoom issue that was changed later on, in very recent versions actually, starting from 3.8.0.

Quote from IlyStr
I checked, everything seems to be fine in the gzdoom.

In general, it's good practice to check the rules in'https://zandronum.com/tracker/plugin.php?page=Rules/rules [^]' to confirm whether the issue also happens in GZDoom 1.8.6 that Zandronum currently is based on. This makes it faster for us to confirm the issue.

It would also be ideal if you stripped down your mod further so it would be possible to upload a minimal example wad/pk3 that allows us to reproduce the issue much faster. The steps to reproduce are too advanced for simple testing.