Search Issue Tracker
By Design
Votes
0
Found in
5.6.1p1
Issue ID
916137
Regression
No
Setting Material.shader has a huge performance difference between Editor(~250 times slower) and Standalone Player
Reproduction steps:
1. Open the attached project.
2. Check Development Build and Autoconnect Profiler checkboxes in the Player Settings.
3. Build and play the "test" scene as a Standalone.
4. Open Profiler (Window > Profiler).
5. Click on the Active Profiler button and select the Standalone player.
- Profiler doesn't show any spikes and stays at about 4000 fps (screenshot attached).
6. Click on the Active Profiler button and select the Editor.
7. Play the "test" scene in the Editor
- Profiler shows spikes (drop to 15 fps) when setting Material.shader (screenshot attached).
Reproduced with:
5.5.3p4, 2017.1.0b7
macOS, Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
Add comment