Anyone have success doing this?
What problems are you seeing. Personally I use stp as it’s quicker, with 3dm you have to upload through the data panel, with stp you can use New Design From File on the file menu.
If you want to import more than just surfaces use DWG, DWG will import surfaces, meshes and curves.
I want to retain all the layers and part names from the Rhino file. Don’t think that is possible with STP, right?
Fusion and other solid modelers I’ve used use blocks to create components not layers. I have a script that converts each layer to a block with the same name but not sure how safe it would be to use if you already have blocks in your design. The script should undo all it’s changes after the export but not sure I’d trust it 100%.
I can open a 3dm in AutoDesk Viewer and the layers and original part names are displayed there like this.
I could have a go with your script if you would be so kind as to share but will start small and simple and let you know how it works.
Fusion doesn’t have layers at all so they are going to be ignored, the viewer might show them and they might transfer to AutoCad but not to Fusion.
Here’s the script, it exports visible layers to either STP or DWG.
MarkExportAsBlocks.py (2.2 KB)
As long as I get the original part names I'll be happy.
Do your part names and layer names match? If not I guess the script could be modified to get the name from the objects instead of the layers then make a block from each object.
If you use blocks in your designs just check they are all there after running the script, not sure I allowed for a block and layer with the same name.
So back to the original topic of this thread. Has anyone been able to upload a .3dm file to the Fusion360 cloud and then open a new Fusion file from the 3dm? I have searched the Fusion/AutoDesk forums and help files and it seems to be a common problem for users. I have tried very simple models in Rhino V5 and V6 and it appears that the upload is successful but the little roundabout timer keeps spinning and the file in the Cloud browser will not open.
Done a quick test, v5 files upload fine but v6 fail. Files that fail should generate an error report.
V5 has worked in all previous attempts. V6 failed in single attempt tried, similar to @Hughes_Tooling. It appears no one has yet reported this in the Fusion forum.
Try exporting a v5 or use STEP, which you may open directly without upload.
I can get a V5 Rhino 3dm to upload to the Fusion cloud and open in the Fusion360 app. No luck with V6. Still no part names just Body xyz which is pretty screwy for my work. So much for the nice parts list function in Fusion.
Guess I'll try the script Mark shared next...
Mark’s script is a step in the right direction!
Still no object names but the conversion of layers to blocks looks like they show up as components in Fusion.
@Joseph_Culbert I’ve worked with files from several solidmoders over the years and they all seem to export assemblies as blocks and nested blocks. I think the only way you could go the other way would be to convert each named body\object in Rhino into a block then select all blocks on a layer and create a block with that layer name containing all the blocks.
What you’d get in Fusion would be a component using the layer name then sub components with the same name as your objects. I’m pretty sure BOMs in Fusion only work with component names not body names anyway.
I’m starting to get a handle on this Rhino/Fusion thing (with your help). I’ve seen your contributions on the Fusion forums as well, thanks!
So, I got around to reporting on the F360 forum Fusion’s inability to import Rhino 6 .3dm, whereas v5 .3dm worked. Seemingly no one else has reported such I could find.
If anyone cares, please consider a comment - squeaky wheel…
…and while you are at it, consider adding your voice to .3dm EXPORT if .3dm round-trips intrigue. Still listed as “Future Consideration” 5 years later. Hey, better that “archived”… aka - circular file.
Yeah, I can do ‘round trip’ using STEP as suggested earlier but also don’t really see any big advantage in using v5 (or v6 if that ever happens) unless object names in a Rhino file can’t be maintained. I’m still trying to get a workflow going but am not going to hold my breath. I’ll chime in on the 360 forum as you suggest ec.