- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 179
- Reaction score
- 7
Anyone else working on DMA overlays lately? Been messing around with the Discord legacy overlay framebuffer method, and it is honestly a massive improvement over the usual Fuser-based setups.
The logic here is pretty clean: it creates a render target, hooks into the Discord process, and pushes the ImGui output directly into the frame buffer. Since you are handling key states and mouse positions through your DMA board, you basically bypass all the usual window capture issues you get with standard streaming or overlay software.
Technical breakdown:
This is arguably the fastest overlay implementation I have seen for a DMA setup. It eliminates that slight input lag and ghosting that plagues most external overlays. Obviously, make sure your firmware is solid if you are planning on running this on a main account, though sticking to alts is always the play with any new injection method until the ban waves confirm stability.
I have been testing this for a few days now, and the resource usage is negligible compared to running a heavy separate overlay process. The draw calls are consistent, even during intense fights.
Has anyone else tried pushing this into other processes besides Discord? Thinking about testing if this can be ported to other stable framebuffers to avoid the need for a Fuser entirely. Drop your findings or any optimizations you have made to the render loop below.
The logic here is pretty clean: it creates a render target, hooks into the Discord process, and pushes the ImGui output directly into the frame buffer. Since you are handling key states and mouse positions through your DMA board, you basically bypass all the usual window capture issues you get with standard streaming or overlay software.
Technical breakdown:
- Architecture: External render target using ImGui.
- Execution: Direct memory writing to the Discord framebuffer via DMA.
- Input handling: Tracks mouse and keyboard state to keep the overlay reactive.
This is arguably the fastest overlay implementation I have seen for a DMA setup. It eliminates that slight input lag and ghosting that plagues most external overlays. Obviously, make sure your firmware is solid if you are planning on running this on a main account, though sticking to alts is always the play with any new injection method until the ban waves confirm stability.
I have been testing this for a few days now, and the resource usage is negligible compared to running a heavy separate overlay process. The draw calls are consistent, even during intense fights.
Has anyone else tried pushing this into other processes besides Discord? Thinking about testing if this can be ported to other stable framebuffers to avoid the need for a Fuser entirely. Drop your findings or any optimizations you have made to the render loop below.
