You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: