Controls & Peripherals / PRAGMATA / RE Engine

PRAGMATA: Fixing Controller Deadzones, Aim Drift, and Input Lag

A controller and frame-time checklist for PRAGMATA aim drift, mushy sticks, and inconsistent input response on PC.

Official cover artwork for PRAGMATA, featuring Capcom, RE Engine, and Sci-Fi Action cues.

Aim problems in a third-person action game rarely have one cause. The controller firmware, Steam Input, the in-game deadzone, and frame time all feed the same stick response.

Fixing Controller Deadzones, Aim Drift, and Input Lag

Verified field fix

The shortest safe order for this issue:

  1. Disable Steam Input for PRAGMATA and test the controller with its native driver.
  2. Calibrate the controller in Windows, then adjust the in-game deadzone rather than stacking both.
  3. Cap the frame rate below the average to stabilise input polling and frame delivery.

Stop layering two input translators

If Steam Input is enabled on top of a native controller profile, both layers can apply a deadzone and a response curve. Disable Steam Input for the title first, then verify that Windows sees the correct device. A drifting stick should be tested in the controller’s own calibration tool before the game gets blamed.

%LOCALAPPDATA%/CAPCOM/PRAGMATA/config.ini
[Controller]
Deadzone=0.12
AimResponse=Linear

[Display]
FrameRateCap=120
VSync=0
The menu may override these keys. Change one value at a time and confirm it survives a restart.

Cap for consistency, not for the biggest number

Uncapped frame times create uneven input sampling even when the average is high. A 118 or 141 FPS cap on a 120 or 144 Hz display usually feels more consistent. Keep V-Sync off for latency testing and use the game’s own limiter before adding an external one.

Field notes before you change the build

Input for PRAGMATA passes through the device firmware, Windows, any vendor software, Steam Input if enabled, and finally the RE Engine 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 the controller in a stable, low-load area

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

Fix the physical input first, then the input layer, and only then the frame cap. Reversing that order makes every test inconclusive.

Did this fix work on Patch 1.02 — frame pacing and FSR fix?

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

Verified against 1.02 — frame pacing and FSR fix. Votes are local-only telemetry.

PRAGMATA: bench questions

2 answers
Should I use Steam Input for PRAGMATA?
Start with it disabled. Native support is usually the cleanest path, especially with a first-party controller. Use Steam Input only if you need remapping that the game does not expose.
Does a higher polling rate fix aim drift?
No. Drift is usually a hardware deadzone or calibration issue. A higher polling rate can add CPU overhead without repairing a faulty stick.
Filed under

Controls & Peripherals

Patch tested: 1.02 — frame pacing and FSR fix

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.