Is there something that doesn't work right in the latest GZDoom? Post about it here.
Moderator:GZDoom Developers
Forum rules Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
The savegame won't really help. This looks like the framebuffer readback from the GPU does not work, so the most important things here are:
1. What operating system?
2. What GPU?
3. Is this specific to these maps? If yes, only specific to certain places in the map?
4. What render backend? Does changing this make the problem go away?
1. Windows 7
2. GeForce GTX 1060 3GB
3. It only started happening part way through Sunder map18 and from the beginning of map19
I was able to reproduce it by running GZDoom 4.10.0 with Sunder 2407.wad warping to map19, and clearing the first arena and saving.
4. I was on Vulkan.
OpenGL ES and OpenGL both save display normally when saving, I tried loading a corrupt save and saving it and it displayed properly.