Stefan Dösinger wrote:
Our d3d implementation works pretty well on Windows(well, as good as it does on Wine), with the exception of directdraw. The problem with ddraw is that ddraw.dll needs wined3d.dll, which loads opengl32.dll, and Microsoft's opengl32.dll loads ddraw.dll. Oops.
Currently we have no real attacking point to this issue.
Is there any good reason for the windows opengl32.dll to be loading ddraw.dll? Might it load it without actually using it? Seems odd that the 3D acceleration API would want to hook into the legacy 2D one.