HoudiniEngineForUnity_deprecated icon indicating copy to clipboard operation
HoudiniEngineForUnity_deprecated copied to clipboard

Edit is Paint, Paint is ?

Open tlaedre opened this issue 8 years ago • 1 comments

An edit node in Houdini seems to become a paint node in Unity, whereas a paint node in Houdini seems to be just ignored in Unity. It also seem like these edit nodes are extremely eagerly picked up, even if I add an edit node set to bypass, and with no output routing, this nodes becomes a paint node that affects the nodes below in Unity.

Besides being a bit confusing (and afaics undocumented), this also makes is a bit cumbersome to build assets that can be used, tested and iterated with equal methods inside Houdini and Unity.

It'd be great to get some clarity on this, as well as a direct mapping to concrete paint nodes pointing out specific attributes.

tlaedre avatar Dec 05 '17 01:12 tlaedre

We'll make this clearer and look at restricting what becomes a paint node.

SeelanV avatar Dec 15 '17 20:12 SeelanV