Open illwieckz opened 1 week ago
We may even display something on the UI, like a subtle icon on a corner of the screen, so when looking at screenshots with bugs we would immediately know that at least one experimental feature is enabled.
We could also only add it when taking the screenshot, but not otherwise. Although the disadvantage of that would be that it wouldn't show up on a video recording.
That can be a simple (and very small) !
character on a corner (like the bottom right one), not very annoying.
I like having more space on my screen to actually see what's going on :p
Also, all of the corners are taken already.
Also, such extra mark could be disabled by a cvar (for doing screenshots for communication purpose), but it would be enabled by default when experimental features are enabled.
That'd work I suppose.
In the linux kernel, when you have at lease one single tainted module (a module not compliant with the license), it reports explicitly that a tainted module has been loaded, whatever the tainted module is loaded, and you can know a tainted module is loaded without having to read every line saying a module is being loaded, and without checking each module one by one.
So I wonder if we could do the same for experimental system features (like experimental renderer stuff that could crash the game). So maybe we can add some
EXPERIMENTAL
flag to some cvars like material system or GPU culling, and when related cvars are ebabled, we could print in log “experimental features are enabled!!!” or something like that.We may even display something on the UI, like a subtle icon on a corner of the screen, so when looking at screenshots with bugs we would immediately know that at least one experimental feature is enabled.