Search Issue Tracker
Feature Request
Feature Request in 2023.2.X
Votes
0
Found in
2022.2.9f1
2023.1.0b6
2023.2.0a4
Issue ID
UUM-29583
Regression
No
Motion vectors are calculated incorrectly when using TAA
Reproduction steps:
1. Open the "terra" project
2. Open the “Assets/TerrainDemoScene_HDRP/Scenes/TerrainDemoScene.unity” Scene
3. In the Hierarchy Window select “Main Camera” GameObject
4. Observe that TAA is selected under the “Rendering” Component in the “Post Anti-aliasing” Property
5. Observe grass in the Scene View
Expected results: Grass is clearly visible
Actual results: Grass flickers
Reproducible with: 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Could not test with: 2020.3.45f1 (Packages required are not available for this version), 2021.3.20f1 (error CS0246: The type or namespace name 'DetailBrushRepresentation' could not be found (are you missing a using directive or an assembly reference?))
Reproduced on: Intel MacOS 13.1
Note: The issue can be seen more vividly when entering the Play Mode and viewing the Game View
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
Resolution Note:
A preivous fix have been done to fix the very blurry grass. The remaining part
require proper handling of motion vectors for terrain detail meshes and is a feature request, not a bug. For now due to limited resources we don't know when this part could be fixed. - We track the work as a feature request to support motion vector on detail meshes
Resolution Note (2023.2.X):
A preivous fix have been done to fix the very blurry grass. The remaining part
require proper handling of motion vectors for terrain detail meshes and is a feature request, not a bug. For now due to limited resources we don't know when this part could be fixed. - We track the work as a feature request to support motion vector on detail meshes