spline in design is laggy and extremely slow

[Ketherton21]

so anytime me or a coworker want to engrave an image we just import a picture in design and trace it all with the spline tools, and then use that  geometry to engrave. in the last few days on multiple files and on multiple computers it is almost impossible to trace them in design.

my computer is an i7 with 4gb video card and 16gb ram.

the other computers are only a few weeks old and are the same but with i9's

[wmhazzard]

You have way too many spline points, less is more when it comes to splines. I like to use control point splines for tracing, it is easier to fit the spline to the image. Try and use as few points as possible, it will be much easier on the program. 

[Ketherton21]

I have files with at least 10x the amount of splines that didn't ever lag like this one.

I just completely restarted from scratch and without even a single spline its doing it.

[g-andresen]

Hi,

traces I do automatically in Inkscape, but in Corel or other vector graphics applications it works the same way.
Depending on the template, however, they have to be reworked.

günther

[Ketherton21]

I opened another file and it wasn't doing it. it must just be the format of the image itself I imported. googled the same thing but a different file and it works normally. thxxx

[jeff_strater · Accepted solution]

I agree with @wmhazzard here - this spline has too many points.  My experience with this spline is pretty much what I expect.  As a single spline contains more and more fit points, it definitely slows down, and at some point becomes unusable.  I do use fit point splines to trace images, but I try to keep each spline to under 50, preferably under 30 fit points.  This spline seems to have about 100 points.  Instead, you can string multiple splines together end-to-end, with tangent constraints between each pair.  You will likely get much better performance from that approach.

I'd like to see an example with 10x points (say, 1000 points) that was ever pleasant to deal with in Fusion.  My experience is the opposite.

When you say: "without even a single spline its doing it", what, exactly, do you mean?  You mean Fusion is lagging outside of sketch/spline?  Have you tried rebooting the machine?  It sounds like you have some other problem than just spline performance.

[Ketherton21]

here I have a crap ton.

just selecting the spline tool and moving the cursor it was hesitating and lagging even without a single spline drawn, but I just found an identical picture and it fixed the issue. ill try your suggestion for the future

[jeff_strater]

thanks.  This is actually a good example of the technique I was advocating above.  There are lots of splines in here, but the largest one I saw was around 20 fit points.  This should behave pretty OK.  Whereas, in the other design, you have a single fit point spline with 100 points.  Here I have 4 of the longer splines selected:

It also sounds like the image you were using was also causing some lag, glad to hear that you found that out and are able to continue.

[Ketherton21]

so when im tracing like that if I double click and end the spline, and then start another one from that end point? it should perform better?

[jeff_strater]

yes, that's it, exactly!

[ioannismat]

Hey! I had the same problem but I found the solution in my file.

It seems like the problem all this time was actually the layer I was making the spline with. When I made a new layer and then created a spline, it wasn't laggy at all, doesn't matter how many points it had,

[HaraldLSFZQ]

@jeff_strater Provided I remember correctly, the computational complexity for splines is O(m*m*n) with m the order of spline and n the number of nodes. So we have linear complexity - which should be handled fine by hardware. At least it should not show a critical effect by raising the nodes from 20 to 100. I'd recommend to revisit the implementation. For my used cases, this limitation makes Fusion360 at least extremely hard to use. Moreover, the slow down is not a local issue (when sketching), but hits in for every computation / re-evaluation of features using it.