yongbin Posted November 18, 2013 Share Posted November 18, 2013 In attrib wrangle, you can run through points, prims, or you can run only once(detail). It seems way more powerful. What is advantage of point wrangle over attrib wrangle? I think point wrangle(or vopsop) was more convenient. But doesn't feel any more. After @OpInput raised, we don't use op:`opinputpath() frequently. Or, is there a function(or node) only can run in point wrangle sop? Or, speed?... Quote Link to comment Share on other sites More sharing options...
yongbin Posted November 18, 2013 Author Share Posted November 18, 2013 The title stripped away... It was, Is there any good reason to use "point wrangle" instead of "attrib wrangle" Quote Link to comment Share on other sites More sharing options...
magneto Posted November 18, 2013 Share Posted November 18, 2013 There are some functions missing in AttribWrangle which uses a different context than PointWrangle/VOPSOP. That's why it can't completely replace them until CVEX catches up. Quote Link to comment Share on other sites More sharing options...
yongbin Posted November 20, 2013 Author Share Posted November 20, 2013 Sorry about late reply. Thank you magneto. I decided only use attribwrangle sop, and watch it's limitation. If I get some, I will post here. Quote Link to comment Share on other sites More sharing options...
magneto Posted November 20, 2013 Share Posted November 20, 2013 That's the best way, to start with an AttribWrangle and only change to PointWrangle if you know AttribWrangle can't do what you need in advance or through experiment. AttribWrangle also has automatic group conversion from any type to any other type. 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.