Complicated sketches shouldn't make the program unbearably slow.

[tima123d]

Seriously. I have a sketch with 56 lines in it. Lots of cascading dimensions. Lots of perpendicular and co-linear relationships. That got pretty slow when you try to select them all. Then I mirrored it and it got REALLY slow. Then I mirrored it again. Almost unusable.
Then I realized that I needed to move it a little to line up with the grid, and it seems impossible...

My machine is beefy. Fifty lines is not very many. Fusion should be better at this.

[HughesTooling]

It's not clear you say 56 lines then mirrored twice, so is that a total of 224 after the mirrors? One thing you should know is the convention with solid modeler is to try and avoid mirroring and copies in sketches, extrude once the copy, mirror or pattern the faces\features. If you have 200+ curves all parametrically linked through 2 mirrors you'll find most parametric modelers will be slow to work with.

Mark

PS have you made a post in the support forum and uploaded the file so it can be looked at by someone from support.

[tima123d]

In this case, the sketch is the end point (fabrication by laser cut), so mirroring the non-existent bodies does not help me.
Mirroring should be pretty much free anyway, since it doesn't add any relations to calculate. 
Also, if I want to move the entire sketch, it shouldn't have to recalculate any relations since they do not change. But it somehow becomes impossible...
A "fully defined" sketch should be faster to recalculate and move because you know the relations between the points are pretty much fixed. You can mark off huge numbers of points as moving linearly with the selection, and only have to recalculate the points that aren't fully defined...
I haven't made a post in the support forum, but they know where to find me... 😉

[HughesTooling]

Mirroring is not free it creates a symmetry constraints for every curve endpoint, actually mirroring actually causes the biggest slowdown. 

[kb9ydn]

Indeed it is nearly always better to pattern/mirror 3D features instead of sketches.  Even if the part will eventually be machined from a sketch I would still always fully model the 3D part.

However, 56 fully constrained entities with 2 sets of mirrors is hardly a lot.  I've had sketches in Solidworks with tens of thousands of entities.  That was understandably slow, but was still workable.

C|

[tima123d]

What I am saying is, whatever way they are doing it, it is wrong for it to get so slow that you think the program has crashed under any circumstances. If it is getting that slow, then they are doing it wrong.
Perhaps creating a separate mirror relation for every line is not an efficient way to do this.
Perhaps the algorithm that determines which entities need to be updated to maintain relations is not correctly eliminating and grouping entities.
I don't know.
What I do know is that it is too slow.

Yes, there are work-arounds, but I shouldn't HAVE to work around.
Hell, I'm already working around the lack of sheet metal tools... they seem to be documented, but don't seem to actually exist.

[thealucardfromhell]

This is the same problem I have with F360.

It feels like F360 was designed entirely to just...

Design a simple bottle cap.

And CAM it for your milling machine.

As for the sheet metal tools, aren't those in Inventor? The team is currently trying to implement sheet metal in F360, no? https://www.youtube.com/watch?v=BEDtSreoXe4 Not here yet but it's on its way.

[Anonymous]

I have a pretty dang fast computer, pretty dang fast internet(which should not matter) and ...SO slow on basic 2d stuff!  A $35 Cad software works and this doesn't!! This is a joke guys! I love Fusion and wanted to use it for this project...and just can't. Other software may slow a little...but yours crashed. 

I have a 13" circle with a quantity of 715  holes that are .250dia evenly spaced out. I load it in as a .dxf supplied to me...and can't even highlight it to move it an inch or anything lol!!!

[djo_laffreux]

Definitely look into your code guys, it's obvious from a mile away that whatever code is responsible for this is a steaming pile of ****.

Don't make me come down there and fix it for you, please.