Search Issue Tracker
By Design
Votes
0
Found in
2022.3.45f1
6000.0.18f1
Issue ID
UUM-79674
Regression
Yes
[Mobile] Shader.WarmupAllShaders takes from 0.8s to 1.5s longer on 2022.3.10f1 and higher
Steps to reproduce:
1. Open the attached user's project "ShaderWarmup2022.zip"
2. Switch to Android and build
3. Once application launches, press the "Warmup All Shaders" button
4. Observe the time it takes to warmup the shaders
Expected results: Shader.WarmupAllShaders time is similar to 2021.3
Actual results: Shader.WarmupAllShaders takes from 0.8s to 1.5s longer on 2022.3.10f1 and higher
Reproducible with: 2022.3.10f1, 2022.3.45f1, 6000.0.18f1
Not reproducible with: 2021.3.43f1, 2022.3.9f1
Reproducible with these devices:
VLNQA00381, Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
VLNQA00528, Hmd Global Nokia G20 (Nokia G20), Android 13, CPU: Mediatek MT6765G Helio G35 (12 nm), GPU: PowerVR Rogue GE8320
VLNQA00547, Samsung Galaxy Tab A8 (SM-X200), Android 13, CPU: Unisoc Tiger T618, GPU: Mali-G52
Not reproducible:
VLNQA00282, Samsung Galaxy S10e (SM-G970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00423, Google Pixel 3 (Pixel 3), Android 9, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00422, Samsung Galaxy S21 Ultra 5G (SM-G998B), Android 11, CPU: Exynos 2100, GPU: Mali-G78
Testing Environment: Windows 11
Not reproducible on: no other environment tested
Notes:
-Issue reproduces on iOS according to the customer
-Issue reproduces with OpenGLES and Vulkan Graphics APIs
-With the affected devices, the Shader.WarmupAllShaders takes around 0.8s - 1.5s on 2022.3.10f1, while on 2022.3.9f1 it takes around 0.1s - 0.2s
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
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note:
This is caused by a fix to another issue. Before the fix it would warm up only the first variant per shader pass and skip the rest.