Wrong ID for SetTexture on d3d9

[rebzzel]

Wrong ID for SetTexture on d3d9

[DevCortez]

This is because DirectX is a C compatible project (look at d3d9.h for example), and in C __thiscall does not exist, so this is passed as a normal function argument.
For normal C++ interfaces, this will always be passed to ecx (unless we take into account some compiler optimization cases).

Living and learning :) Thanks for the explanation, ill close the issue to keep things clean.

[Rebzzel]

Hello, @DevCortez.

Hmm, interesting. I don't know what this might be related to. Try to find out what _FP means.
But I think these functions are the same.
Also, I don't think you need to worry about this, because the program will still call 65 when it calls SetTexture.

Have a nice day!

[DevCortez]

Yeah, it seems the application i'm trying to hook just doesn't call settexture the way i expected it to, there is something very shady going on but i guess you are right, in fact, the vftable seems to be just right (at least the semantic of it).

One peculiar detail i noticed tho and i'm not sure where i could ask you that so ill take the opportunity: You treat functions as _stdcall and set the first parameter as this, in the code i always see a plus 4 in the ret (a function with 2 args rets 0xC for instance), do you know if this is consistent with interface methods? Its a bit of an oddity because i expected it to be on ECX as usual (even prepared myself to inline a correction to set ecx to a variable on detours).

[Rebzzel]

This is because DirectX is a C compatible project (look at d3d9.h for example), and in C __thiscall does not exist, so this is passed as a normal function argument.
For normal C++ interfaces, this will always be passed to ecx (unless we take into account some compiler optimization cases).