Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.22f1
Issue ID
UUM-36299
Regression
Yes
Exposure information is carried to the next scene when using Volumetric clouds
Reproduction steps:
1. Open the attached “VolumetricCloudsBugProject” Project
2. Open the “Assets/Scene1.unity“ Scene
3. Enter the Play mode
4. Press the “C” key and notice the change in scenes
5. Build and run the Player
6. In the Player, repeat 4th step
Expected result: The lighting is the same both in the Editor and the Player
Actual result: The lighting in the built Player is different from the Editor
Reproducible with: 2021.2.14f1, 2021.2.19f1, 2021.3.22f1
Not reproducible with: 2020.3.47f1, 2021.2.13f1, 2022.2.15f1, 2023.1.0b12, 2023.2.0a10
Could no test with: 2022.1.0a1 - 2022.1.0a10 (Assets could not migrate correctly)
Fixed in: 2022.1.0a11
Reproducible on: Intel MacOS 13.3, Windows 10 22H2
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
Hi, we acknowledge there is an issue on 21.3 (fixed on other versions). However we don't have the resources today to look at this issue on this version and we are closing it. If this issue is really important for you please re-open it.