broken surfacing from other modelers like SW
I have to chuckle there. My experience is 180-deg opposite. The broken models always started in Rhino, LOL. It had a habit of blowing its brains on the most harmless of operations. First 3 identical fillets work fine, unlucky number 4 causes a crash. The distressing aspect was very limited diagnostic tools. And I don't consider Ctrl-Z & try again a tool. The forums were chock full of mysterious 'please help me' issues. Sometimes it was a 'micro-gap' error on the 16th decimal place where you assumed a line or point was connected & it never told you otherwise. SW provides feedback every step of the way so you don't build layers of errors that eventually bite you. When a sketch or features says 'fully defined' it means exactly that. Because Rhino is not parametric you cant back up a step or modify a mid step. Sometimes it was like a stack overflow or just lost its way in the calculations. Sometimes it was like steps 1,2,3,4 crashed, but 1,2,3 (refresh/save) 4 worked doing the exact same thing. Some compliant solids would split on a plane, others just refused. Weird.
I found the Rhino forums & admins were fantastic for Q&A, documenting bugs, considering enhancement suggestions and even evaluating problems by sharing files. Small community feel. What I noticed was (assuming it wasn't a fundamental error ) the solution was more of a putty fix technique - patch the missing geometry or force entities slightly... so it calculated as a water tight solid & be on yer way. And don't let the distressed Zebra lines bother you too much LOL. Now SW forum help has gone to sh*t IMO. As one user put it, its like they hired a D-grade teenage Facebook programmer. Bling-blang, Cloud this, Collaborate that, product services I don't have or want. It USED to be type in a keyword & up comes 10 years of relevant, targeted content & 5 willing posters jumping in to help.
I've noticed a repeated misconception that Rhino is somehow the premier app for 3D organic shapes & smooth swerving surfaces vs. the rigid mechanical 3D CAD modelers like SW, Inventor, F360... are confined to clunky Lego block models. This is 100% BS & typically originates from people who either never used the apps or to their capability. I would venture to say there is nothing Rhino can do in a surface model that SW cannot do, probably in multiple different ways & with definable, traceable constraints which don't even have an equivalence in Rhino. Splines types & their control are much richer, more sophisticated capability. Control points, degrees of tangency... I could go on & on. One caveat is free-form tools like T-splines are certainly powerful, albeit niche. But this is available to other modelers AFAIK. Now one app cost 4X the other so we are not talking affordability or $-value here, just capabilities.
So could Rhino patch some bad geometry & fix a broken 3D model from another app? Sure. Well, maybe. As long as you know here to look & how to stich a surface. But the opposite is also true. The difference is, significantly more 'fixit' tools exist at your disposal & a targeted idea of where the problem is.