Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.17f1
2023.2.5f1
2023.3.0b2
6000.0.0b11
Issue ID
UUM-60371
Regression
No
Visual Environment on Local Volume applies to outside cameras when a non-camera GameObject is selected
How to reproduce:
1. Open the “BDTest.zip” project
2. Open the “OutdoorsScene”
3. Make sure you can see both the Scene view and the Game view windows
4. In the Hierarchy window select any GameObject except “Main Camera” and “CaptureCam”
5. Move the Scene view in and out of the “LocalVolume” area and observe the Game view window
Expected result: The “Main Camera” is not affected by moving the Scene view into the “Local Volume”
Actual result: The “Main Camera” renders objects as if it was inside the “Local Volume”
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b2
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- If you have either "Main Camera" or "CaptureCam" selected in the Hierarchy view, things will render properly. But if you have anything else selected in the Hierarchy view, then the settings applied to the Scene View camera will incorrectly be applied to the other camera in the scene.
- This appears to only be an issue with the Visual Environment. Other Volume settings don't appear to be incorrectly being applied outside of their local volume.
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
The project uses realtime lightmaps. These are per object and cannot be different for each camera. So if the same object is visible by two cameras who have a different sky, one of the camera will have incorrect results. Disabling realtime global illumination in the lighting window will solve the issue