-
-
Notifications
You must be signed in to change notification settings - Fork 978
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
Exclude UI from PostFx by default #1154
Comments
As UI can be used also in 3D positioned in the scene, it should be excluded from post-FX only if they are marked as fullscreen or something. If not, elements in the scene would be overly bright and incorrect as they avoid tonemapping and other effects the surrounding geometry are affected by. |
I am new to Stride, did a bit experimenting with Unity, I am beginner and I agree with @manio143. When we set white colour font for the UI you can't send us to a tutorial and do some ceremony to get the white colour working 🤣. |
I think this can be implemented. |
I also want it for code-only approach. There is one already in Stride var graphicsCompositor = GraphicsCompositorHelper.CreateDefault(true);
// edit graphicsCompositor so the white is white or I can just create another one and correct the white there In my case, it would be good to know how this GraphicsCompositor affects the performance but I can play with that once there is a time for that. Not sure what needs to be changed in the Stride Studio so the template also have it, or even having a UI to switch it on if there is a reason for some to have it off? |
Is your feature request related to a problem? Please describe.
It's not expected by users that UI will be rendered with PostFx applied in the default project setup. This comes up often and we direct people to a tutorial on changing it (https://github.com/herocrab/StrideCleanUI https://www.youtube.com/watch?v=cazIR97VPcg)
Describe the solution you'd like
Modify default GraphicsCompositor according to the tutorial and set the default render group in the UI component accordingly.
The text was updated successfully, but these errors were encountered: