Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.62f1
6000.2.12f1
6000.3.0b10
6000.4.0a4
6000.5.0a1
Issue ID
UUM-127954
Regression
No
Motion blur is forced and exaggerated through transparents when "Sort with Refractive" and Motion blur is enabled
Reproduction Steps:
1. Open the attached "IN-121000_REPRO_v2" project
2. Open the “/Assets/OutdoorsScene.unity”
3. Enable “Screen2” object
4. Enter Play mode
5. Observe the Game view
Expected Result: No motion blur is visible
Actual Result: Exaggerated motion blur is visible
Reproducible with: 2023.3.0a9, 6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a4, 6000.5.0a1
Could not test with: 2023.1.0a1, 2023.3.0a3 (HDRP material components for this reproduction unavailable)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Workaround: Disable "Motion Vectors" on the transparent screen object in Mesh Renderer (does not work for World-space UI elements)
Notes:
- MeshRenderer object has its "Motion Vectors" set to "Force No Motion"
- Affects both MeshRenderer and world-space UI elements
- Camera Frame Settings: "Transparent Motion Vectors" is disabled
- Motion Blur is enabled in a global Volume
- "Sort with Refractive" automatically enables "Transparent Writes Motion Vectors" on affected transparent materials
- The scene includes a "CanvasScreen" object (world-space UI) using the same material; it exhibits the same exaggerated motion blur
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment