So Nuke's Reader system wasn't intended to allow the same file type to output different data types (image & geometry for example) - so what basically happening is that the DD::Image::Read and DD::Image::ReadGeo parent classes can't differentiate between a Reader plugin intended for Iop or Geo use because they have the same name and when they're loaded are incompatible with the parent class, causing the error.
DD::Image::Reader and DD::Image::GeoReader plugins are not compatible, so the DD:Image::Read class can't load a GeoReader and vice-versa. I can't think of a way to get around this unless you name each reader differently but allow them both to access the same file extensions using the test method, then you're relying on the fallback behavior where Nuke polls all available readers to see if there's a reader that can handle a certain file type. Good luck... -jonathan On May 23, 2011, at 7:07 AM, Buddly wrote: > Humm one last question.. My problem came cause I was trying to open my file > through a normal Read node. When I do this I do have the same error (plugin > did not define....), but of course everything is fine if I open it with a > ReadGeo node. What do I have to add in my code to open my file with a normal > Read node and automatically convert it in ReadGeo, as it is the case for fbx > files for example ? > > > > Jeremy > _______________________________________________ > 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
