MENOZ Posted October 12, 2009 Share Posted October 12, 2009 hello! I'd like to know how to input a sop node (like particles) into the file parameter in the pcopen VOP node, instead of write to disk a .pc file. thanks! Quote Link to comment Share on other sites More sharing options...
SpencerL Posted October 12, 2009 Share Posted October 12, 2009 hello! I'd like to know how to input a sop node (like particles) into the file parameter in the pcopen VOP node, instead of write to disk a .pc file. thanks! Use the op: to feed things into a file pararameter. op:/obj/myGeoObj/myParticles It does need to be a full path, you cannot use relative paths. if you need to use a relative path you could do something like op:`opfullpath("../myNode")` Quote Link to comment Share on other sites More sharing options...
MENOZ Posted October 12, 2009 Author Share Posted October 12, 2009 Use the op: to feed things into a file pararameter. op:/obj/myGeoObj/myParticles It does need to be a full path, you cannot use relative paths. if you need to use a relative path you could do something like op:`opfullpath("../myNode")` thank you!! Quote Link to comment Share on other sites More sharing options...
mathieu Posted October 12, 2009 Share Posted October 12, 2009 (edited) I have a similar issue, I need to feed a very simple custom sop node with incoming points, but I get some VEX errors... If somebody could have a look on the hip Mathieu Edited October 12, 2009 by mathieu Quote Link to comment Share on other sites More sharing options...
mathieu Posted October 12, 2009 Share Posted October 12, 2009 ... test_render_00.hip Quote Link to comment Share on other sites More sharing options...
DanBode Posted October 13, 2009 Share Posted October 13, 2009 Hey Mathieu, The issue you're facing is caused by the file parameter vop. The expression you have in there for the initial value is not being expanded before being thrown into the vex code. The same expression in the "point cloud texture parameter" of the pcopen vop does seem to be expanding properly. Maybe a bug? Anyway if you delete the expression from the file parameter vop's "file default" everything should work fine. Dan Quote Link to comment Share on other sites More sharing options...
SpencerL Posted October 13, 2009 Share Posted October 13, 2009 (edited) Hey Mathieu, The issue you're facing is caused by the file parameter vop. The expression you have in there for the initial value is not being expanded before being thrown into the vex code. The same expression in the "point cloud texture parameter" of the pcopen vop does seem to be expanding properly. Maybe a bug? Anyway if you delete the expression from the file parameter vop's "file default" everything should work fine. Dan I havent taken a look at the file, but one thing to note is that the "op:" syntax does NOT work when using point clouds in shaders. You have to write out your pts as a .pc/.bgeo file. .pc are more efficient so best to write out those over .bgeo's. Edited October 13, 2009 by SpencerL Quote Link to comment Share on other sites More sharing options...
brianburke Posted October 13, 2009 Share Posted October 13, 2009 (edited) It does need to be a full path, you cannot use relative paths. if you need to use a relative path you could do something like op:`opfullpath("../myNode")` Hey cool, didn't know about opfullpath. Thanks Spencer! Edited October 13, 2009 by brianburke Quote Link to comment Share on other sites More sharing options...
mathieu Posted October 13, 2009 Share Posted October 13, 2009 (edited) As Dan mentionned I deleted the op: expression in the file parameter of my SOP, and it works fine ! Thanks Edited October 13, 2009 by mathieu 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.