Search Issue Tracker
Fixed
Fixed in 6000.0.X
Votes
10
Found in
2022.3.4f1
2023.2.15f1
6000.0.0b12
Issue ID
UUM-43568
Regression
No
Discrepancy between the Render Texture and the actual render when using the Camera.Render method and the Light Probe System is set to Light Probe Groups
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/DemoScene.unity” Scene
3. In the Hierarchy Window select “DemoCamera” GameObject
4. In the Inspector Window, observe the “DemoCamera” preview
5. In the Game View, observe the “Sphere” GameObject
Expected result: “Sphere” GameObject has the same lightning in both instances
Actual result: In the “DemoCamera” preview, “Sphere” GameObject has darker lightning
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.4f1
Could not test with: 2023.2.0a23 (multiple Compute Shader errors in Assets/RenderCamera.cs Script)
Reproducible on: Intel macOS 13.4
Note: For the reproduction to occur these settings must be toggled:
- Under “DemoCamera” GameObject’s “Render Camera (Script)” Component, “Render Camera Manually”
- Project settings > HDRP > Lightning > Light Probe Lightning > Light Probe System > Light Probe Groups
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment