Controls & Peripherals / The Finals / Unreal Engine 5

The Finals: Controller, DualSense & Raw Mouse Input Latency Fixes

Fix The Finals input lag, deadzones, DualSense/FFB detection, and raw mouse polling for a clean competitive or simulation control path on Unreal Engine 5.

Cover artwork for The Finals on the GamePathHub field file.

Input latency is a chain

In The Finals, the path from your hand to a rendered frame crosses the device driver, the operating system, the game’s polling loop, and the display. A slow link anywhere in that chain feels identical to a broken link. Fix the chain in order, not by buying a new mouse first.

The input audit

  1. Test the device on a known-good title. If the lag follows the device, stop here.
  2. Check the connection: wired first, a direct USB port rather than a hub, and no wireless receiver behind a metal case.
  3. Disable the game’s own smoothing, acceleration, and deadzone helpers, then retest.
  4. Confirm the in-game refresh rate matches the display mode Windows is actually using.
  5. Record one clip at 240 fps with a hardware timer if you are comparing two configurations.

A clean The Finals control path

Low-latency baseline

These four changes solve most reported latency complaints.

  • Set the display to its native refresh rate before launching the game.
  • Cap frame rate below refresh to keep the render queue short.
  • Turn off in-game motion blur and camera smoothing for competitive play.
  • For controllers, use a wired connection and re-test the deadzone after any firmware update.

Raw mouse input and controller detection

On Unreal Engine 5, the raw-input flag is not always exposed in the menu. When the game ignores a controller or reports the wrong device, close every virtual controller driver, unplug the extra devices, and let the game re-enumerate. A wireless headset that presents itself as a gamepad is a classic culprit.

If the game supports a config or launch path, keep the input values with the rest of your tested settings:

%LOCALAPPDATA%\TheFinals\Saved\Config\Windows\GameUserSettings.ini
[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.ShaderPipelineCache.Enabled=1
r.ShaderPipelineCache.StartupMode=3
r.GPUCrashDebugging=0
r.FrameRateLimit=0

[DevOptions.RendererSettings]
r.DefaultFeature.AutoExposure=1
Add only to the game-specific Engine.ini, not the global Unreal config. Pool size above installed VRAM is how 8 GB cards start hitching.

Force feedback is a separate subsystem

For wheel users, force feedback quality depends on the game’s telemetry rate and the wheel’s firmware, not on the graphics preset. Verify the wheel in its own control panel first, then set the in-game rotation to match the hardware. If the wheel detects but the force feedback is dead, restart the game after the wheel software has initialised — not before.

Verify the fix

Peripheral verification for The Finals

0 / 5 complete

The line to keep

A stable 141 fps with a short render queue beats a fluctuating 240 fps every time. Latency is what the queue does, not what the number says.

Did this fix work on Patch Current live build — verified Nov 2026?

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

Verified against Current live build — verified Nov 2026. Votes are local-only telemetry.

The Finals: bench questions

2 answers
Is this The Finals fix safe for my current save?
Yes when you back up the profile first. The routine changes configuration and caches, not the save file itself. If a fix edits an active save, the file path and the backup step are called out in the guide.
How do I know the controls & peripherals fix worked?
Repeat the same action that failed before the change and compare like for like. For crashes, that means a cold launch. For frame pacing, that means the same route with a frame-time capture. A fix you cannot re-test is not verified.
Filed under

Controls & Peripherals

Patch tested: Current live build — verified Nov 2026

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.