Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.15f2
2021.1
2021.2
2022.1
Issue ID
1358617
Regression
No
FilteringSettings.excludeMotionVectorObjects does not exclude moving objects from rendering
Reproduction steps:
1. Open the user's attached "SRP Bugs.zip" project
2. Open the "SampleScene" Scene
3. Enter the Play mode
Expected result: Unity renders a white Plane
Actual result: Unity renders a white Plane and moving red Spheres
Reproducible with: 2019.4.29f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b8, 2022.1.0a5
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
- “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
Resolution Note:
This issue is by design. The current project lack an implementation of the "Motion vector" pass to work in the unlit/unlit shader.
The documentation is not clear enough about what the flag excludeMotionVectorObjects is doing and will be updated to avoid confusion.