Closed gadfly16 closed 11 years ago
That's a current Houdini VOPSOP "feature", might worth a try to report to SideFX first.
It's seems to be simply fixable by connecting the incoming global N to the outgoing global N in the processing VOP SOP. Since you do the post calculations of normals in a separate OP I think this way the asset works as advertised.
The logic is the following. In VOP SOP-s if you don't connect an explicit output into the N output the operator will recompute point normals if they are present. So if you want to bypass you have to connect the incoming N to the outgoing one to leave it intact.
On Tue, Jul 16, 2013 at 1:50 PM, Imre Tuske notifications@github.comwrote:
That's a current Houdini VOPSOP "feature", might worth a try to report to SideFX first.
— Reply to this email directly or view it on GitHubhttps://github.com/qLab/qLib/issues/47#issuecomment-21036875 .
If you connect global/outgoing N in VOPs, it will always generate N, even if it wasn't there before. (Which is the same behaviour as in H11 -- I thought it worked better now). Anyway, I put an internal workaround in the asset -- "dev" branch as usual.
For example if the "Vector Attrib" param is "up" and both the pre- and post-compute normals are toggled off N will be (0,0,0) regardless its value before applying the operator.