Search Issue Tracker
Feature Request
Votes
4
Found in
2023.1.0b20
2023.2.0a18
Issue ID
UUM-37788
Regression
Yes
Motion Vectors are incorrect when using Graphics.DrawMesh
How to reproduce:
1. Open the attached “Vector.zip” project
2. Open “OutdoorsScene”
3. Enter Play Mode or Build And Run
Expected result: Right cube is not rendered blurred
Actual result: Right cube is rendered blurred
Reproducible with: 2023.1.0a18, 2023.1.0b20, 2023.2.0a18
Not reproducible with: 2021.3.26f1, 2022.3.0f1, 2023.1.0a17
Reproduced on: Windows 10, Windows 11 (user’s machine)
Notes:
- Left cube is rendered with MeshRenderer. Right cube is rendered with Graphics.DrawMesh
- Setting Rendering Debugger’s Fullscreen Debug Mode to MotionVectors (Window > Analysis > Rendering Debugger) will reveal vectors of the cube on the right, indicating the blurry effect
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
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [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”
Resolution Note:
The missing problem of motion vector for DrawMesh is not a bug or a regressoin but just have never been implemented in Builtin... This isn't related to SRP. So it is a feature request to add the support.
However there is an existing alternative, the RenderMesh API have been develop to currently fix all the issues with DrawMesh (which can be modify too much due to backward compatibility). See https://docs.unity3d.com/ScriptReference/Graphics.RenderMesh.html . RenderMesh support the motion vector