If I export some Rhino blocks in stp format the mirrored ones are saved as not instances.
For example importing the stp file in Spaceclaim all mirrored blocks aren’t intances anymore, the not mirrored blocks are correctly imported as instances.
I tried also with SAP (Deep Exploration), same issue.
Regards
Hi Rhino developers.
This video shows the issue.
When exporting mirrored blocks your stp kernel converts the mirrored objects as not instanced.
I will need to take a look at the file. I am also seeing some odd behavior in the Mirrored blocks, but I cannot see a pattern yet. Generally they work.
If I can see the file then perhaps that will help understand what is missing from mirrored blocks.
OK, so this is a file with the mirror. I see in Rhino that is does read in with both sides. I guess we want to see if it reads into Space claim as both sides.
I can imagine spaceclaim not liking a mirrored block, but let’s test his file.
Also, normally following the concept of a part and assembly model, I would make a block of one screw. Then, Array that screw onto the grid. Then Mirror that array.
At this point all the screws one one side are one part, as the screws themselves are not within their own block.
screws_v8_extruded.stp (12.7 MB)
The rules here seem to still (V8) apply to Rhino’s STEP export, except blocks must also be at full scale; other uniform scales will also result in exploded instances.
I use STEP File Analyzer and Viewer to study STEP files.
Yes, the scaling issue is something that may be a barrier to some step instances, especially part and assembly style organizations. I believe it comes from the idea that part and assembly program instances are changed internally. In our case the transform scaling is done externally to the instance.
