Search Issue Tracker
Won't Fix
Votes
5
Found in
2022.2.0a13
Issue ID
UUM-3334
Regression
No
[HDRP] Motion Vectors are not applied to the GameObjects when they're rendered through Terrain
How to reproduce:
1. Open the attached "case_1372553" project
2. Open the "OutdoorsScene" Scene
3. Observe the Game view in the Play Mode
Expected result: The Motion Vector is applied to the grass/foliage. No severe ghosting and blurriness is observed
Actual result: The quality of motioned grass/foliage that is rendered through Terrain is severely ghosty and blurred. The higher the "Camera -> Rendering -> Quality Preset", the worse and blurry the quality of the GameObjects
Reproducible with: 10.7.0 (2020.3.24f1), 12.1.2 (2021.2.6f1), 13.1.3 (2022.1.0b2)
Couldn't test with: 7.7.1 (2019.4.33f1) (project files got corrupted due to downgrading)
Comments (2)
-
PutridEx
Dec 11, 2021 01:40
-
PutridEx
Dec 09, 2021 06:23
Hi,
It seems you misunderstood the bug report, it's not about that higher quality TAA should give better results. TAA documentation states: " The default settings for higher presets are not guaranteed to produce better results than lower presets. The result depends on the content in your scene."The issue is much bigger than that, it's that grass/foliage, when rendered through instancing, it loses motion vectors which TAA needs to do a good job.
Hence in the project you can see a specific grass rendered through terrain 'detail object' looks blurry in comparasion to the other grass which is rendered normally as a mesh placed on the level. Because the latter has motion vectors, and the former (the one rendered through unity's terrain detail object) loses it's motion vectors.And you have to use instancing with grass, otherwise the high density of grass will kill your performance cause of drawcalls and overhead. You have to use instancing/indirect instancing, otherwise you can't have a forest, or any large amounts of grass. which is why terrain uses instancing to render grass.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
There are no fixes planned for this Bug