Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.1.0f3
Issue ID
935938
Regression
Yes
Editor FPS drops from >200 to <60 when there are GameObjects with particle system selected
Editor FPS drops from >200 to <60 when there are GameObjects with particle system selected. Also CPU usage seems more unstable (refer to attached image)
Reproduction steps:
1. Open attached project
2. Open the scene Nuclear
3. Open profiler
4. Enable Editor profiling
5. Select all game objects in the scene
Cpu usage increases and becomes less stable
Drops to ~2-3 FPS on 2017.2.0a1 onwards
Reproduced on: 5.5.4p2, 5.6.0a1, 5.6.3f1, 2017.1.0f3, 2017.1.0p2, 2017.2.0b5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Camera.current returns null when Camera.targetTexture is set to null in OnPostRender
- Crash on BaseHierarchyProperty::Next when opening a specific project
- ShaderLab pragmas are no longer allowed in regular include directives
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
Add comment