Search Issue Tracker
Won't Fix
Votes
1
Found in
2023.3.0b3
Issue ID
UUM-61870
Regression
Yes
[URP][TAA?] Motion vectors cause GameObject flickering when in the Play mode
Reproduction steps:
1. Open the attached “Flickering.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Observe the “Cube” GameObject in the Game view
Expected results: No flickering is observed
Actual result: GameObject is flickering
Reproducible with: 2023.3.0a18, 2023.3.0b3
Not reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0a17
Reproducible on: Windows 11
Not reproducible on: no other environment tested
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
- 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
Resolution Note:
No new evidence of a bug was provided.
Motion vectors were double checked. Motion vectors are fully functional. Note that motion vector values in the target are signed and very small +-1/(width, height).