Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Obvious report of experimental feature enablement #1403

Open
illwieckz opened this issue Oct 30, 2024 · 5 comments
Open

Obvious report of experimental feature enablement #1403

illwieckz opened this issue Oct 30, 2024 · 5 comments

Comments

@illwieckz
Copy link
Member

illwieckz commented Oct 30, 2024

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.

@VReaperV
Copy link
Contributor

VReaperV commented Oct 30, 2024

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.

@illwieckz
Copy link
Member Author

illwieckz commented Oct 30, 2024

That can be a simple (and very small) ! character on a corner (like the bottom right one), not very annoying.

@VReaperV
Copy link
Contributor

I like having more space on my screen to actually see what's going on :p

Also, all of the corners are taken already.

@illwieckz
Copy link
Member Author

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.

@VReaperV
Copy link
Contributor

That'd work I suppose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants