Now if McNeel REPAIRS SmartTrack so it really does what it should do better than POOR - and adds the CUSTOMIZATION OPTIONS to it / then Rhino has a horn! Moi3d furthermore let you pick colors, highlight sizes - it was a marvel - went back to Rhino and it was like going back to Jurassic Park by comparison! It was a new Rhino - slightly different - strong as hell in intuitive selection capabilities!Īs you move your cursor it tells you the angles and dotted lines appear - it was as if SmartTrack really was smart! Really smart, as in genius! They banned me for redesigning the layout and reverse engineering it so it was totally modded-out! I did away with the adolescent ice cream GUI and it was all grown up. If there was an Moi plugin for RHINO, that’d be a real “best of both worlds” kind of solution ! Best to all, - C. Rather than managing the incident faces, a fillet will almost CERTAINLY fail, and one suggested workaround is to make sure that the coincident fillet radiuses decrease in radius size, as you add additional fillets ! Still,as an integrated single modeler to use as a base of operations, RHINO is strong, and the ability to see through the component in front to select a feature of the one behind, makes it a stand-out. I also struggle with RHINO’s frustrating lack of attention to such basics as successful filleting. At this point, I actually create my models one face at a time, joining them, and spending my time checking and double checking for closed polysurfaces before moving on to the next step. Why they seem to have decided that selecting the far-most behind or earliest drawn entity rather than the foremost and latest is beyond me, but responses to my questions and input has been frustrating, to say the least ! Also, that I can’t get through a single model without devolving through the curve level, all the way down to manipulating individual points to get what should have been a simple operation to succeed, has been a source of multiple requests to tech support. Also, the Moi interface seems to focus on user effectiveness, in the areas you mentioned, with what I’d add as - a focus on entity selection, which has been one of my long standing frustrations with RHINO. Most of the “commands” in RHINO are there for helping the user discover what went wrong with the results of a routine used to accomplish a specific purpose, and fix the fail. Moi3D does INDEED have some workflow features designed to enhance productivity, without forcing the user to “learn” the internals so they can debug fails they encounter when modeling, as in RHINO.