http://bugs.winehq.org/show_bug.cgi?id=27746
Summary: fbo vs backbuffer regression in wine 1.3.24 Product: Wine Version: 1.3.24 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: galtgendo@o2.pl CC: stefan@codeweavers.com
This is a follow up of bug 25717.
As noted there, commit cd96c59d9168fbda25536d328edb24c0bc0e5139 (wined3d: Track framebuffer changes.) caused a regression, in that certain elements aren't drawn if fbo is used, while they're still displayed correctly with backbuffer.
The game in question spits following warnings repeatedly, regardless of commit, that caused the regression: err:d3d:loadVertexData >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glBindBufferARB @ state.c / 4319 err:d3d:loadVertexData >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glBindBufferARB @ state.c / 4319 err:d3d_draw:drawStridedSlow >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glEnd and previous calls @ drawprim.c / 309
If it matters: linux-2.6.39, r200, libdrm-2.4.25, mesa-7.10.3, xf86-video-ati-6.14.2