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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment