Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a11
2023.2.0a1
Issue ID
UUM-14527
Regression
No
[WebGL] Depth of Field is less blurry in Build when compared to Game View
How to reproduce:
1. Open the attached project "DoFTest.zip"
2. Build and Run the Scene "SampleScene" for WebGL
3. Compare the view in Build and in the Game View of the Editor
Expected result: Game View matches the Build
Actual result: Background objects in Game View are more blurry than in the Build
Reproducible with: URP 12.1.7 (2021.3.10f1), 13.1.8 (2022.1.17f1), 14.0.3 (2022.2.0b8), 15.0.1 (2023.1.0a11)
Could not test with: 2020.3.39f1 (WebGL build fails)
Tested on:
- Google Chrome (105.0.5195.102) on macOS 12.3 (Intel)
Notes:
- On 2023.1.0a11 a non-working build is created unless "Development Build" is checked in Build Settings
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.