More FPS on
Apex Legends

What really holds Apex Legends back

Apex runs on a heavily modified version of the Source engine, pushed far past what it was designed for. In battle royale, with sixty players, shields, abilities and physics everywhere, the CPU gives up first. Respawn said as much themselves when talking about CPU-bound scenarios.

The most important change is elsewhere, and it invalidates a huge amount of content still online: Apex only runs on DirectX 12. Respawn warned about it in early 2025, then removed DirectX 11 shortly after. No launch option brings it back. If a guide tells you to add a line to force DirectX 11, it is old, and so is the rest of its advice.

The practical consequence of that switch is DirectX 12 shader compilation. Apex redoes it after a game update and after a graphics driver update. The first matches stutter, then it settles. Your machine is not failing.

The rest is standard battle royale territory: background programs cost you more than any graphics menu line, and a CPU dropping clocks mid-match shows up immediately in your dips.

What FPSDoctor fixes for Apex Legends

FPSDoctor never touches the game, does not modify its config files and will never have you fiddle with an obsolete launch option.

The FPSDoctor power plan holds your CPU clocks, which counts double on a CPU-limited game like this one. The gaming tweaks take over system scheduling. Startup cleanup returns cores and RAM, and game mode deals with whatever is hanging around when you launch.

The GPU optimization applies a profile in the NVIDIA, AMD or Intel panel depending on your card, after saving what was there. On a DirectX 12 engine, how the driver handles its shader cache is part of the equation.

The network latency and network responsiveness optimizations work on the network stack and adapter power saving, which matters as much as frames in a game where one burst ends you.

The BIOS assistant spots an XMP or EXPO memory profile that was never enabled and walks you through turning it on yourself. It never writes to your firmware.

And the built-in counter records your average FPS and your 1 % lows over a session, which is the only honest way to know whether anything changed on your machine.

What you can expect to get back

On Apex, the average is not the interesting number. The engine caps at 300 frames per second: past a certain point it is no longer the average that climbs, it is the dip that lifts. A duel is lost on a drop to 70, never on an average of 200.

That dip is what FPSDoctor goes after first, and it is what the counter records: the 1 % lows of every match, kept next to the average.

The only figure that matters is still yours. One match before, the optimizations, one match after: the history will tell you what your machine actually got back, without you having to trust ours.