SVG handling SLOW!

[Anonymous]

Running a CNC router I get called upon to import & engrave clip art.

Grab a reasonable vector clip art from ShutterStock, import it into a sketch, and watch it drag Fusion 360 to its knees.

Even after I edited it in Illustrator to eliminate a bunch of paths, merging curves, etc it's still awful. We're talking minutes of calculation time just to *select* the curves in a sketch.

Machine is a Ryzen 1700X, 4Ghz, 16 Gb of 3200 Ghz RAM, M.2 SSD, R9 Fury which is a *monster*. In fact, I was editing the SVG in Illustrator with no slowdown at all while Fusion cranked away on one thread trying to "select all" .

There is something seriously wrong in the part of the code that handles sketches.

Oh, and the board won't let me upload a SVG to share...

[jeff_strater]

you can zip up the SVG and attach it to the forum as a zip file.  My guess is that it still has thousands of entities in it, and yes, that will never be easy to deal with in Fusion.  The Fusion sketch environment is meant to deal with sketches that are created natively in Fusion, and once you get above a couple hundred curves, the sketch environment gets pretty sluggish.  Sometimes it is easier to just retrace the curves in the Fusion environment sketch environment yourself.

[Anonymous]

"Never" is a hell of a long time...

It is interesting to see 360 use all 16 cores when working out CAM toolpaths, but playing with an SVG in a sketch - something that Illustrator could do 2 decades ago on 2000s hardware - only uses 1 core at maybe 30%. There is something seriously broken in sketch handling.

I'm going to try and make the same model in Solidworks and see how it does.

[Anonymous]

Bumping this thread because this problem shouldn't still exist. I'm importing a 24KB .svg file to try and emboss onto a model.

Fusion 360 developers will chime in and say some nonsense about constrained sketch environments and Fusion 360 can't possibly be expected to handle more than 300 curves in 2021. Surely there is a workaround. Surely you can fix this problem.

This problem has been documented since 2014 in these very forums! How are you not able to solve this or create a workaround? What are you even doing about the problem?