Search Issue Tracker
Not Reproducible
Votes
2
Found in
2017.1.0a1
2017.1.0f3
Issue ID
931625
Regression
Yes
Shader.EditorCompileVariant in 2017.1 takes more time than in 5.6 on large projects
To reproduce:
1. Open project(link in edit) on 2017.1.0f3
2. Open profiler
3. Play 'Stage 1 mechanical' scene (use WASD and mouse button for contol)
4. Notice that sometimes editor has 0.5-2 seconds 'hiccups'
5. Repeat these steps with 5.6.2f1 or 5.6.2p3
Expected vs actual: on 5.6 'hiccups' are always 20-70ms smaller than on 2017.1 or 2017.2
Reproduced: 2017.1.0f2-f3, 2017.2.0b2
Not reproducible: 5.6.2f1, 5.6.2p3
Regression introduced 2017.1.0a1
Comments (2)
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
- “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
shihui142857
Dec 18, 2018 08:25
2017.4.14f1 ----- cause 100 ms in deep profile
Spiral-Organ
Nov 30, 2017 06:39
Present on Unity 2017.3.0b7 as well. Causes very extreme lag spikes (pauses) for a split second. Can be very disorienting to players in a mouse orbit HUD game,