[3.x] Tweak default sky appearance to avoid blue tint in shadows in new projects #62825
+12
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3.x
version of #57993.This change only affects projects created after this PR is merged, as only the initial
default_env.tres
file contains the new values. Creating a new ProceduralSky in the editor or via code will keep using the old defaults for compatibility reasons.Given the above precaution is taken for backwards compatibility, I think this is safe to try out for 3.5. Performance should be identical compared to before, as we're only tweaking default colors. We can consider further changes to the default environment for 3.6 (such as using ACES Fitted by default like in #49736).
Testing project: environment_tweaks_3.x.zip
Applying to existing projects
If you wish to apply the new defaults in an existing project:
default_env.tres
(located at the project root) with a text editor.default_env.tres
file. You can specify its path later in the Project Settings.Preview
GLES3, no GI, Linear tonemapping
GLES2, no GI, Linear tonemapping
GLES3, no GI, ACES Fitted tonemapping (whitepoint set to 6.0)
GLES3, GIProbe (propagation set to 0.0), Linear tonemapping
Comparison between 3.x and 4.0
No GI and ACES Fitted tonemapping on both screenshots.
3.x appears brighter, as the fallback material in 3.x is much brighter than it is in 4.0. We could compensate for this by decreasing the default sky contribution to 0.6, but users would then have to set it back to 1.0 after loading a custom sky. We can also tweak the fallback material appearance instead.