I’m actually starting to love Alias!
I’ve had only 4 classes in Alias so far (each lasting around 3 hours, including a 30-minute break), and we’ve already finished designing a very basic helicopter (just to get used to the surface creation and surface fillet tools) and are on our way to designing our first car.
We aren’t playing around with primitives; we’re doing full-on class-A surfacing, with special emphasis on creating surfaces with as few spans as possible.
And I have absolutely NO problem with the interface, or in using the marking menus; infact, I LOVE THEM!
Don’t get me wrong: Rhino will always be my first and true love.
It was the very first graphics/CAD app I had ever tried (even before PhotoShop/Illustrator); and I’m extremely proficient at it.
And there are SOOOOO many things that I can do Rhino that I can’t quite imagine doing in Alias (even if I were extremely proficient at it as well), or even anything else for that matter (except for maybe CATIA; but I’m still trying to learn it).
Heck, I still love doing all my line-work of my drawings in Rhino than in Illustrator; and I still use Rhino to do all my solid-modelling before exporting to SolidWorks.
And who in their right mind can forget about T-Splines?!
But Rhino is lacking in a lot of areas (e.g. marking menus, functional ‘Record History’ on the BlendCrv and the surface matching commands, etc.).
I even tried to get the developers to implement the new selection filters in V5 into a menu that can called up with the middle-mouse button, so it would approximate Alias’s marking menus; but they seem to heading the development of V5 in a very disjointed manner (two different tabbing systems that aren’t quite compatible with each other, etc. etc.)
Plus, I hate how it’s such a struggle at getting single-span transitional surfaces with continuity.
That’s my biggest beef with Rhino, really.
Every time I use the BlendSrf command I get a surface with a totally-bonkers layout of isoparms…something that almost never happens in Alias.