Like someone else said, I can spend days in an ICE tree before caching anything, it seems to me that the instantness of ICE would be lost in a round-trip to an external process. But I'm sure it has a lot of advantages. A big one for AD being that they don't have to venture too deep into the Maya code base to be able to integrate it.
On Wed, Mar 19, 2014 at 2:49 AM, Raffaele Fragapane < [email protected]> wrote: > In my book that it's an external module is good for a very extensive > number of reasons, and it has a good team behind it. > > The approach to the dev and release cycle though I find both questionable > and insufficient to place it anywhere significant on the map any some than > two to three years, and that leaves a massive gap for those coming from > soft and incapable or unwilling to adopt or develop competing solutions. > > Given autodesk propensity to rushed and whimsical decisions it also makes > me unwilling to roll the dice on it at all since it might be a great thing > that might still get canned if it doesn't instantaneously produce results, > results I question it can produce at all any time soon. > On 19 Mar 2014 04:48, "Arvid Björn" <[email protected]> wrote: > >> I was really surprised that Bifrost was some external process, and then >> even more surprised that they tried to tout this as a good thing. Here's >> the mental image I got during that demo: >> >> http://i.imgur.com/OUhV4wj.jpg >> >> >> On Tue, Mar 18, 2014 at 5:08 PM, Morten Bartholdy >> <[email protected]>wrote: >> >>> Its probably like this.. >>> >>> >>> >>
