Welcome to the ZDoom Forums!

It's a quite weird story about those weapons on saved games thumbnails.
It appeared to be inconsistencies between renderers, between the same renderer but different versions, and between various options in a particular version.
IMHO we need to stick to one decision regardless of renderers, setting, etc. Or probably to make this an option, which it seems a bit more complicated.

Works fine here too, and iirc the weapon has never been visible before.

This may be a matter of preference but IMO the thumbnails should have the weapon art baked in.

Works fine for me in every combination of post-processing effects I tried.

I just noticed one discrepancy with saved game thumbnails.
When bloom is enabled player's weapon is visible, without post-processing or with any other effect(s) it's hidden.
Actually, what is the correct behavior? Should weapon be visible on these pictures?

Please try again now. I pushed a commit that I think fixes this.

It's the same issue. Most of postprocessing effects break saved game thumbnail in one way or another.

I also have a savegame thumbnail issue that might be related:
[attachment=0]FXAA-Savegame.png[/attachment]

This happens under Windows 10 (build 10.0.16299.431) when FXAA is enabled. I used a new INI file and simply enabled FXAA (doesn't matter which quality setting)

Okay, I'll take a look soon. Based on the screen shots, it probably has something to do with glViewport not being what the screenshot code reading from the back buffer expects.

I'll leave this to dpJudas then. Apparently I missed something important about the setup and I do not want to make it worse.

It should be enough to have [b]gl_tonemap 1[/b] and everything else by default.
BTW tonemap and lens distortion give even more weird picture

[attachment=0]savepic.png[/attachment]
Screen resolution is 1440x900, thumbnail size is 216x162 and this corresponds to black rectangle in the corner.
This seems to be introduces with [url=https://github.com/coelckers/gzdoom/commit/67cb6e63b57e52fb95e31e5802f3ed7758ff2449]this commit[/url] and it's somehow related to switching of render buffers target textures.

I cannot reproduce this with any tonemap (or other postprocessing) effect.

I managed to reproduce this on Windows. Enable tone mapping (set [b]gl_tonemap[/b] CVAR to true) and the bug will appear.

Thought I'd give it a go with your INI and a current Git build (2d50f535ff666a9cb0a0d3fe97c31f07e5a6f9a8) but couldn't reproduce. Am running Debian Stable, but also an ancient Intel GM45, so don't put too much faith in this. It could well be system-dependent though.

[url]https://marisakirisa.me/tmp/gzdoom.ini[/url]

(refresh if it gave you a 403, seems like the permissions got a bit screwy when I uploaded the file)

Cannot reproduce this on Ubuntu 16.04 VM. Could you please attach your .ini file?