Search Issue Tracker
By Design
Votes
0
Found in
2022.3.38f1
Issue ID
UUM-76030
Regression
No
Frame Debugger missing "MotionVectors" pass when Temporal Anti-Aliasing and Per Object Motion are enabled
How to reproduce:
1. Open the attached “IN-80298“ project
2. Open “SampleScene”
3. Enter Play Mode
4. Open and enable the Frame Debugger (Window → Analysis → Frame Debugger)
5. Notice that there is a single draw call under the “MotionVectors” pass
6. Disable the Frame Debugger
7. Click “Capture the current view and open in RenderDoc” button
8. Check the “MotionVectors” pass in RenderDoc
Expected results: RenderDoc logs are identical to those from the Frame Debugger
Actual result: There is a “DrawSRPBatcher” pass under the “MotionVectors”
Reproducible in: 2022.3.38f1, 2023.1.20f1
Not reproducible in: 2023.2.0b1, 6000.0.11f1
Could not test with: 2021.3.40f1 (No “MotionVectors“ pass in the Frame debugger), 2023.2.0a1 (unresolvable package version issues), 2023.2.0a22 (unresolvable package version issues)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
* Unable to find a fixed version in between 2023.1.20f1 and 2023.2.0b1 due to unresolved package version issues
* The “DrawSRPBatcher” will show up in the Frame Debugger if the “MeshRenderer” is changed to the “SkinnedMeshRenderer”
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Motion Vectors are not rendered for dynamic objects in 22.3.
This behaviour was changed in 23.2.
RenderDoc shows the correct capture as the Playmode is not paused.
Is not something about the tool, is something about the implementation of the motion vectors and how the prev and current object matrices are handled to know if the motion vectors should be rendered.