Well.. I really hope that Fabric Engine will be our fixing solution. I think both SI and Maya way of handling solvers/gizmos ect are bit sloppy compaired to Fabric... n slow.. : )
On 7 January 2014 00:30, Ben Barker <[email protected]> wrote: > I found that the biggest problems in rigging are management issues: > listening and weighing input, absorbing unexpected changes gracefully, and > finding solutions that fit into a much larger pipeline over which you have > limited control. Rarely are you even in a position to dictate the software, > it's simply another variable to consider. Often there are overarching > political issues that you must absorb and translate into production. Like > all things, it always comes back to people. Really, moving vertices is the > easiest part of the job. > > > On Mon, Jan 6, 2014 at 5:20 PM, Steven Caron <[email protected]> wrote: > >> are you asking me personally? >> >> i think some studios might favor the dependency graph structure of maya >> for custom nodes and behaviors. they would choose that over the better >> initially organized softimage environment which lacks some customization >> options that maya has. a topic discussed to death already, maya's dominance >> is because of timing (of their release years ago) and it's extensibility. >> >> s >> >> >> On Mon, Jan 6, 2014 at 2:03 PM, Matt Lind <[email protected]>wrote: >> >>> So what does maya rigging tools have that Softimage doesn’t that makes a >>> significant difference at the end of the day? >>> >>> >>> >>> Matt >>> >>> >>> >> > -- -- Juhani Karlsson 3D Artist/TD Talvi Digital Oy Pursimiehenkatu 29-31 b 2krs. 00150 Helsinki +358 443443088 [email protected] www.vimeo.com/talvi
