Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2023.1.0a2
2023.1.0a4
Issue ID
UUM-9525
Regression
Yes
[URP] Motion Blur is not displayed correctly, motion is not calculated
Steps to reproduce:
- Open attached project and open SampleScene
- Observe that Main camera has post processing enabled
- Observe that Global Volume contains Motion Blur
- Enter Game View and notice that view is blurred, but cube is static
- Disable Motion Blur, notice that cube is displayed correctly
Expected result: Motion Blur should not show any motion on a static image, motion should be calculated correctly
Reproduced in: 2023.1.0a4, 2023.1.0.a2
No repro in: 2023.1.0a1
Regression since: 2023.1.0.a2
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.1.X):
No repro. My recent changes that landed refactored the matrix tracking for motion vectors. There's a chance it has fixed the issue.
I tested on (intel) Mac
on
2023.1.0a4.431
Revision: trunk 77dfbc7234b7
Built: Thu, 21 Jul 2022 16:06:38 GMT
with and without latest URP package from trunk.