Search Issue Tracker
Fixed
Fixed in 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Votes
0
Found in
2022.3.21f1
2023.2.14f1
6000.0.0b12
Issue ID
UUM-66503
Regression
Yes
MotionVector is rendered after the GameObject when the Material Surface Type is Transparent
How to reproduce:
1. Open the “2022.2.2f1_motionVectors“ project
2. Open the “SampleScene“
3. Select Window → Analysis → Frame Debugger
4. Enter Play mode and press Enable on the Frame Debugger window
5. Observe the Frame Debugger
Expected result: “Motion Vectors“ is seen before “DrawTransparentObjects“
Actual result: “Motion Vectors“ is seen after “DrawTransparentObjects“
Reproducible with: 2022.2.2f1, 2022.3.21f1, 2023.2.14f1, 2023.3.0b10
Not reproducible with: 2021.3.36f1, 2022.2.1f1, 6000.0.0b11
Fixed in: 6000.0.0b11
Reproducible on: Windows 10, macOS 12.6.7 (M1) (user device)
Not reproducible on: No other environment tested
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2022.3.23f1):
MotionVector pass now follows its copy depth texture dependency, which pass order is configurable from the renderer asset.