I've initially also had my concerns about writing code in a new language but then the devs have been reassuring. The choice for the language allows you to write user-friendly code while having some modern programming optimizations being run out of the box without you having to code any differently most of the time. With 1.12 you can even run a single piece of code either on CPU or GPU.
Disclaimer: I'm currently not using Fabric as I've got other priorities but it's on my medium-term todo list. I'd rather wait for the planned 2.0 overhaul anyways. But as many—like Andrea Interguglielmi who came up with Coral—, I've been wishing for a such framework for some times. What they came up with so far is beyond anything one could have come up with. But that make sense—they've got the engineers behind ICE from Softimage, they've got ideas, they want to change things, and they're a talented bunch. On 06/07/2014, Marcus Ottosson <[email protected]> wrote: > Fabric Engine falls under the early adopter hype with me and as such I > really like it, but can't say much about it's prospects. My main concerns > being that it is commercial as opposed to open source, and that it relies > on an isolated, custom language as opposed to using an existing, already > established one. Hard to say whether there ever was an option, but it is > how it is. I would expect an open alternative to be in the works, that > potentially uses a more established processing language, like julia > <http://julialang.org/>. > > I echo Justin on interest in seeing what you can come up with Jeremy and'd > be happy to see a post of that sorts here! > > > On 5 July 2014 15:53, Christopher Crouzet <[email protected]> > wrote: > >> It's commercial but their licensing scheme permit anyone to try it out >> easily: http://fabricengine.com/get-fabric/ >> >> I've been following the project for a while and for the first time here's >> a team of devs that I believe in. As I said in another blog post (sorry >> for >> the plug, trying to genuinely share a point of view), I even see this as >> being the future: >> http://christophercrouzet.com/blog/post/2014/03/07/Softimage-Has-Been-Killed%2C-the-Future-of-CG-Softwares-Is-Now-in-TD-s-Hands >> >> In your case, if I wanted to build a portable rig or deformers with GPGPU >> performances in bonus, I'd go with Fabric. It might get more involved >> though as I'm not sure what tools are at disposition for rigging so far >> but >> it sounds like they've just implemented a paint weight tool that you can >> now use in Maya to replace the default crappy one, so it shouldn't be too >> bad. >> >> >> >> On 4 July 2014 21:40, Justin Israel <[email protected]> wrote: >> >>> If you do anything with Fabric Engine, maybe you could write up some >>> info on the experience. Never used it but was interested. It's >>> commercial >>> though, right? >>> I sat in a demo once where they were trying to pitch a sale of an aspect >>> of the framework. Looked interesting. >>> On 5/07/2014 1:35 PM, "Jeremy YeoKhoo" <[email protected]> wrote: >>> >>>> At the moment, I am trying to build a rigging tool, I am trying to >>>> write >>>> my code more or less independant from Maya's short coming (with maybe >>>> ambitiously trying to extend that tool to other software like Houdini) >>>> pyMel looked like it could provide that flexibility. I was actually >>>> hoping >>>> that pyMel, since now it is being shipped by Maya, the performance of >>>> it >>>> would now be a bit quicker. But from my research it looks like pyMel is >>>> still independent of Maya and could pose annoying problems with varying >>>> versions of Maya (since I freelance and different studios use different >>>> versions of Maya and etc...) >>>> >>>> It is good to know that you guys gave me that input before I developed >>>> more of my code too far down that path. Bit of a shame really in regards >>>> to >>>> PyMel. Now I am wondering more about Fabric Engine, I might look into >>>> that further, maybe that should be a topic for a later date. >>>> >>>> -Jeremy >>>> >>>> On Friday, 4 July 2014 12:06:52 UTC+10, Jeremy YeoKhoo wrote: >>>>> >>>>> Hey guys, >>>>> >>>>> I want to ask your personal opinion of pyMel. After reading the topic >>>>> on Monkey Patching the Maya API >>>>> <http://christophercrouzet.com/blog/post/2014/06/23/From-Monkey-Patching-the-Maya-Python-API-to-Gorilla-and-Bananas> >>>>> by Christopher Crouzet and an earlier discussion regarding this topic >>>>> in >>>>> this forum >>>>> <https://groups.google.com/forum/#!topic/python_inside_maya/cLdkFBAgRtI> >>>>> , I started thinking back to pyMel and wondered if it might be an >>>>> answer, I feel like kicking myself for disregarding PyMel previously. >>>>> I >>>>> have just realised how pythonic and how pyMel holds more of a object >>>>> oriented paradigm as opposed to MEL and maya.cmds (even described by >>>>> Autodesk >>>>> <http://download.autodesk.com/us/maya/2011help/PyMel/why_pymel.html>) >>>>> >>>>> So I have a few queries, Pymel is now being shipped with Maya, but not >>>>> supported by Autodesk which my have production implications. >>>>> >>>>> What do you guys think of Pymel? >>>>> >>>>> -Jeremy >>>>> >>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Python Programming for Autodesk Maya" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/python_inside_maya/51d18c7a-0653-4ace-9bf1-2cdc6eb7560a%40googlegroups.com >>>> <https://groups.google.com/d/msgid/python_inside_maya/51d18c7a-0653-4ace-9bf1-2cdc6eb7560a%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups >>> "Python Programming for Autodesk Maya" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2tqcmHNBNUz%2BvLWrW9YBcy_%3DGtTVvGRoEcQxrydVUaBQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA2tqcmHNBNUz%2BvLWrW9YBcy_%3DGtTVvGRoEcQxrydVUaBQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Christopher Crouzet >> *http://christophercrouzet.com* <http://christophercrouzet.com> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CANuKW52c26YwiS_hu-UvmWW-HrmnU-fjtO36b7%3DAz6mOCFkryA%40mail.gmail.com >> <https://groups.google.com/d/msgid/python_inside_maya/CANuKW52c26YwiS_hu-UvmWW-HrmnU-fjtO36b7%3DAz6mOCFkryA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > *Marcus Ottosson* > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOBieVuqy0AoHm%3Dt1mksrgTxC99Jzw-hpkwTMbnoKOsaJg%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- Christopher Crouzet *http://christophercrouzet.com* <http://christophercrouzet.com> -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CANuKW53fO04XfkohK%2B-WBg6AKs9RU1NcDZOKwistDyxamoEDsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
