Search Issue Tracker
By Design
Votes
0
Found in [Package]
preview - 6.5.3
Issue ID
1149723
Regression
No
[HDRP] Meshes close to the Camera create artifacts around them when in motion and Motion Blur is enabled
How to reproduce:
1. Open the attached "case_1149723-HDRPMotionBlur.zip" project and open "SampleScene"
2. Enter Play mode
3. Using WASD, try walking near the wall and inspect the torch
Actual results: There are artifacts around the torch
Reproducible with: HDRP 5.13.0 (using 2019.1.2f1, 2019.2.0b1, 2019.3.0a2), HDRP 6.5.3 (using 2019.2.0b1, 2019.3.0a2)
Note: Couldn't test in 2018.4.0f1 due to package errors.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
This is a side effect of the algorithm we use (it is tile based, so to a certain extent you will see bleeding of motion vectors). With lower intensities this should be less noticeable. For now we'll close it as by design, but I'll keep a note so that if we revisit motion blur this problem might get addressed.