Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
5
Found in
2019.3.2f1
2019.3.7f1
2020.1
2020.2
Issue ID
1233944
Regression
Yes
Mesh API calls causes slowdown in Play Mode
How to reproduce:
1. Open the attached 'InfiniGRASS_SUBMIT2019.3_URP.zip' project
2. Open 'Open DEMO v1.7 SCRIPTED INTERACTIVE GRASS DEMO URP' Scene
3. Enter Play Mode
4. Open Window > Analysis > Profiler
5. Observe ControlCombineChildrenINfiniDyGrass.LateUpdate() CPU usage
Expected result: Separate Mesh API calls such as Mesh.GetTriangles() takes up to 1% of total CPU usage
Actual result: Separate Mesh API calls such as Mesh.GetTriangles() takes from 11% to 23% of total CPU usage
Reproducible with: 2019.3.2f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a10
Not reproducible with: 2018.4.22f1, 2019.3.1f1
Notes:
- Screenshots of the issue are attached in Edit
- When entering Play Mode Editor lags/freezes for a minute
- Reproducible with:
OS: 10.15.4, CPU: 2.4 GHz 8-Core Intel Core i9 GPU: AMD Radeon Pro 5500M 8GB
OS: Win10, CPU: Intel(R) Core(TM) i7-9700K 3.60GHz, GPU: NVIDIA GeForce RTX 2060 6GB
OS: Win10, CPU: i7-6900k (8 cores), GPU: NVIDIA GeForce 1080TI
- Not reproducible with:
OS: 10.14.6, CPU: 2,5 GHz Intel Core i7, AMD Radeon R9 m370X 2GB
OS: Win10, CPU: i7-6700, GPU: NVIDIA GeForce 960M
OS: Win10, CPU: Intel i7-7600U 2.8 GHz, GPU: Intel HD Graphics 620
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
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b10
Resolution Note (fix version 2019.3):
Fixed in 2019.3.15f1