http://bugs.winehq.org/show_bug.cgi?id=22971
--- Comment #8 from tipecaml@gmail.com 2010-06-01 14:32:56 --- (In reply to comment #6)
There are all sorts of problems and which I think are driver related.
Framebuffer object errors (very serious since common settings are being used): fixme:d3d:context_check_fbo_status FBO status GL_FRAMEBUFFER_UNSUPPORTED (0x8cdd) fixme:d3d:context_check_fbo_status Color attachment 0: (0x8742528) WINED3DFMT_B8G8R8A8_UNORM 1280x800 fixme:d3d:context_check_fbo_status Depth attachment: (0x8742d90) WINED3DFMT_D24_UNORM_S8_UINT 1280x800
Lack of s3tc support (you might be able to activate this using driconf): err:d3d_texture:basetexture_bind >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glBindTexture @ basetexture.c / 322 err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glCompressedTexSubImage2DARB @ surface.c / 760 err:d3d:IWineD3DDeviceImpl_UpdateSurface >>>>>>>>>>>>>>>>> GL_INVALID_ENUM (0x500) from glCompressedTexSubImage2DARB @ device.c / 5332
Indeed, activating the s3tc support using driconf made all the GL_INVALID_ENUM errors disappear.
If you can really upgrade your drivers since I expect those are causing the issues.
Ok, I'll try and get the latest Intel drivers and give you some feedback.