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
- 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
Add comment