Hey Cuco! Sounds like your plugin may be calling _request for an area different than the incoming bbox.
Are you doing copy_info() (or manually setting you Iop's _info) in validate()? To help troubleshooting this, you could print out the values of x,y,r and t in your _request() function, just to see what _request() is being called for when you change the bbox of your inputs. Also, make sure you apply the bbox offset when you read / write data in engine. You should add +x to both your input and output pointers. ie. const float* B = row[Chan_Blue] *+ x*; float* outptr = row.writable(channel) *+ x*; Hope that helps. Un saludo! Ivan On Fri, May 20, 2011 at 11:08 AM, Cuco Bures <[email protected] > wrote: > First of all let's introduce myself, as I never wrote here... hi all, this > Cuco!! > > I'm writing my first nuke plugin. It's an Iop that looks in some channels > and makes a matte depending on them (I know... I should make it a Pixelop, > but I'm still learning!!). It compiles fine and it's working pretty well, > but the problem comes when the image has a bbox set: exr file with autocrop > info, or if you just crop any image right before the node and you check the > black outside option on it. When that happens, the image generated is > garbage. Also, to make it even weirder, if you set the crop x value to > anything other than 0, it works fine again. > > Probably I'm missing something obvious in my code, any suggestions on what > can it be? > > Thanks in advance, > Cuco Bures > Senior Nuke TD @ Primefocus > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
