If you dont want to hook CreateDevice9 on startup to get the devicepointer you just hook it using the static adress + offsets I posted in the information thread for 3.1.2 it didn't change, credits to SKU
If you dont want to hook CreateDevice9 on startup to get the devicepointer you just hook it using the static adress + offsets I posted in the information thread for 3.1.2 it didn't change, credits to SKU
Yeah I'm still not sure why folks are saying that C# pointer writing throws lots of exceptions; it throws no more exceptions than any other pointer writing (assuming we're talking about the same thing, which is using unsafe pointers).
You have to know what you're doing -- whether or not you're writing to protected memory, whether or not there are any race conditions, and so on -- but it's not some kind of rocket science. I use various pointer writes ALL the time in my code (like dozens of times per second) with no try/catch and no problem.
One real benefit of unsafe code is that you can cast struct pointers which are sparse (not all fields sequentially laid out or present) using FieldOffset attributes.
WriteProcessMemory is just a write with a try/catch, when you use it internally.
Don't believe everything you think.
Well, all I know is that I've never had problems with reading using WPM/RPM. I had many issues with pointers. Got tired of having unknown problems.
Wow this thread.. Can't wait till Cypher responds.![]()
I code in autoit because pointers are harrrddddd.