I’m not asking that Rhino do anything with this geometry other than analysis. I’m trying to find out what needs to be done to repair this geometry. Every previous version of Rhino can do the job - Rhino 7 fails and that is a bug. All the bad geometry in this will be removed when I add draft to this model but I need to be able to first analyze the model to even get started on fixing this model. I’m not trying to fix all the horrible fillets in this model . I’m trying to figure out what needs to be done to create a new model. I will create my own fillets. What I need to know is which of the base surfaces need draft and which can be used as they are.
The point I am making is that one of the reasons that Rhino keeps regressing like this is because Rhino does not have adequate error checking. Without good error checking the development process is doomed to be forever groping the dark. Its a bug that Rhino 2 can identify the one bad surface that is causing Rhino7 to fall on its face.
That is a bug I have been complaining about for 16 years and amazingly McNeel sycophants are still trying to argue that Rhino falling on its face when it encounters degenerate geometry is expected behavior.
In the model I sent if the first thing you do is explode and seldup Rhino reports no duplicates. However if you extract parts of the model by window selecting and and then join the result and repeat that several times and then explode the entire model and run seldup you will find duplicates. In other words, Rhino7 adds the duplicated surfaces. That is another bug that I reported in my first post. How is the user going to fix a model with bad geometry if Rhino keeps adding more errors as one proceeds?