site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Framebuffer 0 is not the original target framebuffer in a plugin. On Jun 24, 2008, at 2:28 PM, David Patrick Farmer wrote: Howdy! www.davidpatrickfarmer.com/GetTexture.zip Thanks! David Farmer coreaudiovisual _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/catchall%40davidpatrickf... _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... I am trying to use FBOs with GetTexture method and have found ugliness. It may very well be an incorrect use but I need to understand how to make it all work in FxPlug! Example Project Synopsis: Retrieve arbitrary frame from source layer. Render source layer to view, call glBindFramebufferEXT( GL_FRAMEBUFFER_EXT, 0 ) and clear view with arbitrary color. Why? Because the other noid has real FBOs. 9-) This was as clear cut as me thinks me could make the problem. If the bind framebuffer call is commented out, it all works. Why? Is it changing the context state somehow? Is it a masking issue of some sort? Update.: it does not need to use the GetTexture method to die. I came about this assumption through lack of thought. Still, why would binding the window frame buffer cause further render calls to be evaluated incorrectly or dismissed? This email sent to catchall@davidpatrickfarmer.com This email sent to site_archiver@lists.apple.com