What about Bifost in Maya 2015? Any news about that? —
Sent from Mailbox for iPhone

On Fri, Feb 28, 2014 at 4:21 PM, Paul Doyle <[email protected]> wrote:

> Hey Gustavo - comments below
>>>I tried Fabric once but learning curve was a bit steeper then I predicted
> (coming from an ICE user / no ofense intended). V 2.0 looks like it has
> greater benefits, so even if the >>price is steeper then a visual, higher
> level thing like Houdini it might pay off...
> Yes, this is feedback that we took on board from a few people - our target
> was for a TA/TD to be able to quickly build something powerful, but the
> graph approach we took for the standalone was tough for people to get their
> heads around. Visual programming is part of the 2.0 model - obviously the
> library of nodes isn't going to be there from day one, but being able to
> write your own nodes in KL (rather than C++) should help with that. We're
> still iterating on a few things so apologies for the vagueness - this stuff
> will tighten up over the next few months.
>>> Do you have a timeframe for F2.0? Since the [2.0] video points at some
> significant changes I would rather wait before diving in that pool again.
> It will be early summer - we were pushing for a Spring release but various
> requirements coming out of customers made it clear that we needed to
> revisit some areas.
> That said - using Fabric within Softimage/Maya/Arnold is there now. It's
> much more accessible to people than the standalone path - we're also
> pushing on a few things over the next two releases (March and April) that
> will make Fabric quite exciting within the plug-in context.
>>> Another question is one that regards functionality. Houdini has a lot of
> functionallity built in that could be exposed through its "Engine". I know
> you guys are a small company and >> you cant aim at covering great areas
> for now. We all have seen many great FE videos exploring topics like
> rendering, motion capture, procedural animation, crowds and so
>>> on... And we all agree the plataform is great, flexible and fast. But my
> question is: what can one TD or a small TD group expect from FE RIGHT NOW?!
> I know MPC and Hybride >> can do great stuff with it, but where would I be
> able to apply my FE knowladge on a day to day basis, and what should I
> leave to the houdinis and mayas for now?
> I would rather guys like Eric and Guillaume (and Mathieu if he has the
> time!) commented here - you're going to get a clearer production
> perspective imo.
> That said, it's important to understand that Fabric is a long way from
> being a replacement DCC. Our focus is on the platform, making sure we offer
> kickass performance and flexibility before we shift to higher-level
> functionality. I'd say jump in now (it's free after all for individuals,
> and we do deals for educational institutions), watch for the next two
> releases and keep an eye on the progress on 2.0.
>>>I have great respect for what you guys are doing, the way you do business
> and the way you do software keeps me confident an investment in FE would be
> a solid one. But I want >> to know where I am going in order to applie the
> right time investment in each tool from now on.
> Thanks for the kind words. I understand the need to get a sense of our
> roadmap - I hope this helps a bit. We tend to share a lot more on our
> mailing list.
>>> Ps: if you ever sell to AD please... well dont ever sell to AD ;)
> Whenever this gets mentioned, my response is the same - we're building a
> business, we've just closed a long-term deal with MPC, our intent is not to
> sell the company - it's to build something awesome. However, it's a two-way
> street - it can be frustrating and demoralizing for young companies to see
> a steady flow of "this is great, when it does X I'll take a look". If you
> want to influence the direction of a company then you have to be involved -
> it doesn't even mean giving us money, but install it, give feedback and so
> forth. Even if it's not Fabric - do the same for Modo, or C4D, or Blender.
> We have people on the list who haven't been able to get Fabric into the
> studio yet, but they tinker in their own time and tell us how to help them
> succeed. I can't overemphasize how valuable this is to us, or Exocrotex or
> anyone else.
> On 28 February 2014 10:38, Gustavo Eggert Boehs <[email protected]> wrote:
>> Hey Paul, I see you active on this "migration" threads, which is quite
>> nice by the way, and I have some questions.
>>
>> I tried Fabric once but learning curve was a bit steeper then I predicted
>> (coming from an ICE user / no ofense intended). V 2.0 looks like it has
>> greater benefits, so even if the price is steeper then a visual, higher
>> level thing like Houdini it might pay off...
>> Do you have a timeframe for F2.0? Since the [2.0] video points at some
>> significant changes I would rather wait before diving in that pool again.
>>
>> Another question is one that regards functionality. Houdini has a lot of
>> functionallity built in that could be exposed through its "Engine". I know
>> you guys are a small company and you cant aim at covering great areas for
>> now. We all have seen many great FE videos exploring topics like rendering,
>> motion capture, procedural animation, crowds and so on... And we all agree
>> the plataform is great, flexible and fast. But my question is: what can one
>> TD or a small TD group expect from FE RIGHT NOW?! I know MPC and Hybride
>> can do great stuff with it, but where would I be able to apply my FE
>> knowladge on a day to day basis, and what should I leave to the houdinis
>> and mayas for now?
>>
>> I have great respect for what you guys are doing, the way you do business
>> and the way you do software keeps me confident an investment in FE would be
>> a solid one. But I want to know where I am going in order to applie the
>> right time investment in each tool from now on.
>>
>> Best regards,
>> Gustavo E Boehs
>> Dpto. de Expressão Gráfica | Universidade Federal de Santa Catarina |
>> http://www.gustavoeb.com.br/
>>
>> Ps: if you ever sell to AD please... well dont ever sell to AD ;)
>>

Reply via email to