3 ms·

This wasn’t the driver doing what ever it wants up stream it was overriding the renderqueue and other functions within the executable at runtime. As far as I k

• AshamedCaptain 3y ago
  I really doubt that; not because they haven't done that in the past, because they have; but because with the frequency of updates of game clients these days you really cannot get away with that as easily. On the other hand, hooking the lower-level Win32 functions is extremely common, I am yet to see a GPU driver that doesn't implement some level of idle/activity detection based on hooking the message loop, for example. My bet is they have just decided to put whatever this new thing is in a separate module which they they forgot to send to Valve for whitelisting.
  • armada651 3y ago
    There's a world of difference between hooking a message loop and hooking a Win32 function: You can hook a message loop using regular Win32 APIs, while hooking a Win32 API requires you to modify code in the process. Specifically you need to inject a trampoline function into the process memory and then overwrite the first two bytes of the Win32 function you'd like to hook with a jump instruction to your trampoline. The former is a lot easier to allow while the latter is much more likely to open the flood gates for cheats.