Search Issue Tracker
Fixed
Fixed in 5.0.x
Votes
0
Found in [Package]
5.0.7
Issue ID
PBLD-73
Regression
No
Severe performance degradation when the "ProBuilder" window is opened in Play Mode
How to reproduce:
1. Open the “MultiplayerRTS“ project
2. Open the “Main” scene
3. In the Game view window enable the “Rendering Statistics” window (“Stats” button)
4. Enter Play Mode and observe the “FPS” field in the “Rendering Statistics” window for 3-5 seconds
5. Open the “ProBuilder” window (Tools > ProBuilder > ProBuilder Window) and observe the “FPS” field in the “Rendering Statistics” window for 3-5 seconds
Expected result: performance does not decrease and stays at about 600 FPS when the “ProBuilder” window is opened
Actual result: performance decreases by 100-300 FPS when the “ProBuilder” window is opened
Reproduced with: 5.0.1, 5.1.0 (2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a22)
Reproduced on: Windows 10 (by reporter), Windows 11
Notes:
1. For the 2023.2 stream a separate project has been provided where scripting errors have been fixed - “MultiplayerRTS_2023.2“
2. Depending on the Editor version the amount of performance that is decreased varies
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Image is distorted when VisualElement is scaled and Scale Mode set to scale-and-crop
- Euler angles return different values during Animation Event when using Playables API and the time is 0
- Editor is frozen on "Reloading Domain" when entering Play Mode for the second time using Socket.Poll(-1, ...)
- Empty GameObjects are created without Skinned Mesh Renderers when using AnimatorUtility.DeoptimizeHierarchy() on FBX files with same-named GameObjects
- Snapshots don't work for exposed parameters after using SetFloat
Add comment