Search Issue Tracker
In Progress
Fixed in 2022.3.45f1, 6000.0.18f1
Fix In Review for 2021.3.44f1
Votes
0
Found in
2021.3.40f1
2022.3.37f1
6000.0.11f1
Issue ID
UUM-76307
Regression
No
Incorrect depth values when using "Render Objects" feature
How to reproduce:
1. Open the attached “IN-80085“ project
2. Open the “RenderObjectDepth” scene
3. Enter Play Mode
4. Open and enable Frame Debugger
5. In the “CopyDepth” pass change “Levels“ at the top of the Frame Debugger to range from ‘0' to '0.1’
6. Observe the “Output“ screen
Expected result: Both cubes are the same color
Actual result: The “CubeRenderObject“ is lighter than the “CubeDefault“ object
Reproducible in: 2021.3.40f1, 2022.3.37f1, 6000.0.11f1
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
-
AljoshaD
Sep 02, 2024 08:41
You will need to update the settings of your RenderObject feature for the fix to have effect. The problem was in the UI but the data is serialized and only updated when the settings change.
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
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
Resolution Note (fix version 6000.0.18f1):
the editor of the RenderObject feature always sets cameraOffset.w to 1.
This is added to the current camera position, resulting in a different view matrix. The offset.w needs to be 0.