[Bug 9584] Mame will not start due to missing Direct3D functionality

http://bugs.winehq.org/show_bug.cgi?id=9584

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Louis Lenders   2007-09-05 10:43:20 ---
> The actual test for capabilities is done in the function device_verify_caps: >tempcaps & D3DPRESENT_INTERVAL_ONE.

Your analysis looks right, hack below makes the game start fine. Maybe we could
add this flag to the capabilities without problems, but i dunno really much
about d3d. Maybe Stefan could comment on this?

diff --git a/dlls/wined3d/directx.c b/dlls/wined3d/directx.c
index e199f36..ed53d8c 100644
--- a/dlls/wined3d/directx.c
+++ b/dlls/wined3d/directx.c
@@ -1810,7 +1810,7 @@ static HRESULT WINAPI IWineD3DImpl_GetDeviceCaps(IWineD3D
*iface, UINT Adapter,
                                       WINED3DCAPS2_FULLSCREENGAMMA |
                                       WINED3DCAPS2_DYNAMICTEXTURES;
     *pCaps->Caps3                   =
WINED3DCAPS3_ALPHA_FULLSCREEN_FLIP_OR_DISCARD;
-    *pCaps->PresentationIntervals   = WINED3DPRESENT_INTERVAL_IMMEDIATE;
+    *pCaps->PresentationIntervals   = WINED3DPRESENT_INTERVAL_IMMEDIATE |
WINED3DPRESENT_INTERVAL_ONE;

*pCaps->CursorCaps              = WINED3DCURSORCAPS_COLOR            |
                                       WINED3DCURSORCAPS_LOWRES;