Hi
I’ve been looking at using the import Solidworks blocks as linked blocks option as this would be useful to be able to reference material across from Solidworks to my Rhino model keeping the parts up to date. I’ve hit a few snags (see attached PDF with some screen grabs):
- On import it does a nice job of rebuilding the assemblies as layers, but if I move those layers to under a parent layer and save the file, then next time I open it, the Solidworks assembly is re created as a layer/sublayer under the top level again, rather than re loading under the parent layer I’d moved it to. Is there a way of getting Rhino to re load the blocks under that parent assembly?
- Importing parts mirrored as configurations internally in Solidworks. See attached PDF for some screen grabs. Block imported parts don’t mirror correctly (importing them as dumb solids seems to work OK) with incorrect handing and offset. I suspect that this is more to do with Solidworks woeful handling of mirroring than Rhino as I’ve got similar issues with importing flat patterns in Sigmanest and a longstanding bug with Solidworks on how it handles sketches on sheet metal parts imported from Rhino and then mirrored (the sketch gets mirrored and rotated 180deg, which is a pain when you’re using it for marking frame locations and other information for plasma etching…)
- Deleting blocks in the block manager (see attached). I can’t mass delete a set of assemblies from the block manager, as it throws up an error about blocks being nested, deletes one of the assemblies, then either stops or crashes. It would be handy to be able to sort by the “number of” column so you could delete all the blocks that are in use first, then delete all of the nested blocks in a second pass.
I can email over a couple of typical assemblies for testing if it would help.
Being able to load all of the structure for a vessel in Rhino and quickly do sections, clipped views, centres of gravity, weights and explanation notes for the folks in the yard is a big time saver over having to wait for Solidworks to load, rebuild and then think about whether it is going to calculate accurate weights for assemblies. I think the WIP is a big step forward over 7 for this, especially if these niggles can be sorted, so thanks for all the hard work. My balance of work done in Rhino to that in Solidworks has significantly moved to Rhino in the past couple of years, as Dassault see to have given up on Solidworks users that do more than assemblies with a couple of hundred parts (presumably trying to drive us to CATIA?).
Rhino v8 issues 14-9-23.pdf (470.0 KB)