ksanderson opened this issue on Dec 28, 2009 · 22 posts
philebus posted Sat, 16 January 2010 at 11:44 AM
Quote - It's a funny thing concerning nurbs. The spline modeler is almost a nurb modeler and I don't know how much farther it would be to take it to full nurbs and have a full nurb modleing interface.
Amapi was a full nurb modeler but the interface drives me absolutely nuts so I haven't gone in deep with it.
I fussed with Hexagon for a few days but I haven't really tried it in earnest. It's hard for me to get excited about a vertex modeler when we have one in C that I already know. Hex is just Amapi reworked to be better. What I don't know is why they can't import the nurbs whickamagoosa into Hex. That would be quite awesome for me. We would then have a living NURBS modeler that is hooked into C with a better interface (please?).
Maybe DAZ will make getting a patch a whole lot more sensible for people with tiny brains like me (I hate having tiny brain syndrome).
Hexagon uses some of the same code as Amapi and was developed by the same team for organic and character based work. However, when Eovia sold their software, Amapi and Hexagon went to different buyers (e-fronteir and DAZ respectively) - if Hexagon could be given the sort of tools Amapi has for product design, then Amapi would be a less attractive purchase, so the purchase of Hexagon was conditional on it not getting those facilities. So with regards to those kinds of tools, DAZ has their hands tied, ironically without need thanks to the death of Amapi.
There does seem to be some resentment of Poser users influencing Carrara's development - which really began under eovia with the introduction of native Poser import in C5. However, if Carrara is to be developed then it needs money and that requires a sufficiently large user base and, as I image eovia recognised, the Poser user base could be tapped for that money. Without Poser content, I'm not sure what place and future Carrara would have in today's market: who would own it and keep it either at this price point or keep it at all? Also, beyond the actual content import, just about any new feature added that will be of interest to Poser users will be of use to other users also - while some of you might not be interested in dynamic cloth, I expect users will be. (and do we really think that serious character creators and animators in Max or Maya wouldn't mind going without it?) The big question is, will DAZ go the same way with dynamic cloth as they did with Studio? - in which case, I agree, it would be of very, very little use - even to Poser users. However, if they allow users to create and set up their own cloth, then it's a good thing for all.