Search Issue Tracker
Fixed in 2022.3.5f1
Fixed in 2022.2.X, 2023.2.X
Votes
0
Found in
2022.2.5f1
2023.1.0a26
2023.2.0a1
Issue ID
UUM-23069
Regression
No
Incorrect motion vectors on the first frame or on the first frame after an Entity has been spawned
Reproduction steps:
1. Open the attached project "HybridHDRPSamples.zip"
2. Open the "MatrixPrevious" Scene
3. Enable Pause and enter Play mode
3.a Step frames forward until the subscene is loaded
4. Open the Rendering Debugger window
5. In the Rendering tab, set Fullscreen Debug Mode to "MotionVectors"
Expected result: The Game view is black
Actual result: Motion vectors pointing away from origin are visible
Reproducible with: 0.51.1-preview.21, 0.51.0-preview.32 (2021.3.8f1)
Could not test with: 2020.3.38f1 (Various errors when downgrading/remaking the project)
Reproducible on: macOS 12.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment