hey guys, I seem to have uncovered a strange issue when using attribVops operators. I recently started noticing a discrepancy on one of my assets on the results I was getting in Houdini VS maya. after much surgery, I noticed that an XYZdistance VOP inside of an attribVop was always returning -1 as the hit primitive no matter what.
I decided to put a few print VOPs to compare the data in between maya and houdini. In houdini, this is what the opInput2 of my Geometry VOP Global prints:
OpInput2: opobj/subnet_UVLayout/meshesToUV/layoutLightmapUVs_maya1/layoutLightmapUVs/subnet_scaleToWorld/foreach_calculateUVcoverageIn3D/attribwrangle6
However, in Maya, this prints the following:
OpInput2: opobj/layoutLightmapUVs_maya::1.0/layoutLightmapUVs_maya1/layoutLightmapUVs/subnet_scaleToWorld/foreach_calculateUVcoverageIn3D/attribwrangle6
note that the op path in maya has the version number in the op name preceded yb the ::, which I know this is an invalid behaviour in Houdini natively.
To confirm this, I renamed my digital asset to not use namespaces (i.e. EAS_layoutLightmapUVs_maya_1_0) and now it works fine
I presume this is related to the fix done in 13.0.540? could we address this one as well?
thank you!
Issue when using opinputs in VOPs
3625 4 3- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
- awong
- Member
- 818 posts
- Joined: Sept. 2013
- Offline
- damian
- Member
- 402 posts
- Joined: March 2013
- Offline
- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
-
- Quick Links