Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0b9
Issue ID
886498
Regression
Yes
When pressing on error, it takes some time to get to the selected object in hierarchy while there is low FPS
Reproduction steps:
1. Open project attached(LowFPS.zip)
2. Open scene "ExampleFSMScene" from Assets -> Unity -> Editor -> FSMExample
3. Disable particle system.
4. Press play.
5. Wait till error appears (game should get paused, so press click on pause button to continue). Repeat twice.
6. Enable particle system.
7. Press on Errors that appeared (there should be low fps, you can adjust it by changing the amount of particles).
8. Inspect hierarchy when pressing on errors.
Expected result: Object that caused error will be shown instantly in hierarchy.
Actual result: It takes some time to get to the selected object.
Reproduced on: 5.6.0b3, 5.6.0f2, 2017.1.0a5.
Works fine in: 5.5.2p4.
Regression introduced in: 5.6.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #880331