Failed to load function d3d9.dll direct3dcreate9

#Failed to load function d3d9.dll direct3dcreate9 code#

#Failed to load function d3d9.dll direct3dcreate9 code#

To be fair, the C# code wasn't the problem specifically, it was transitioning between managed and unmanaged code very often that appeared to cause the slowdown. Depending on your needs, this may not be an issue but for my needs it caused problems so I'm trying a managed C++ approach now. To note, I have since dropped this method of doing things because the native > managed > native transition was too expensive for use in a real-time gaming application (frame rate dropped from ~60fps to ~40fps just calling one of my functions every frame.

I also initially ported IDirect3D9 over to C# at first but as you said, you can't return your custom IDirect3D9 object because it's managed and the hooked application expects an unmanaged IDirect3D9 object.Д«y typecasting the IntPtr that Direct3DCreate9 returns to a C# structure with an IntPtr* was the only way I could figure out to successfully gain access to the native IDirect3D9 structure through managed code. If you hook Direct3DCreate9 and have your hooked function just call the real one and return the IntPtr the real one returns, do you still experience the crash?

(We haven't written the wrapper yet but thats next.) So what we are going to need to do is have the function think it's. What we want the function to do instead of creating a normal instance of Direct3D is to create a new instance of our wrapper. I didn't experience the crash you are referring to. The next step after creating the trampoline will be to create our new function for Direct3DCreate9.