Search Issue Tracker
Duplicate
Votes
0
Found in
2020.2.0a16
2020.2.0a21
Issue ID
1272076
Regression
Yes
Linux Editor has low performace in Playmode on a new project
How to reproduce:
1. Create a new project
2. In the "Game" window press on the "Stats" button near the top right corner of the window to open the "Statistics" panel
3. Enter Playmode
4. Observe the FPS in the "Statistics" panel
Expected result: the FPS is from 100 to 3000 if not higher
Actual result: the FPS is about 10
Reproducible with: 2020.2.0a16, 2020.2.0a21
Not reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0a15
Notes:
1. Reproducible on Ubuntu 18.04
2. Doesn't reproduce on Windows 10
3. Uninstalling all preinstalled packages doesn't have any effect
Comments (1)
-
APSchmidt
Aug 28, 2020 08:08
Issue #1271213 mentions that this happens in 2020.2.0a15; it doesn't for me. It happens from 2020.2.0a16 on to a21.
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
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
This is a duplicate of issue #1271213