kgoossens Posted September 30, 2009 Share Posted September 30, 2009 Hi everybody, I've just build a very simple test scene where I'm reading data from SOP's ->COP's do some operations there and then read back information from COP's -> SOP's. If you try and move the timeslider you can see it is taking 10's of seconds to update. From the results I see when I interrupt the cooking. It seems that the whole COP operation is executed per point (making it this extremely slow), but I'm not sure. Is there something I misunderstood or did completely wrong? I'd really like to know. Cheers Kim Slow.hipnc Quote Link to comment Share on other sites More sharing options...
sam.h Posted September 30, 2009 Share Posted September 30, 2009 pic() is very slow, use Colour Map in a vopsop instead. Quote Link to comment Share on other sites More sharing options...
sam.h Posted September 30, 2009 Share Posted September 30, 2009 pic() is very slow, use Colour Map in a vopsop instead. annnnd heres the file. Fast.hipnc Quote Link to comment Share on other sites More sharing options...
kgoossens Posted September 30, 2009 Author Share Posted September 30, 2009 annnnd heres the file. Hi Sam, Thanks a lot! Now it happened to be that when I added a velocity blur COP node, it caused Houdini to crash. But tests with other nodes didn't deliver any problem. Quote Link to comment Share on other sites More sharing options...
goshone Posted May 26, 2010 Share Posted May 26, 2010 I was stoked to see this example because up to this point, I thought I had to write the images to disk in order to use the colorMap VEX node. That 'op:/img/comp1/' trick is a good one. 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.