Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
10.8.1
Issue ID
1405265
Regression
No
[HD RP] Motion Blur isn't applied to Alembic models when Camera doesn't have a motion
How to reproduce:
1. Open the user's attached "MotionBlur_HDRP" project
2. Enter the Play Mode in the "ExampleShot" Scene
3. Observe the Alembic models in the Game view
Expected result: Motion Blur is applied to Alembic models
Actual result: Motion Blur isn't applied to Alembic models until the models Material is selected in the Project Browser (e.g., Default Material)
Reproducible with: 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.30f1)
Couldn't test with: 12.1.5 (2021.2.14f1), 13.1.6 (2022.1.0b10), 14.0.0 (2022.2.0a7) (Alembic Models are broken)
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:
It looks like the issue might lie in the velocity data, if you select Interpolate Samples in the alembic asset to compute velocities procedurally it seems that all is fine.