Hi, importing SolidWorks models with medium complex sub-assemblies, the resulting layers in Rhino become nested in a deep way. Here’s an example of a layer tree that should be mostly flat, where root level assemblies become disorganized and deeply nested. It’s always worked this way in Rhino 6 as far as I know.
What I would like is the smallest example that exhibits the behavior you don’t like. ie. if you have a 10Mb setup and 100Mb setup that both exhibit the behavior, the 10Mb is preferable. It would also be handy to have a screen shot of the layer structure the way you think it ought to look like after the import is complete. I only need the SW file(s) that will let me see the existing behavior in action. I do not need the 3dm file that is the product of reading in those SW file(s). You can upload the file(s) here, https://www.rhino3d.com/upload, and mention my email so I get notified.
Hi Tim I uploaded an example. I have a suspicion the issue is multiple instances of the same part or assembly. In SW these get appended with an instance number Seat<1>, Seat<2> etc. It looks like Rhino tries to repeat existing layer names for multiple instances instead of using the instance increment. Attached is a picture of something like how the layer tree should look.
Hi Eric - I can see this is messy- you’d like it split up the way it shows in SW, correct? All the parts/sub assemblies to correspond to top level layers in Rhino?
Hi Eric - so, I guess, there must be a specific arrangement that makes it messy - some nesting order or something. Question is, what? I’m not handy enough at all with SW to really test in any meaningful way, I suspect, but I’ll see if I can see how it works.
Like I mentioned, I suspect it might have to do with multiple instances of the same part being in the assembly. You could suppress copies in SW and see if it makes a difference.