Search Issue Tracker
Fixed
Fixed in 2.3.X
Votes
0
Found in [Package]
2.3
Issue ID
SPLB-167
Regression
No
High CPU usage when Spline Evaluate functions are used
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/Endless.unity” Scene
3. Open the Profiler (Window > Analysis > Profiler (Standalone Process)
4. Press the “Deep Profiler” button
5. Type “evaluate” in the search bar
6. Enter the Play Mode
7. Press the “~” key on your keyboard
8. Type “SpawnEnemy Tapeworm 1 false” and press the “Enter” key
9. Wait for the GameObject to spawn and observe the Profiler
Expected result: Spline Evaluate functions do not use a lot of processing resources
Actual result: Spline Evaluate functions use a lot of processing resources resulting in a drastic plummet in FPS
Reproducible with: 2022.3.1f1, 2023.1.0b18, 2023.2.0a16
Could not test with: 2020.3.48f1 (error CS0234, error CS0246 and multiple error CS8124, error CS1526 and error CS1003 in Splines package), 2021.3.25f1 (three error CS1061)
Reproducible on: Intel MacOS 13.3.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Infinite inertial tensor rotation values are not discarded (both AB and RB)
Add comment