by DarkkOne » Sat Feb 01, 2025 4:53 pm
With gzDoom 4.14.0 (as well as 4.11.something, I updated to see if a newer version resolved the issue) and Vulkan rendering (it's fine with OpenGL), the graphics are corrupted when using "Nearest" scaling for textures (any mipmap choice has the same results). As far as I can tell, it doesn't affect walls, floors, items, etc, just like... menu text, menu images (including the default Doom menu text), status bar, and things like that. Though I'm not sure that it's conclusive that it doesn't affect other things.
In the attached image, you can see the errors both in the menu text and the large background image. I don't know how to describe the issue, it looks like occasionally two adjacent pixels are swapped, but I feel it's very apparent in the attached image.
With gzDoom 4.14.0 (as well as 4.11.something, I updated to see if a newer version resolved the issue) and Vulkan rendering (it's fine with OpenGL), the graphics are corrupted when using "Nearest" scaling for textures (any mipmap choice has the same results). As far as I can tell, it doesn't affect walls, floors, items, etc, just like... menu text, menu images (including the default Doom menu text), status bar, and things like that. Though I'm not sure that it's conclusive that it doesn't affect other things.
In the attached image, you can see the errors both in the menu text and the large background image. I don't know how to describe the issue, it looks like occasionally two adjacent pixels are swapped, but I feel it's very apparent in the attached image.[attachment=0]GZdoom rendering error small.png[/attachment]