On a brighter note, you won't need the NVidia Apex clothing plugins to
set up cloth in UE4 anymore, at least if I get their claims right for
version 4.18
Jordi
Thanks for the input, your 'point list' is very well thought out. I think
I'm covered (UE4 side for realtime and Houdini for composited works).
I'd give a point for serious Cross-Platform support (OSX, Linux). I think
I might even give more than 1 point to open standards support (in
Seems like open source is the best 3D software model to make something float
indefinitely regardless of market trends. Hope FE does that…. Unless they got
bought out or something.
-Draise
From: softimage-boun...@listproc.autodesk.com
Although I understand where you are coming from the minimising risk side, it is
also true that you end up investing a lot more in both, the software and glue
to communicate various software applications with a myriad of file formats and
what not, therefore I advocate for a hybrid approach in
Pretty much my though.
> On 28 Oct 2017, at 13:39, Mirko Jankovic wrote:
>
> How replacing 1 tool with 5 or more, and work that could be done by 1 man now
> requires 5 or more as well can be advantage?
> ᐧ
> --
> Softimage Mailing List.
> To unsubscribe, send a
Investing your time into mastering the totality of one major software is
risky.
The specific example that I want to test in the coming months doesn't seem
unreasonable for one person (and you could swap the parts out to suit your
tastes/budget/needs/prior experience) (but please critique the
I agree with everything you said..
And I'm also saddened to see fabric close-up it's doors,
especially in this already diversity deprived environment.
& all the best to the FE team!
On 10/27/17 17:59, Jonathan Moore wrote:
How replacing 1 tool with 5 or more, and work that could be done by 1 man
now requires 5 or more as well can be advantage?
ᐧ
--
Softimage Mailing List.
To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with
"unsubscribe" in the subject, and reply to confirm.
Jordi, what you just stated is exactly why I suggest that 'we' need to stop
looking at things as a Softimage replacement where you do the majority of
your work, from start to finish, inside of one application. We have to
pretend we are big studios, split everything into smaller parts, using a
It is clear to me that developing a new 3D application is extremely expensive
and the size of the market just does not justify the effort, which is the
reason it was so very disheartening when AD killed Softimage.. Building
anything similar to Softimage would cost a fortune to barely make a
That's too bad.
This is rough market. There's not much money in developing better
solutions. I guess we'll ride out our DCC's with ancient architecture, and
wait till one of us becomes a billionaire and funds something cutting edge.
I'd love to here more of the story of what happened from some
https://urldefense.proofpoint.com/v2/url?u=http-3A__fabricengine.com=DwIBaQ=76Q6Tcqc-t2x0ciWn7KFdCiqt6IQ7a_IF9uzNzd_2pA=GmX_32eCLYPFLJ529RohsPjjNVwo9P0jVMsrMw7PFsA=NGIA25JXPveaf5MIyjSYphp-EdBdUfzUWDPJRUxHmAc=7kg20PfKIhjC7adrNpSQ_8q1HKu7LJUyPif5TKQJYh8=
--
Softimage Mailing List.
To
12 matches
Mail list logo