- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 692
- Reaction score
- 457
Most publicly available overlay bases are ancient artifacts from the C++11 era or worse, filled with legacy garbage and inefficient rendering loops. If you are tired of digging through outdated pastes, this modern external DirectX 11 base is a solid starting point for building your own ESP or menu system.
The Technical Meat
This isn't just another ImGui wrapper. The author focused on modern C++ standards and addressed one of the biggest issues with external tools: timing jitter.
Architecture & Compatibility
The architecture is lightweight and doesn't bloat your process. Since it uses DX11, it is compatible with almost everything from the last decade. If you are planning to take this to a professional level, I'd recommend looking into hooking a legitimate overlay (like Discord or Steam) instead of creating a top-level window.
Source Link:
How are you guys handling the overlay detection on the latest EAC builds—switching to DMA or still trying to hide external windows via hijacking?
The Technical Meat
This isn't just another ImGui wrapper. The author focused on modern C++ standards and addressed one of the biggest issues with external tools: timing jitter.
- Rendering: Clean DirectX 11 implementation utilizing ImGui for the UI layer.
- Standard: Written in modern C++, moving away from the messy syntax found in older bases.
- High-Resolution Timer: Most projects rely on
, which suffers from the notorious 15.6ms Windows timer resolution drift. This base implements a high-res timer to ensure smoother frame delivery and less CPU stutter.Code:
std::this_thread::sleep_for - Build Systems: Full support for CMake (for those who prefer a proper workflow) and standard Visual Studio solution files for the click-and-compile crowd.
- Randomization: Includes basic window name randomization. It is not a bypass, but it is better than leaving it as "ImGui Example".
Keep your expectations in check—this is a base, not a finished product for clearing EAC or Vanguard. There are no built-in kernel drivers, hijackers, or sophisticated overlay hiding techniques (like layered window hijacking or using an existing overlay's swapchain). If you run this as-is on a protected game, the anti-cheat will flag the overlay window instantly. It is meant for learning and as a foundation for your own custom bypass logic.
Architecture & Compatibility
The architecture is lightweight and doesn't bloat your process. Since it uses DX11, it is compatible with almost everything from the last decade. If you are planning to take this to a professional level, I'd recommend looking into hooking a legitimate overlay (like Discord or Steam) instead of creating a top-level window.
Source Link:
You cant view this link please login.
How are you guys handling the overlay detection on the latest EAC builds—switching to DMA or still trying to hide external windows via hijacking?