Dismal Fusion360 performance opening/visualizing

[jamie.q.white]

After a short and very pleasant break, I'm back to the usual agonizingly slow performance.  Here's a screencast of loading a design and visualizing linked components. 

 http://autode.sk/1VQfYLF

Here's a typical file,  downloadable:

http://a360.co/1NDVnSI

Thanks,

-jamie

[Phil.E]

In this post you said your performance improved:

http://forums.autodesk.com/t5/design-validate-document/fusion360-is-still-really-slow/td-p/6237968/p...

Did you review any of the steps from this post to see if perhaps you need to do them again?

Can you run speedtest.net and let us know what kind of down/up speed you are getting? I ask this because your bike file is 199 MB which is the largest Fusion file I've ever seen.

Looking at your design, I think the problem is hardware capacity. There are a few features of your model that will definitely degrade performance. There are an exceptionally large number of objects in this model. Open the text commands (under the view menu) and type "component.count" as a .txt command.

This is the result:

With Overrides: LeafOccurrences 578: Bodies 3392: VisibleLeafOccurrences 24: VisibleBodies 67: LeafOccurrencesWithVisualMaterialOverrides 252: OccurrencesWithTransformOverides 260

LeafOccurrences = components

So there are 578 components with a total of 3392 bodies.

When opened there are 24 components and 67 bodies visible. I'm assuming the visible stuff is what you really care about for the design.

Looking at the individual parts to determine where the bodies are buried, I find that:

• Deco (the lettering) has 158 bodies, including a partial copy of the frame.
• Seat mount has 481 bodies.
• 003_BB_PF24 has 262 bodies, but only 3 are visible.
• 003_ST-dropouts-bridge has 500 bodies, but only 7 are visible.
• 003_HT has 311 bodies, but only 1 is visible.
• 003_BB_PF30 has 113 bodies, but only 1 is visible.

003_Jamie_Race (which is a collection of some of the above) has:

With Overrides: LeafOccurrences 314: Bodies 1769: VisibleLeafOccurrences 25: VisibleBodies 67: LeafOccurrencesWithVisualMaterialOverrides 125: OccurrencesWithTransformOverides 131

So the top level assembly has 003_Jamie_Race and an additional appx. 1600 bodies.

There is just a lot going on here and it would slow down any normal computer to run Fusion while there is all this on the screen.

Have you considered:

Opening each of the child components and deleting a few hundred bodies you don't think are useful any more?

Not using 3D text and logos, instead trying decals for logos? The fleur de lis and Metier lettering adds hundreds of bodies/faces/edges. Do these objects serve a critical purpose in the design?

Thanks,

[jamie.q.white]

Hi Phil,

Thanks for having a look.  I tried some of the graphics troubleshooting from the previous post but didn't see much improvement, if any.  I have not tried clean re-installing El Cap.  It is a lot of work.

Speedtest says 37Mbps download and 4.77 up: http://www.speedtest.net/my-result/5278422188

That is as fast as it gets out here in the sticks.

I tend not to delete objects because I go in different directions and often need to come back to something I originally thought I didn't need. My though process isn't very linear.

That file size is pretty typical, but I'll try deleting items I am certain I won't need.  Part of the reason I make copies of objects as I go is that Fusion360 tends to crash; if I am working on an object at least I can go back to the previous copy after a crash.

The text and logos are 3D-printed; they have to exist as objects. Same for threads; they have to be modeled so they print. I usually add them last so I am not making copies, and keep the base bodies in a separate component. 

Did you experience the same delays when you opened the file?

Thanks,

-jamie

[Phil.E]

I wouldn't recommend re-installing OSX again. Just keep an eye on your RAM and CPU usage. Restart Fusion if it starts to keep too much RAM.

Yes, I'm having a bit of difficulty working with it.

Right now I'm trying to remove all seemingly unneeded bodies to see if I can get performance back to normal. Just to try and get a baseline for this model's performance in "stripped down" mode. It's probably more than you want to delete, but it should give us an idea where things are slowing down. I'll have more to report later today or tomorrow.

Thanks,

[jamie.q.white]

Thanks for investigating.  It would be useful to know what I am doing / which components are slowing things down.  Glad to hear it is not slow only for me. 

-jamie