Controls & Peripherals / Apex Legends / Modified Source

Apex Legends: Fixing Mouse Input, Packet Loss, and Frame-Time Jitter

A clean input and network troubleshooting path for Apex Legends, with a minimal Source-engine configuration.

Official Steam Store header artwork for Apex Legends.

Apex uses a modified Source engine with its own input and network layers. Most “my aim is off” cases are a mouse path or a packet-loss problem before they are a sensitivity problem.

Fixing Mouse Input, Packet Loss, and Frame-Time Jitter

Verified field fix

The shortest safe order for this issue:

  1. Disable mouse acceleration and remove overlay hooks before changing sensitivity.
  2. Test packet loss with a wired connection and no background uploads.
  3. Cap the frame rate to stabilise frame delivery and verify the change with a benchmark.

The physical input path

Use a wired mouse or a receiver on a direct USB port, disable pointer acceleration, and remove third-party overlays. If the game has a raw input option, confirm it. Sensitivity is a preference; skipped counts and inconsistent movement are not.

%USERPROFILE%/Saved Games/Respawn/Apex/local/autoexec.cfg
fps_max 0
cl_showfps 1
// Keep the list minimal.
// Verify any command in-game; old Source cvars may not apply to Apex.
Use the in-game benchmark and performance overlay. A command that is accepted is not automatically a performance fix.

Network loss looks like bad aim

Open the performance overlay and watch for packet loss and frame-time spikes separately. A wired Ethernet test with background downloads stopped is the clean baseline. Do not stack rate commands from CS or TF2; Apex is not the same client.

Field notes before you change the build

Input for Apex Legends passes through the device firmware, Windows, any vendor software, Steam Input if enabled, and finally the Modified Source client. Test one layer at a time, starting wired and with the vendor layer removed. A sensitivity change cannot repair a skipped USB report.

Use the same display refresh rate and a stable frame cap for every comparison. If aim or camera motion feels inconsistent only when frame time spikes, treat it as a performance problem before buying a new peripheral.

  • Do not stack two deadzones or two response curves.
  • Do not change DPI, polling rate, and in-game sensitivity in the same test.
  • Do not use a third-party injector to bypass an anti-cheat input path.

Check it before you keep it

Test aim and packet loss in the firing range before a live match

0 / 5 complete

One input chain at a time

When the setup feels right, write down the device, connection, profile, and in-game values. That baseline is more useful than another round of random sensitivity adjustments.

The line to keep

Separate the mouse from the network. A consistent input path plus a stable frame time is the actual aim fix.

Did this fix work on Patch Season 28.1 — netcode and stability?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Season 28.1 — netcode and stability. Votes are local-only telemetry.

Apex Legends: bench questions

2 answers
Does an autoexec improve Apex performance?
Only if it changes a setting that affects your machine. Most gains come from resolution, GPU load, and a clean network path.
Why does packet loss only happen in Apex?
It can still be a local router, Wi-Fi, or upstream issue that the game exposes more readily. Test another online game and the same network path.
Filed under

Controls & Peripherals

Patch tested: Season 28.1 — netcode and stability

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.