NVIDIA GameWorks Integration

[anonymous_user_bcf66e2c]

@.;299971

I don’t know of any technical reason why couldn’t work, or why technically it shouldn’t be done, but as I recall, whenever I bring up the subject of a complete in-engine toolchain, some of our lead technical artists on the HairWorks project push back vigorously. Toochain and workflow are largely a matter of preference, but our artists believe that much of the work should be done in the DCC plugins together with a dedicated tool like the HairWorks viewer. Not being a production artist myself (or any kind of artist really), I like the idea of having a complete toolchain in-engine, at least one that would let you do, say, 90% of the operations that the full toolchain provides. makes it much easier to introduce the to new people, demonstrate it, roll out new versions, etc.

I tend to be on both sides of the fence really, I can see the benefits of a in-engine toolchain, but also can also see the side of the technical artists, same argument applies to in-engine modelling tools. I think would be a great project for the community to work on, while the HairWorks team can continue on making HairWorks for UE4, and continue to maintain the plugins and standalone viewer. The in-engine hair modeller could be released as an optional plugin that users could choose to install if they would like the features.