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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment