I know that Fabric engine is growing up fast and honestly I'm really happy
to know that visual programming is on the way, so at least I will be able
to try out the basic and understand whats going on, then, over time maybe
the library of the KL "nodes" will expand, so it'll be accessible to a
wider audience that is in my same situation

Based on the videos lots of cool stuff have been added, and it looks like
they're not super-complicated to setup ( if you know what you're doing :-D
) so thats a plus, then there is the Realtime Renderer that looks very very
promising, looking forward to see what else could be done


2014-03-06 13:35 GMT+01:00 Paul Doyle <[email protected]>:

> My comment regarding Python familiarity was trying to say that if you can
> write code in a dynamic language like python or javascript, then KL will be
> accessible to you. With FE2.0 we will have visual programming capabilities,
> but the library of KL nodes will have to build up in much the same way that
> ICE built up over time.
>
> It's important to note that we aren't making ICE2.0 - although our team
> had a lot to do with ICE, that doesn't mean we think it's the perfect
> solution. There are many differences between architectures that mean visual
> programming systems are rarely similar beyond 'boxes and lines'. It's
> important that expectations are around 'visual programming for Fabric'
> rather than "Fabric is making a new ICE'.
>
>
> On 6 March 2014 07:25, Cristobal Infante <[email protected]> wrote:
>
>> Houdini seems to be the closest thing:
>>
>> http://frenchdog.wordpress.com/2009/09/12/ice-vs-vop/
>>
>>
>> On 6 March 2014 12:12, Chris Marshall <[email protected]> wrote:
>>
>>> Is there anything out there at all like ICE? I'm not a coder, but
>>> understand the concepts as I used to code a long time ago, which is what
>>> made ICE a great tool for someone like me.
>>>
>>>
>>> On 6 March 2014 11:29, Eric Thivierge <[email protected]> wrote:
>>>
>>>> ICE compounds get ported by converting them to scripts / nodes in the
>>>> other applications. Those who have built them should have the chops to get
>>>> it done since at its core, it is just math and logic.
>>>>
>>>> I'm 100% behind Raf here. Unless you're working at a studio where you
>>>> need to continue to dev Softimage plugins in order to get current or up
>>>> coming jobs out the door it doesn't make sense to continue to build plugins
>>>> for Softimage only. Even in its prime, the 3rd party tools market for
>>>> Softimage is minimal.
>>>>
>>>> If you can dev for multiple platforms at the same time that's going to
>>>> be helpful as well. Mootz and his early test with Fabric is, in my opinion,
>>>> the correct direction. Support your plugins for Softimage but diversify to
>>>> others are the same time.
>>>>
>>>> For those who are replying and don't know how to script, I don't
>>>> believe Raf's comments were for you. Its for those who are developers and
>>>> TD's. It's a valid point that for these people to make a living, they need
>>>> to transition faster than most. We already saw another thread where someone
>>>> lost a dev job because they announced the end of Softimage. This is just
>>>> the beginning.
>>>>
>>>> Fabric is one of the only options I see as a viable platform to
>>>> continue with. Splice works in Softimage and Maya currently with Houdini
>>>> and I believe Max coming within the year. This hybrid approach allows you
>>>> to keep your work relevant while having a comfortable transition using
>>>> Softimage during that time until you're fully comfortable in say Maya.
>>>>
>>>> I know it's not artistic friendly yet, but the only way to ensure that
>>>> is to get more developers on board to push it there asap.
>>>>
>>>> Raf, myself, and many others have been hard core fans of Softimage for
>>>> years. It's not like we're are giving up on a solution that is in its
>>>> prime. It's on its last leg with a drop dead date of April 2016.
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Chris Marshall
>>> Mint Motion Limited
>>> 029 20 37 27 57
>>> 07730 533 115
>>> www.mintmotion.co.uk
>>>
>>>
>>
>

Reply via email to