Am Freitag, 25. November 2005 21:30 schrieben Sie:
D3D works fine for me with Diablo II & Diablo II: Lord of Destruction in recent winehq.
If I remember right, you just have to `wine D2VidTst.exe` then hit "Skip Test", and pick the "Direct3D DirectDraw HAL" option (and then hit "OK").
Might have been some registry poking needed to make it happy running in 32bits, since 16bit switching isn't supported by any drivers. I've no idea which key it was, though, nothing's jumping out at me poking around in the registry.
This is strange: The VidTest worked fine for me, I selected Direct3D DirectDraw HAL, but D2 does not even attemt to initialize D3D and runs with DDraw only instead.
Now I can at least try to get D2VidTest working with my d3d7 implementation, to solve some more capatiblity flag issues.