Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.17f1, 2023.1.0b14, 2023.2.0a4
Votes
0
Found in
2021.3.16f1
2022.2.1f1
2023.1.0a26
2023.2.0a1
Issue ID
UUM-22368
Regression
No
[VFX/SG] Wrong Motion Vector on Mesh using SG
Step to repro:
- Import attached package in project in HDRP
- Switch to debug motion vector
- Observe unexpected constant value pointing top left corner of the game view
Expected: Same motion vector than without SG
Workaround: Switch output mesh to another output mesh (lit or unlit), it will clean up unexpected values.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment