WDDM Hook - UD D3D HOOKING
WDDM Hook - UD D3D HOOKING
Hi..
today a full source :P
If u don know whatś WDDM - dont use it ..
It also includes a simple Hook Class .. (not finished :P)
Its UD for most Anti-Cheats ..
Use Code::Blocks :P
Give me Credits ..
PCe
PCeumel-WDDM_HOOK.zip - Jotti's malware scan
https://www.virustotal.com/de/file/a...is/1362502108/
today a full source :P
If u don know whatś WDDM - dont use it ..
It also includes a simple Hook Class .. (not finished :P)
Its UD for most Anti-Cheats ..
Use Code::Blocks :P
Give me Credits ..
PCe
PCeumel-WDDM_HOOK.zip - Jotti's malware scan
https://www.virustotal.com/de/file/a...is/1362502108/
my question?
it's hotkeys?
or menu?
and thanks
and im stoped coding for CF hacking
but im like thank ppl like helping
Thanks
it's hotkeys?
or menu?
and thanks
and im stoped coding for CF hacking
but im like thank ppl like helping
Thanks
WDDM is still working and undetected ? 
get ready for tons of questions 
you still didnt tell me where you learned it
you still didnt tell me where you learned it
Originally Posted by giniyat101
get ready for tons of questions
you still didnt tell me where you learned it
you still didnt tell me where you learned it
@OP: Instead of using the hardcoded DLL-names for ATI/NV you might better want to utilize IDirect3D9::GetAdapterIdentifier, which allows you to retrieve the driver's name much cleaner. By the way you could just patch the callback pointers in the structure filled by the original OpenAdapter (and later CreateDevice) call, making your hook even stealthier. If I were you, I'd also consider removing the OpenAdapter detour after it triggered for the first time.
Originally Posted by Ende!
Probably in ntKid's post on GD. Guess I won't be allowed to post the full URL.
@OP: Instead of using the hardcoded DLL-names for ATI/NV you might better want to utilize IDirect3D9::GetAdapterIdentifier, which allows you to retrieve the driver's name much cleaner. By the way you could just patch the callback pointers in the structure filled by the original OpenAdapter (and later CreateDevice) call, making your hook even stealthier. If I were you, I'd also consider removing the OpenAdapter detour after it triggered for the first time.
@OP: Instead of using the hardcoded DLL-names for ATI/NV you might better want to utilize IDirect3D9::GetAdapterIdentifier, which allows you to retrieve the driver's name much cleaner. By the way you could just patch the callback pointers in the structure filled by the original OpenAdapter (and later CreateDevice) call, making your hook even stealthier. If I were you, I'd also consider removing the OpenAdapter detour after it triggered for the first time.
I've patched the hooks in my (not public) version .. :P
Newer heared something about GetAdapterIdentifier but thx ^^
Pce
Nice bro
approved .
just checked it out
why did you copy some stuff from directx sdk to struct.h?
why did you copy some stuff from directx sdk to struct.h?
PCe, why you Post This?
cool thanks
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
What it is
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
What it is
omg @pceumel you're back?
Originally Posted by Barstarzz
omg @pceumel you're back?
---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------
Originally Posted by CFHackerExtreme
PCe, why you Post This?
The best thing to stay undetected is to just not hook... lol =D
I try this thing.
