Performance issues

[dstevenslv]

On macos 10.12.5, 2.7ghz i5, 8gb ram, network 18 down/12 up macbook pro 13".

Random erratic behavior, extended beach balls on simple tasks, sketch behavior can be unpredictable.  All of this before I imported a 790 body sldprt file (tried to import as an assembly but F360 kept telling me I was missing a file that was there...).  It's a full model of a Raspberry Pi.   Converted the bodies to components.  On moving that object it took just under two minutes (about 115 seconds) for the computer to even respond and move the object, then responded in a jerky manner before landing at the destination.  What I imported behaves as it should in the native program that created it.  Even under emulation on this Mac.

I hid the import and went to add four holes in a basic base extrusion (the part is a case for a Pi and Pi-Hat for an open source race car scale project).  When I apply the hole it's a good 20-25 secs of beachball as shown in the cast.

I've abandoned ship on this project in F360 for now, I need to get something on the printer in the morning, I'll finish this part off with the other tool.  I would like to get back to a point where I could distribute these parts as native F360 parts.  It just doesn't feel right distributing SLDPRT files on a small open hardware project.

If some issue is found, that's swell.  If not that's swell too as I've got a fallback but it would be nice to distribute this in a format that didn't cost an arm and a leg to use for the maker/hacker types.

I've tried to export the distributed design to post but it wouldn't let me (really guys?)  If it makes sense I can upload both the Pi in SLDPRT and an F360 native of the few sketches and features on the base plate.

[ahreum.ryu]

Hi @dstevenslv,

Thank you for reporting this issue. yeah.. I think it's an add behavior so I would like to look into your model

If you can't export the file, could you invite me to your project? my email address is ahreum.ryu@autodesk.com

and this is how to share your model.

I look forward to your reply

Many thanks,

Ahreum.

[dstevenslv]

Thanks.  Sharing the model with a link works for the community to see it but not as a solution for distribution. (you've got an invite into the project)  Thanks though for pointing that feature out.  As an aside to the performance issue the lack of ability to locally export a distributed project is a pretty big blind spot.  These projects are largely distributed with git based tools, Github, Bitbucket, etc as they are a combination of software/firmware, circuitry and fabricated assemblies.    For example this project has an RPi image with the source for the scale program (and the script that builds the image), mobile app code for Android and iOS, the scale pad assemblies and the enclosure.  Ultimately I need a better ability to work with tools outside the F360 sphere. 

Should the performance issues with the big model resolve I think I can get around the distributed design export issue by breaking the link of the imported part.  Failing that I think deleting anything that isn't part of the fabricated assembly and exporting that as an F360 file would be a better solution than distributing it as an SLDPRT or ASM.  

EDIT:  not mentioned in the first post...  cleared local cache, no difference.  Manually uninstalled and reinstalled, no difference.

Dave

[TrippyLighting]

You can create a public link with download ability directly from your design in the data panel. Downloading this design will create a .f3z file ( as opposed to a .f3d), which will contain any linked components/assemblies.

To do so select the design in the data panel, right-click on it and select "share public link".

[dstevenslv]

Thanks Peter.  Downloading the f3z will work well to put into github.  In fact it rendered the design, generated the file far faster than opening in F360.  The issues are still there with the Pi model loaded into F360 but at least this way with any other assemblies that have multiple parts it's an easy export.

Dave

[ahreum.ryu · Accepted solution]

Hi @dstevenslv,

Thank you for sharing your design.

It seems to have the issue that not only adds the hole but also moves the reference file. Sorry for the inconvenience caused. 

I reported this issue (FUS-33931) If I receive any response from them. I will get back to you. 

Many thanks,
Ahreum.

[dstevenslv]

Thanks. I appreciate it.