Search Issue Tracker
By Design
By Design in 6000.2.X
Votes
0
Found in
2022.3.50f1
6000.0.23f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-84121
Regression
No
Motion Blur has sharp edges when object is moving in the foreground of another object
Steps to reproduce:
1. Open the attached "Repro" project
2. Open "MatrixPrevious" Scene
3. Enter Play mode and observe the moving GameObjects
Actual results: Motion Blur of moving GameObjects has sharp edges when when they are moving in the foreground of a Plane GameObject
Expected results: Motion Blur has smooth edges
Reproducible with versions: 2022.3.50f1, 6000.0.23f1
Could not test with: 2021.3.44f1 (due to entities package errors)
Tested on (OS): macOS Sonoma 14.5 (Intel)
Notes:
- Issue is also reproducible in the Player
- Issue is not reproducible on Windows 11 Pro
- Issue is only reproducible when the non-moving GameObject is positioned below moving GameObjects
- Issue might appear after 2-3 minutes depending on the speed of the moving objects
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
The algorithm is working as designed. This is an occlusion problem that exists in the motion blur implementation of all existing engines.
We'd need to make a new motion blur effect to solve this problem and right now this is not something we plan to investigate
Resolution Note (6000.2.X):
The algorithm is working as designed. This is an occlusion problem that exists in the motion blur implementation of all existing engines.
We'd need to make a new motion blur effect to solve this problem and right now this is not something we plan to investigate