Venis

the hooking of genuine IDirect3DQuery9 objects for the only purpose of logging will be available by rebuilding the project with the #define HOOKD3D9QUERYINTERFACE statement if it have negative effect on efficience of d3d drawing,it's neccessary i guess

CoD4 is still requies some pre-conditional hack for Vertex and textrue format,however it's fairly simple to bypass,the hardest section is the query9 obejct,now seems like conqured.Great job

Test with this build,but i'm still wondering whether we can directly manipulate the geniune createquery9 object

Do you refer to your custom build or to my dxwnd.dll that I posted here https://sourceforge.net/p/dxwnd/discussion/general/thread/c5891cdcc6/?page=1#5df7/4cbf/f8a2 ? I ask because I fear that my hack architecture is quite different from yours. I'm testing with the wip12 dll,it shows your fake object type works great, In my hack architecture,its based on the same idea that forcing SW TnL flag for some hardcoded program,however,this "middleware" layer can only change the parameters it sends to,but...

It's the RegSetKeyValueW from ADVAPI32

You should not use existing flags like TEXTUREMASK and TRANSFORMANDLIGHT to activate custom features because in this way you would also activate the corresponding hacks and this may alter the target behavior. You should use the EXPERIMENTAL flags. Anyway,it's just an temp workaround for GUI test switch when I have no spare time to digging out which option it belongs to,but this option seems like takes no effect in Dxwnd panel,is it the "texture handling" section?

Great,it will be better to exist as an tweak in there

Yeah,after some explore i found the debug option,however,I think it will be a bit difficult to find this without manual ;)