Not sure if this breaks the DX12 version, but seems wrong to me, to be referring to injecting the DX11 EXE
Code: Select all
[ENABLE]
aobscanmodule(INJECT,Control_DX11.exe,0F 2F 51 64 0F 93 C0) // should be unique
alloc(newmem,$1000,"Control_DX11.exe"+2C7FCE)
Indeed, if it wasn't for two occurrences of "Control_DX12.exe", I would say you uploaded the the DX11 version twice.
In total there are 153 occurrences of "Control_DX11.exe", where I would expect to see "Control_DX12.exe"instead.
A few are clearly commented out (starting "// ", but most are not.
This is the only time DX12 EXE is used, in the DX12 CT in the "Inf Power" section
Code: Select all
[ENABLE]
aobscanmodule(INJECT,Control_DX12.exe,F3 0F 11 41 40) // should be unique
alloc(newmem,$1000,"Control_DX12.exe"+E07E5)
Apart from that one reference, the DX12 CT is identical to the DX11 CT.
I can't see how, this script can work on DX12 in it's current state.
I've just checked, and only "Control_DX12.exe", is running, so the DX11 EXE isn't even running in the Memory, and doesn't seem called as either a thread, or module according to Process Hacker.