STEP import not correct after update last week

[wim (Wim Dekeyser)]

Hi Tom -

@VectorTom

I imported a STEP in the beginning of the week in Rhino 8 and everything was showing up like it has to be. This week there was an update of Rhino 8 and after installing the STEP file doesn’t import like it used to be, not everything shows up.

This change is the result of an attempt to fix an issue when a STEP file is imported several times and new block definitions are created for identical blocks that already exist.

You can read the discussion about this here:

Importing STEP files to Rhino creates a new block

I have Solidworks and Inventor assemblies which I export from these two applications as STEP files. When I import those STEP files to Rhino, they become nested blocks, which is fantastic. However, each time the very same STEP file is imported, Rhino automatically creates a new block definition, and a new block instance from it. And it does this not only for the top most (parent) block, but also for all the nested blocks inside it. This makes the opportunity of using mechanical software’s ass…

This is clearly something that will be worked on further, but in the meanwhile, you can use the TestStepBlockHandling command to turn the current behavior off. You will have to use the No option in that command.
-wim