If a Fortnite cheat overlay flickers, drifts or refuses to draw at all, the cause is almost always the game's render path rather than the build itself. Fortnite runs on two rendering engines: the stripped-down Performance Mode and full DirectX 12 on Unreal Engine 5. External software behaves differently in each, and the fix takes a minute in the game settings.
The legacy DX11 mode is gone from the client, so in 2026 the choice comes down to these two paths. Below is how they differ in FPS and latency, where exactly overlay rendering breaks, and how to set the whole thing up on a weak machine. Tested on patch v42.00 with builds from the Fortnite cheats → catalogue.
Fortnite's two render paths and what they give
Performance Mode is built for competitive play: simplified geometry, minimal effects, frame rate above all. On mid-range hardware it multiplies FPS against DX12 and cuts input latency noticeably, with many configurations landing at three hundred frames and up.
DirectX 12 runs the full Unreal Engine 5 feature set, Nanite for geometry and Lumen for lighting included. Better picture, fewer frames. On budget hardware the difference is dramatic: turning off Nanite alone returns almost all the lost FPS.
There is a third option for very old graphics cards. On Pascal generation cards, meaning the GTX 900 and 1000 series, DirectX 11 sometimes delivers more frames than DX12, even though the client defaults to twelve.
Nanite, Lumen and the price of a pretty picture
Two of DX12's heaviest components are worth knowing by name. Nanite handles geometry detail and eats most of the frames on budget systems, so switching it off returns nearly everything lost. Lumen computes lighting in real time, looks great on rock faces and indoors, and costs plenty on a mid-range card.
The practical point is that the choice between modes is not binary. You can stay on DX12 for the visuals and disable the heaviest effects, landing on a compromise. But if the goal is stable frames alongside a working overlay, Performance Mode is simpler: it ships without those components, so there is barely anything left to tune.
A separate note for laptop players. Thermal throttling joins the equation there: the game and the software together heat the CPU, clocks drop, and the picture looks like a cheat-induced stutter when the real cause is temperature. You check that with a frame counter and clock monitoring, not by reinstalling the build.
Why this affects the overlay
External software draws its own window over the game without touching the client itself. How that window lands on the picture depends on how the game captures the screen and which window mode it runs in. Exclusive fullscreen hands output straight to the graphics card, and an external overlay does not always make it in.
So the first thing to check when rendering misbehaves: switch Fortnite to borderless windowed mode. It looks identical to fullscreen, and the overlay starts working reliably in both render paths. In our experience that closes most tickets of the "ESP is not showing" variety.
Frame rate and synchronisation
The second most common problem shows up as stuttering and flickering boxes. Usually the overlay refresh rate and the game are out of sync. In the builds this gets fixed in the software's own settings: Krush has VSync, an FPS cap up to 500 and DPI scaling with an auto mode, while Arcane has a separate VSync toggle and a frame counter.
The logic is plain: if the game runs at three hundred frames in Performance Mode while the overlay draws at sixty, your eye catches the difference on fast turns. Aligning the cap or enabling synchronisation removes the effect.
Setting up on a weak machine
If the goal is a game that runs smoothly with the software active, the order goes like this.
- Turn Performance Mode on: the biggest win in frames and latency, especially on budget builds.
- Drop the resolution: 1600 by 900 or 1280 by 720, plus 3D Resolution between 50 and 75 percent of screen resolution.
- Switch off the extras: shadows, anti-aliasing, motion blur. View distance is better left far, since it matters for orientation.
- Borderless windowed mode: a requirement for the overlay to work reliably.
- Take load off the CPU: Mason has a reduced CPU load mode, useful on older quad cores where software and game compete for resources.
A word on very old hardware. If the card comes from the GTX 900 or 1000 series, it is worth comparing DX11 and DX12 in the same match, since the difference can favour eleven noticeably. Run that experiment in a practice mode rather than ranked: you can switch settings between drops and watch the frame counter without risking rating.
What not to do
Do not chase maximum FPS at the cost of information. We regularly see configs where view distance is dialled to minimum for frames, and the player stops seeing opponents at mid range with their own eyes, relying on ESP alone. In Zero Build that ends badly: the software shows a marker, but you have no read on the terrain people are crossing to reach you.
Second: do not run several overlays at once. A recording program, a messenger overlay, the driver panel and your software together produce exactly the picture where everything flickers. The anti-cheat has nothing to do with it, this is several applications fighting over the same output. Check them one at a time: turn off recording, play a match, bring it back, turn off the next one.
Overlay resolution and interface scaling
One more situation people mistake for a fault: the software menu looks enormous or microscopic. The cause is Windows scaling, particularly on high resolution monitors where the system defaults to 125 or 150 percent.
The builds solve this with a DPI setting. Krush has DPI scaling with an automatic mode and a separate menu font size setting. You set it once and forget it. On a dual monitor setup it is worth checking that the game and the overlay sit on the same screen, otherwise some elements drift off the edge.
The Override season and system load
Patch v42.00 on 20 August brought crossover locations, code panels and Override consoles to the map, and with them Sprite effects that fire from several players at once mid-fight. On budget systems that shows: where the drop used to come only in the final circles, it now happens mid-match when someone nearby activates a Sprite.
The practical conclusion is simple. If you tuned your graphics for the previous season and have not touched them since the patch, rebuild the config. This goes double for anyone sitting on DX12 for the visuals: the new effects cost frames, and whatever headroom you had may be spent.
From the software side the same measures help: an overlay frame cap, disabling the animated menu background and the reduced CPU load mode. Arcane turns off animated menu particles with its own checkbox, and on weak machines that helps more than the description suggests.
How to test the setup in one match
A diagnostic order that saves time. First launch a clean client with no software and see whether frames are stable in your render path. Then add the software and repeat the same match on the same map. Compare like with like: same drop spot, same mode, ideally the same server time of day, otherwise the load difference smears the result.
If the FPS drop only appeared on the second step, the question is overlay settings: lower the software frame cap, enable VSync, turn off animated menu elements. If the picture was already sagging on the first step, the game's graphics are the problem and you tune those first.
That test is convenient on daily access, before buying a month. Covcheg from 239 rubles and Mason from 299 rubles suit checking on a specific machine, while Krush from $5 is interesting precisely for its performance settings.
Picking for your system
Builds differ in load and in how many rendering settings they expose. On the cheats for Fortnite → page each one shows its status after the latest patch along with its feature set, including whether it has a frame cap, VSync and resource-saving modes.
If you are unsure what your configuration can handle, ask in the community: Telegram (200+ members) and Discord (637+ members). Setting combinations for specific graphics cards get posted there regularly.
Common questions about Fortnite performance
Why is ESP invisible in fullscreen?
Exclusive fullscreen hands output straight to the graphics card, and an external overlay does not always reach it. Switch Fortnite to borderless windowed mode, the picture will look the same and rendering becomes stable in both render paths.
Performance Mode or DirectX 12 when running software?
Performance Mode wins on frames and latency, so it is the pick on weak and mid-range hardware. DX12 gives you the full Unreal Engine 5 picture with Nanite and Lumen, at a steep performance price. The overlay works in both, provided the game runs borderless windowed.
Does the Override season affect performance?
Yes, the Sprite effects and new locations from patch v42.00 added load, most noticeably on budget systems mid-match. If your graphics were tuned before 20 August, rebuild the config: the frame headroom you had may have gone into the new effects.
How much FPS does a cheat cost in Fortnite?
External software with an overlay is usually cheap in frames, with most of the load coming from menu animations and a high redraw rate. Krush has an overlay FPS cap, Mason has a reduced CPU load mode. On older quad core processors those settings help noticeably.
Is it worth switching to DirectX 11?
Only on old Pascal generation cards, meaning the GTX 900 and 1000 series, where DX11 sometimes delivers more frames. The legacy mode is gone from the client, but the API choice remains. On modern cards DX12 or Performance Mode come out ahead.
The overlay flickers and stutters, what now?
Check how many programs draw over the game at once: screen recording, a messenger, the driver panel. Turn off the extras and keep one. Then align the overlay rate with the game through a frame cap or VSync in the software settings. Builds with those settings are marked on the private Fortnite cheats → page.
