Controls & Peripherals / American Truck Simulator / Prism3D

American Truck Simulator: config.cfg, 120 FPS, and Wheel FFB

A 120 FPS Prism3D baseline and force-feedback setup for American Truck Simulator that avoids clipping and placebo sliders.

Official Steam Store header artwork for American Truck Simulator.

American Truck Simulator can run at high frame rates, but the city route and mirror load decide whether 120 FPS is stable. Wheel feel follows a separate chain: firmware, calibration, and in-game gain.

config.cfg, 120 FPS, and Wheel FFB

Verified field fix

The shortest safe order for this issue:

  1. Set the display refresh rate in Windows before editing config.cfg.
  2. Lower mirror quality and shadow range before disabling all detail.
  3. Set wheel force feedback below clipping, then calibrate the steering range.

A 120 FPS baseline

Use DX11 for a clean first run, 100–125% render scale, and medium mirror quality. A 118 FPS cap on a 120 Hz display leaves a little headroom. Test a city loop and a highway route separately; a GPU result from the highway alone hides the CPU cost of a dense city.

%USERPROFILE%/Documents/American Truck Simulator/config.cfg
uset r_vsync "0"
uset r_mode_refresh "0"
uset r_buffer_page_size "30"
uset r_texture_detail "0"
uset r_anisotropic_filtering "3"
uset r_smaa "1"
uset t_averaging_window_length "20"
uset g_menu_aa_limit "0"
Back up config.cfg before editing. The game can rewrite values when it exits.

Force feedback without clipping

Calibrate the wheel range in the manufacturer software and match it in-game. Start with 60–70% gain, then raise it only if the wheel is not clipping. Road-surface and engine-vibration effects are optional garnish; steering weight and self-aligning torque are the information you need.

Field notes before you change the build

Input for American Truck Simulator passes through the device firmware, Windows, any vendor software, Steam Input if enabled, and finally the Prism3D 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 a city route and a highway route separately

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

Set the display, stabilise the route, then tune the wheel. A 120 FPS goal is a whole-system setup, not a single line in config.cfg.

Did this fix work on Patch 1.59 — DX12 beta and wheel API?

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

Verified against 1.59 — DX12 beta and wheel API. Votes are local-only telemetry.

American Truck Simulator: bench questions

2 answers
Is DX12 faster in ATS?
On some hardware the beta path improves frame consistency, but it can introduce first-load shader work and new driver interactions. Test the same city route twice.
Why does my wheel feel light after an update?
Check the controller profile, wheel range, and in-game gain. A reset profile or a mismatched rotation range can make FFB feel vague without any game bug.
Filed under

Controls & Peripherals

Patch tested: 1.59 — DX12 beta and wheel API

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.