4 ms·
Most likely, they just forgot to wait for Valve to ship the update where they whitelist those specific modifications.
by fxtentacle 3y ago
Most likely, they just forgot to wait for Valve to ship the update where they whitelist those specific modifications.
- sillysaurusx 3y agoDo valve whitelist those? I think the geforce changes operate by hooking into the actual rendering functions, not individual games —- or can they?
- armada651 3y agoGPU vendors don't have to hook rendering functions since they're the ones providing the implementation of those rendering functions. If Nvidia requires extra hooks into the game they usually ask the developer to call certain functions in NVAPI, which is their vendor-specific driver interface.
- no_time 3y agoThere must be some kind of whitelist system. Discord for example doesn't have many options to draw it's ingame overlay. They either create a topmost transparent window (does not work in exclusive fullscreen) or hook glEnd() of the targer or however it's called these days.
- armada651 3y agoCounter-Strike allows detouring of system calls by code signed DLLs if it's not running in trusted mode. Once it's running in trusted mode all hooking is blocked, so even the Discord overlay would not be allowed. Source: https://help.steampowered.com/en/faqs/view/09A0-4879-4353-EF95 https://help.steampowered.com/en/faqs/view/09A0-4879-4353-EF...
- deleted 3y ago[deleted]
- armada651 3y ago> Is there a whitelist of software that can be safely injected into CS:GO? > No. Unfortunately, even benign applications are often a vector for cheats that hijack them in order to cheat in CS:GO. So in Trusted mode, all foreign software is blocked. Source: https://help.steampowered.com/en/faqs/view/09A0-4879-4353-EF95#whitelist https://help.steampowered.com/en/faqs/view/09A0-4879-4353-EF...
- AshamedCaptain 3y agoAlmost 100% sure they keep a whitelist with all common GPU drivers. Note that by definition GPU drivers _require_ the ability to inject DLLs into the process, read/write to the process memory, and even create new threads on it... That's the reason Chrome and derivatives put GPU stuff on a separate process. But you try to do this type of sandboxing on a game and it will utterly destroy performance.
- dogma1138 3y agoCan you provide some docs around it? It goes quite against everything public, when NV adds new features that are not part of D3D or other APIs they release binaries for developers to use to call NVAPI directly Ive never seen their driver injects anything into a running process.
- AshamedCaptain 3y agoD3D is not IPC. It is mostly implemented in the process' address space. When you call a D3D function you are not magically dumping all your primitives into the kernel-side driver (which would be slow), you are calling into nvd3dum.dll which _may_ eventually call into the kernel. All of this happens in the same process and therefore the GPU driver can do whatever the hell it wants to it.
- mardifoufs 3y agoYes but this derouted the engine.dll (or equivalent) code in userspace (not sure if that's the right term here). I agree that they probably whitelist or even just don't check the graphics or rendering related functions, since tons of mods allow you to do that without any widespread ban wave. But when it's hooking to the core engine code, I think that's a different story. Correct me if I'm wrong though.