MartybNz
amm
Just to make clear, I really like Houdini for home, evening experiments, ICE uniformity become somehow boring through the years - but, that constant ‘diving’, plus compositing app node style (no any modern 3 app looks like this) are parameters that rounds my willing force to zero, to use H for anything with deadline - while ICE can go.
To clarify are there other reasons too to not use H for serious work? Just want to be sure that these issues are the major reasons.
Thanks!
Of course it is not only that, this is only a not so good metaphor. First reason is Indie license, which effectively disables around 4/5 of possible work. Second is not enough of confidence, which is nothing unexpected. Felt enough confident with Softimage after let's say two years. Now is only one year of H, while I'm learning Maya, too.
Third is, that these days, work of one man band, or small studio, already is described by something like Max - or more correctly, it is ‘formed’ by Max and similar apps (where I feel familiar, already) - so even Softimage and especially ICE, represent a huge overload of abstractions. A lot of comments about ICE, by ‘small people’, on SI forums, actually were negative. I think it was a small exodus in ‘back to Lightwave and Modo’ direction, when ICE was introduced. Perhaps some my ICE stuff holds the record
, of several pages in one day on old XSI Base, full of negative comments about been too technical. Now, when happened what happened, ICE is all good.
However that ‘compounding’ question, this is where I am, very personally, sensitive as an author of some ICE stuff, mainly used by small shops and individuals ( but not only them ). Where development was a sequence of simplifications, but at one point, finally got a few of artistic souls. able to promote it by their really attractive work. Or, people just figured out that there is no other choice
, who knows.
So, from that, always amazingly interesting point of view, of ‘encounter of cultures’ (programmer and artist, here) , I'd believe any as much clear message is important - against somehow typical bombarding with all possible options. Perhaps it's not that much about combining the VOP and SOP context - ICE tree from link, full of switchers, is mine, ‘my artist’ won't go with all that. But, abstraction of creating an attribute in advance, while overridden parameter, somewhere later n network
is not even greyed out - this is really unpleasant part.
Also, any as much simplified, streamlined default of saving and installing HDA's is welcome, while actual state is good enough, imho.
Anyway I hope I'll have some exact, finished ‘product’ to share (small hair system), the end of this year, so let's wait and see.
thank you for reading a long story