SUBSCRIBE The SideFX mailing list is a great place to make contact with Houdini users. To subscribe, send us an email with no subject and the word subscribe in the body.
[Sidefx-houdini-list] Compiled .vex via SOHO?
Friday, 30 December 2011 Fri, 30 Dec '11
Hi Peter, Sorry that I read this mail :) This is indeed handled in the processShaderString code. However, the real magic for embedding happens in C++ code that SOHO calls. In theory, the "forcevop" option *should* get the code output. But this only works if you're referring to a VOP network (I think). Also, SOHO keeps track of whether code has been output, so you can't output the code two times. Happy new year. On Friday Dec 30 at 15:00, Peter Bowmar wrote:
Hi, I just sent this to Support but I bet (and really, hope) that they won't see it until Tuesday... So maybe someone else has hit this? I need to get the compiled .vex file from any SHOP via a script (Python). It seems to me that Soho should offer this, since at some point the .vex file is (optionally) embedded in the IFD. I tried tracing back through the Soho code but I can't follow it. It looks like maybe sohoglue.processShaderString() might be involved, but I tried it and it returned nothing (shader name in first list value, empty string in 2nd list value). I can't find docs for it so I'm not sure what it's supposed to be doing. Am I on the right track? Can anyone provide an example that, given a /shop/SHOPNAME returns the compiled .vex code? -- Cheers, Peter B --No, I am not on Facebook. _______________________________________________ Sidefx-houdini-list mailing list Sidefx-houdini-list at sidefx.com https://lists.sidefx.com:443/mailman/listinfo/sidefx-houdini-list-- Mark Elendt