Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
10.2.0
Issue ID
1288704
Regression
Yes
[iOS][URP] Bloom is too intense in the URP scenes on iOS
How to reproduce:
1. Open the attached project or create a new URP template project
2. Build & run on device
Expected result: No issues
Actual result: Bloom is too intense
Reproducible: 2020.2.0b7 (URP 10.0.0-preview.26), 2020.2.0b10 (URP 10.2)
Devices
Reproducible on:
VLNQA00158 iPhone X A11 14.0.1
Not reproducible:
VLNQA00090, Samsung Galaxy S8 (SM-G950U), Android 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
----------, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
VLNQA00340, Samsung Galaxy Note20 Ultra 5G (SM-N986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00269, Samsung Galaxy S10e (SM-G970F), Android 9, CPU: Exynos 9 9820, GPU: Mali-G76
----------, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00103, Samsung Galaxy Note8 (SM-N950F), Android 7.1.1, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Notes:
- Same issue was reproduced with UniversalRenderingExamples scenes: https://github.com/Unity-Technologies/UniversalRenderingExamples
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment