|
Notes |
|
|
|
|
Please merge this into 3.2 before its final release. Thank you. |
|
|
|
|
|
|
|
|
|
Saw this one got merged in, thank you, I think it should look a bit better now compared to before. |
|
|
|
|
Turns out there unfortunately was a conversion error with the latest sprite, caused by some shenanigans in the version of the paint program I used. For some reason the sprite doesn't like to be converted to 32-bit graphic for Strife. It has to be fixed again, so it can still look right in the software renderer for Strife. For some reason it slipped under the radar since it still looked good in Hexen, but I must've forgotten to double-check Strife.
See the attached screenshot for comparison between the last merge request and the fixed sprite for Strife. |
|
|
|
(0024489)
|
|
Kaminsky
|
2025-04-22 14:56
(edited on: 2025-04-22 14:57) |
|
With this latest update, are you 100% confident that the icon looks okay in every IWAD in the software renderer now? I'm only asking because 3.2's release is right around the corner, so if you are, I'll open another merge request for it whenever I can. Thanks for the update, as always.
|
|
|
|
|
Yeah, it should look good now without any odd pixels. I double-checked with all iwads, and it seems to be all clear now.
For some reason when I let Paint.NET auto-update some time earlier, it somehow changed the way sprites were saved, which for some reason Strife didn't like.
I also don't wish to delay 3.2's release any further, and think you should release it ASAP. I can only think of one regression to iron out if there's still a chance, namely 0004513. |
|
|
|
|
|
|
|
|
|
allyicon_contrastfix.wad (351) 2025-04-07 04:47
allya0_contrast.png (291) 2025-04-07 04:47