View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0021591||2.x IDE Bugs||Image Editor||Public||2016-05-20 10:32||2021-07-19 09:43|
|Reporter||Sam Cumming||Assigned To||CoreTech|
|Priority||None||Severity||C - General||Reproducibility||100%|
|Platform||OS||Windows 8||OS Version||8.1 Pro|
|Target Version||Fixed in Version|
|Summary||0021591: Image Editor: Arc Tool causes large FPS drop if a high number of points are created|
|Description||Extreme usage of the Arc tool causes a large FPS drops on two occasions.|
1. If there are many points to the arc, and the arc is being dragged around, the FPS will drop significantly as it calculates the spline.
2. If there are many points to the arc, the IDE FPS will degrade due to the number of UI elements present.
After about 50 points, FPS will halve.
Extreme usage (400+ points at high iterations) causes the IDE to drop to an idle FPS of ~5fps, and active arc tool usage to ~0.9fps.
The larger the distance between each spline point, the larger the FPS drop.
|Steps To Reproduce||1. Create/Open a 2016 project.|
2. Create/Open a sprite.
3. Open the Image Editor.
4. Enable the Debug Info view
5. Select the Arc Tool.
6. Draw many arc points, dragging them around occasionally.
7. Observe significant FPS drop.
|2.x IDE Found In||0.0.6.139|
|2.x Runtime Found In||0.0.1.23|
|2.x IDE Verified In|
|2.x Runtime Verified In|
Arguably, you're using it wrong with 400+ points...
However, immediate idea is to merge each stage to a separate texture so that it's only the last two knots which are dynamic.
Problem with that is if the user then goes and tries to modify a previous knot, the whole thing needs recalculated again anyway... though I suppose it could just change the current active sets, and bake the rest.
Same thing could be applied to the Polygon tool, as it'll likely have the exact same issue.
No longer reproduces in v2.3.3. Closing.