yaz Posted April 30, 2016 Share Posted April 30, 2016 (edited) Hey guys, I've been writing VEX code for about a year as a hobby and I wanted to get the process more streamlined and modularized. I'm trying to create a 'New Operator Type' that can handle Structs and take in parameters (e.g., point wrangle's channel functions). I see there is Operator Style 'Vex Type' and Network Types: 'Surface Shader Operator', 'CVEX Operator', and 'Geometry Operator'. 'CVEX Operator' seemed to be the only one that worked in the Object network (with Attribute Vop). However, why does the CVEX digital asset need to be created in the SHOP network and not directly in the Object network? I thought SHader Operators were only limited to pixel surfaces (like a pixel shader is in real-time gfx)? Inside a attribute VOP, can I load a CVEX file rather than SHOP? (Script doesn't seem to do it) 'Surface Shader Operator' behave like pixel shader and materials correct? In what case is 'Geometry Operator' used over 'CVEX operator' ? Why doesn't point wrangles support Structs if inside it contains a attribute vop? Do pragma hint for value input work with CVEX? I don't see where the interface is accessible on the VOP attribute. I appreciate the help!! Edited April 30, 2016 by yaz 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.