Add warnings for unsupported features in mobile and gl_compatibility backends#73959
Conversation
There was a problem hiding this comment.
We might want to add here that if fog is enabled and multiview shaders are enabled, that we note that volumetric fog does not yet work in stereo rendering as well.
Something I still have on my list of tasks
BastiaanOlij
left a comment
There was a problem hiding this comment.
This looks really good, sorry I didn't get to it first :)
3471a68 to
b0e4366
Compare
|
Tested, seems to work well aside from this which is a bit annoying: Any GL compatibility project (even empty, without any custom WorldEnvironment) prints this: Seems to come from the default value of |
b0e4366 to
c69b14e
Compare
|
Force pushed with the addition of: To |
|
Thanks! |
| } | ||
|
|
||
| if (uses_sss) { | ||
| WARN_PRINT_ONCE_ED("Sub-surface scattering is only available when using the Forward+ rendering backend."); |
There was a problem hiding this comment.
| WARN_PRINT_ONCE_ED("Sub-surface scattering is only available when using the Forward+ rendering backend."); | |
| WARN_PRINT_ONCE_ED("Subsurface scattering is only available when using the Forward+ rendering backend."); |
|
|
||
| #ifdef DEBUG_ENABLED | ||
| if (uses_sss) { | ||
| WARN_PRINT_ONCE_ED("Sub-surface scattering is only available when using the Forward+ rendering backend."); |
There was a problem hiding this comment.
| WARN_PRINT_ONCE_ED("Sub-surface scattering is only available when using the Forward+ rendering backend."); | |
| WARN_PRINT_ONCE_ED("Subsurface scattering is only available when using the Forward+ rendering backend."); |
|
@Iniquitatis This PR has already been merged, feel free to open another PR with the changes you have suggested! |
Closes #55880
This PR does a few things:
WARN_PRINT_ONCE_EDmessages when features that are unsupported are used@BastiaanOlij and I discussed and agreed that we should stop hiding "high end" features in the editor as it was often creating an awkward situation for users where they would enable something, switch to the low end backend, and then they couldn't disable the thing without switching back. Similarly, we often got reports about missing features because the feature didn't appear in the editor. Having a toast pop up with a warning is preferable as it clearly communicates the lack of the feature and allows users to turn the feature off if it is turned on.