Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.2.2f1
Issue ID
1313043
Regression
No
Output Mesh uses particle motion vectors even when it is not moving and its shader is not set to support them.
Repro steps:
1. Import the attached project and open the repro scene
2. Enter play mode
3. Observe that both the particles and the capsule (output mesh) are blurred.
Expected outcome:
- Only the moving particles to receive motion blur
Notes:
- Looks like the particle motion vectors are being used for the output mesh
- We also don't have a way of enabling/disabling motion vectors at the Output Mesh level (it can only be done in the shader, which means separate shaders need to be used to just toggle motion vectors on a per-mesh-output basis)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Add comment