d3d9 | Direct3D9 wrapper for Go

I'm trying to draw CEF buffer (returned on OnPaint) to D3D9 texture of the game, and game randomly premanently freezes. I figured out that code provided below is the reason of the game freeze, but still can't understand. What did I miss?

There is a problem with run Unity project on Hyper-V virtual machine. To make a long story short, my Unity project is working on my PC, but doesn't work on a VM. I described this in detail here:

https://stackoverflow.com/q/65550732/5709159.

I found a crash log where Unity wrote everything. Because there is a restriction on number of chars that I can post on stack overflow I uploaded the full file here: https://drive.google.com/file/d/1xAtTUytNGH7WFSSIr8WGotCDrvQKW9f-/view, and here I just posted the last part of this file:

I making a d3d9 app in C, but when trying to create a device object it fails in C, but its counterpart in C++ just works and returns S_OK.
C:

I'm trying to create a transparent overlay over some process' window (I want to draw some stuff on the overlay using Direct3D 9).

The overlay is being created by using an external program (not a .dll injected library or something).

The problem is when I launch the program, an invisible overlay appears over the process window (and it even draws some text on it, so the WM_PAINT seems to be working), but in the next few seconds the cursor becomes a "sand clock" styled (sorry, I don't know how else is it called xd) and if I click on the window, it shows an error "The app is not responding" and becomes solid white.

I import the overlay class into the entry point file and here's how I run it in the main function (simplified):

Hi I am trying to combine the given code with mine to output an array of pixels from the image, but the problem is 1) It outputs an empty array 2) memcpy fails with "unique_ptr to const void * ERROR" How to access pixels data from ID3D11Texture2D?

To be honest, I don't understand what the problem might be, because I did everything as it says. Help please, maybe I missed something.

Yes I included all the libs but every time I run my program in x64 it gives me an unresolved symbol but works perfectly in x32??

Severity Code Description Project File Line Suppression State Error LNK2019 unresolved external symbol Direct3DCreate9Ex referenced in function "int cdecl DirectXInit(struct HWND *)" (?DirectXInit@@YAHPEAUHWND__@@@Z) DirectX Overlay D:\VSprojects\2020\Mygui\Garrysmod take 2\Overlay aimbot\DirectX.obj 1

I needed to draw some simple shapes and I decided to go with D3D9. After going through a few of the tutorials on directxtutorial.com, I finally have all the code and knowledge I need to make my first shape appear on the screen. The problem is, though, that no image is appearing. I've looked over the code many times and have compared it with the code on the website, and it all checks out. Why is nothing rendering on the screen?

On the D3D10 Docs is a list which shows the deprecated features from D3D9 to D3D10. It says that W buffering is no longer supported and we should use high-precision depth buffers/Z-Buffers instead. I suspect that it is also not (fully) supported in Direct3D 11 and 12. But is there any way to use W-buffers in Direct3D 12?

I am following the process to create a trampoline in order to hook a dll function (in my case Direct3DCreate9 from d3d9.dll) as outlined here: https://www.malwaretech.com/2015/01/inline-hooking-for-programmers-part-1.html and https://www.malwaretech.com/2015/01/inline-hooking-for-programmers-part-2.html

My code differs slightly as I am working out the offset bytes manually using a disassembler rather than using the hde32_disasm function.

Everything seems to work fine, the victim process calls my injected dll wrapper function, the new function does some stuff, then calls the original function (Direct3DCreate9), once the original returns the wrapper should then call some other stuff, before returning to the victim process.

Unfortunately when the original function is called from the hook wrapper it returns back to the victim application and not the hook wrapper, this means it misses out some of the code from the wrapper.

Having stepped through the disassembly it looks as though the call stack is being overwritten so when the Direct3DCreate9 returns it pops back to the victim application instead of my hook function that made the call.

I'm guessing I need to push the hook function manually onto the call-stack? How would I go about this?

Other potentially pertinent information: Both the victim process and the hook have been built in debug mode. Direct3DCreate9 is a __stdcall and I am using vs2010 for the hook dll, but the victim process was compiled with vs2015.