Fixes compatibility issues with older games running on Windows 10/11 by wrapping DirectX dlls. Also allows loading custom libraries with the file extension .asi into game processes.
Follows https://github.com/elishacloud/dxwrapper/issues/164#issuecomment-1644897489 and assuming d3dx is even something that you (can) care.
It turns out that my weird observation is the result of a directx sdk change. Up until the december 2005 version, I get the high numbers.
Starting with the one from february 2006 (not sure about the latest, but still) I'm getting half if not even less the framerate.
Under wine, there is still a nominal difference, but it's leaps and bounds lower.
This is the breakdown of the sample internals:
While this is the stack for every one of those d3dx9_29.dll calls
Is there something that could (and should) be done to avoid this?
Follows https://github.com/elishacloud/dxwrapper/issues/164#issuecomment-1644897489 and assuming d3dx is even something that you (can) care. It turns out that my weird observation is the result of a directx sdk change. Up until the december 2005 version, I get the high numbers. Starting with the one from february 2006 (not sure about the latest, but still) I'm getting half if not even less the framerate. Under wine, there is still a nominal difference, but it's leaps and bounds lower.
This is the breakdown of the sample internals:
While this is the stack for every one of those d3dx9_29.dll calls
Is there something that could (and should) be done to avoid this?