http://bugs.winehq.org/show_bug.cgi?id=13122
--- Comment #26 from Robert M. Muncrief rmuncrief@comcast.net 2008-05-22 19:52:27 --- (In reply to comment #24)
Commenting out GL_EXT_framebuffer_blit from the extension table in direct.c could show if it's a problem with fb_blit or not.
I guess the glCopyTexImage2D with offscreenrenderingmode != fbo causes the slow performance with multisampling.
I'm not familiar with Wine architecture, but I'd be happy to run the test if you give me a little more instruction. After commenting out GL_EXT_framebuffer_blit what should I expect to see/not see? What tests would you like to be run?
I'm also not familiar with glCopyTexImage2D, but if there's a problem with data transfer or manipulation and there's at least some semi-defined I/O and architectural documentation I could try fixing it. I have a few decades of experience as a digital hardware/firmware/software designer, but as I said I know nothing about the internals of Wine.