Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0b18
2023.3.0a14
Issue ID
UUM-55666
Regression
No
Volumetric Clouds change to bright unnatural colors when certain Shape presets are selected with the Light in a sunset or sunrise position
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Open the "Assets/OutdoorsScene.unity" scene
3. Enter the Play Mode
4. Observe the Game view
Expected result: Clouds do not appear with bright unnatural colors
Actual result: Clouds appear with bright unnatural colors
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a14
Reproducible on: macOS Ventura 13.6 (M1 Max), Windows 10
Not reproducible on: No other environment tested
Note:
-Issue is reproducible with Volumetric Clouds Shape presets “Overcast” and “Stormy” while the “Sun” GameObject Light is in a sunset or sunrise position
-On version 2021.3.32f1, the Scene view turns black and artifacts in the Game view can be seen after leaving the Play Mode and rotating the “Main Camera” GameObject Camera
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
Seems to be happening due to color drift in the ambient probe computation
Closing as won't fix as this only happens when using extreme exposure values
Resolution Note (2023.3.X):
Seems to be happening due to color drift in the ambient probe computation
Closing as won't fix as this only happens when using extreme exposure values