http://bugs.winehq.org/show_bug.cgi?id=5547
------- Additional Comments From stefandoesinger@gmx.at 2006-20-08 15:20 ------- err:d3d_surface:IWineD3DSurfaceImpl_SetMem Not supported on render targets
Urgh, that sounds really, really nasty. It appears that the application creates a render target and wants to set the pointer where to find the surface data. Technically render targets should be in video memory, so there's no way for apps to set a surface pointer.
The problem for wine is that our 2D render targets need a dib section, and when the dib section is created gdi decides where to put them. There used to be a hack for old ddraw in gdi32 to allow ddraw to set the memory for the dib section, but AJ really disliked that and was glad to remove the hack after the ddraw rewrite. I'm afraid there's no way to get that back. Maybe we can do some memcpying(slow) or the game calls that because of incorrect capatiblity flags.