My object in Rhino is a joined, valid polysurface with 1 naked edge representing the border of the open polysurface. Why after exporting to IGES would it begin determining there are bad objects in the scene?
I also find, even though my default tolerance in Rhino is 0.01, that the IGES file I open is by default in a tolerance of 0.001, even after specifying 0.01 as the IGES tolerance. My workaround is opening a doc with 0.01 tolerance then importing instead. The IGES I open always breaks apart the polysurface, and then creates bad objects when I join it up again. (Due to the bad objects present and the tolerance I suppose).
I think some of my problems are originating from these types of surfaces.
Whilst working I would find such things hard to spot amongst a large file - is there anyway to detect something other than visually? I’ve been misled from ShowEdges and Check telling me that everything is okay. I found RebuildEdges trimmed the surface back to where it should be to expose the gap that exists.
The file is confidential, but there’s something missing in my steps and process that I want to learn from. I appreciate maybe it’s not as simple to say that a good polysurface in Rhino is necessarily a good IGES file, but if so then I need to be able to know where I may be getting false readings/feedback.