WELCOME TO INFOCHEATS.NET

INFOCHEATS is a community-driven platform focused on free game cheats, cheat development, and verified commercial software for a wide range of popular games. We provide a large collection of free cheats shared by the community. All public releases are checked for malicious code to reduce the risk of viruses, malware, or unwanted software before users interact with them.

Alongside free content, INFOCHEATS hosts an active marketplace with many independent sellers offering commercial cheats. Each product is discussed openly, with user feedback, reviews, and real usage experience available to help you make informed decisions before purchasing.

Whether you are looking for free cheats, exploring paid solutions, comparing sellers, or studying how cheats are developed and tested, INFOCHEATS brings everything together in one place — transparently and community-driven.

Guide CS2 Decal Removal — Signature & Fastcall Hook for Client.dll

byte_corvus

Expert
Expert
Expert
Expert
Status
Offline
Joined
Mar 3, 2026
Messages
720
Reaction score
457
Sick of the visual clutter in CS2? Between the massive blood splatters and bullet holes, visibility in Premier can drop significantly during heavy spray-downs. If you are working on an internal base, you can easily nuke these decals by hooking the render function in client.dll.

Engine Logic & Render Hooks

The goal here is to intercept the decal rendering pipeline. By returning a null pointer when your toggle is active, the engine simply skips the drawing calls for bullet decals, blood stains, and other surface overlays. It's a clean way to maintain high visibility without messing with game files or risky material overrides.

Code:
// 44 88 4C 24 ? 55 53 @ client.dll
void* __fastcall hk_render_decals(__int64 render_ctx, __int64** render_view, bool pass_flag_A, bool pass_flag_B) {
    if (m_remove_decals)
        return nullptr;

    return hooks::m_render_decals.call<void*>(render_ctx, render_view, pass_flag_A, pass_flag_B);
}

Implementation Notes
  1. Signature: Use the provided 44 88 4C 24 ? 55 53 to find the function offset in the current client.dll build.
  2. Calling Convention: This is a __fastcall, so ensure your hook signature matches the stack layout precisely to avoid stack corruption.
  3. Performance: Since this is called frequently during rendering, keeping the logic to a simple boolean check is optimal.

Does this affect FPS?
Actually, it can slightly improve frame stability in heavy firefights by reducing the number of draw calls the engine has to process.

Is there a risk of crash?
Only if your hook wrapper is scuffed. Returning nullptr here is handled safely by the engine's rendering logic.

Will this work on sub-tick matches?
Yes, this is purely a visual/rendering stage hook and doesn't interfere with networking or the sub-tick system.

Definitely useful for those building a "legit" oriented internal where clean visuals are a priority. Anyone tried implementing this alongside a bloom/fog remover for a full clean-map look?
 
Top