Search Issue Tracker
By Design
Votes
2
Found in
5.6.0f3
Issue ID
898848
Regression
Yes
[Splashscreen] SplashScreenRender takes up CPU time on multiple platforms when disabled
Reproduction Steps:
1. Import attached project.
2. In Player Settings, disable "Show Splash Screen".
3. Build and Run with "AutoConnect Profiler" enabled.
4. Select frame 2.
5. Observe SplashScreenRender.
Expected result: SplashScreenRender should not take up Time ms. (Image attached)
Actual result: SplashScreenRender takes up about 0.29 - 1.5 ms.
Reproducible with: 5.6.0f3, 2017.1.0a6
Not reproducible with: 5.5.3f1
Comments (3)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
karl_jones
Apr 25, 2017 15:09
Its not actually the splash screen doing this. Its the drawing of the Watermark that happens in Developer mode, it just so happens to be done in the area that the splash screen is also drawn. We will improve the label.
jonnyboy1969
Apr 23, 2017 12:25
Me too.
samizzo
Apr 17, 2017 10:32
I see this too.