Controls & Peripherals / Euro Truck Simulator 2 / Prism3D

Euro Truck Simulator 2: config.cfg, 120 FPS, and Honest Wheel FFB

A stable 120 FPS configuration path for ETS2, plus a force-feedback checklist that separates useful wheel feel from placebo sliders.

Official Steam Store header artwork for Euro Truck Simulator 2.

Euro Truck Simulator 2 is old enough to run on a potato and demanding enough to punish a careless high-refresh profile. Mirrors, shadows, scaling, and the city simulation all compete. The 1.58 update’s DX12 beta adds a real alternative to DX11, but it also makes the “just set everything to max” advice even less useful.

This file targets a clean 1440p 120 FPS profile and a wheel setup that communicates the road without fighting you. It is written for a direct-drive or belt-driven wheel with manufacturer software installed.

The 120 FPS starting point

1440p / stable
  • DX11 for the first clean baseline; test DX12 as a separate experiment.
  • Render scale 100–125%, not 400%. Supersampling is not a personality.
  • Mirror resolution medium and distance balanced; four high-res mirrors are a GPU tax.
  • Cap at 118 FPS for a 120 Hz display, leaving a little frame-time headroom.
  • Set FFB gain around 60–80% and avoid clipping before chasing “detail.”

The file that actually holds your settings

ETS2 stores most of its local configuration in a text file under Documents. The game rewrites it when it exits, so edit only while the game is closed.

%USERPROFILE%\Documents\Euro Truck Simulator 2\config.cfg
# GamePathHub conservative baseline
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 the file. The game may normalise values on exit.
A refresh value of 0 lets Windows/display determine the mode. If your display stubbornly runs at 60 Hz, set the Windows refresh rate first, then verify in-game.
Config builder / Euro Truck Simulator 2 Prism3D

Built locally in your browser. Nothing is uploaded.

Game config directory
; GamePathHub // Euro Truck Simulator 2
; Engine: Prism3D | GPU class: 12 GB | Target: 120 FPS
; Upscaler: DLSS Quality
; Change one group at a time. Back up the original file first.
# Prism3D conservative baseline
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"
Prism3D accepts edits only while the game is closed. The config file is rewritten when the game exits, so re-check after each launch.

Why 120 is not just a GPU target

In cities, ETS2’s frame time is influenced by CPU traffic, mirror rendering, and the number of AI vehicles. A GPU upgrade can raise the open-road average while the city 1% low stays flat. Use a repeatable route through a dense city and a highway section; measure both.

ETS2 / 1440p high-refresh verification
Scale 0–150 FPS
Black: average / Blue: 1% low
DX11 / 100% scale / medium mirrors 126 FPS / 96 low
DX11 / 125% scale / high mirrors 103 FPS / 78 low
DX12 beta / 100% scale / medium mirrors 131 FPS / 102 low
DX12 beta / 125% scale / high mirrors 108 FPS / 81 low

Bench: i9-13900K / RTX 4080 SUPER / 32 GB DDR5. Route: city centre loop plus 40 km highway. Mirror quality and scaling vary by row; all other settings fixed.

DX12 gave a small average advantage and a better 1% low on this bench. It is not a universal win; the beta can introduce first-load shader stutter and a different set of driver interactions. Test the same route twice before deciding.

Wheel FFB: set the path, then the gain

Force feedback is a chain: wheel firmware → manufacturer software → game controller API → in-game gain → physics. A weak feeling can start in any link. Work from the outside in.

  1. Load the wheel’s own control panel and confirm the device is in PC mode, not console mode.
  2. Calibrate the full steering range, then set the same range in ETS2.
  3. Start the game with a clean controller profile.
  4. Set in-game FFB gain to 60–70%. Raise it only after a clean lap without clipping.
  5. Add road-surface and engine-vibration effects sparingly. They are garnish, not steering information.

If the wheel is clipping, more gain does not add detail. It removes the detail you already had.

GamePathHub / controls desk

ETS2 high-refresh & wheel checklist

0 / 8 complete

Test DX12 separately

If you opt into the 1.58 DX12 beta, back up the config and run the same route. If the first drive is stuttery, quit, relaunch, and repeat before judging. First-run shader work is not a permanent performance verdict. If you see a new crash, return to DX11 and report the route with your GPU driver version.

The honest summary

A stable 120 FPS in ETS2 is a balanced configuration, not a single cvar. Set the display correctly, keep mirrors sane, cap below the refresh rate, and configure the wheel in the right order. The frame-time chart and the steering feel should both be repeatable before you call it tuned.

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

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

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

Euro Truck Simulator 2: bench questions

3 answers
Is DX12 faster than DX11 in ETS2?
On the 1.58 beta bench, DX12 improved high-refresh consistency on an RTX 4080 but introduced longer first-load shader work. It is worth testing, not automatically enabling. Keep a DX11 fallback and compare the same route.
Can ETS2 hit 120 FPS at 1440p?
Yes, with a modern mid-range GPU and sensible mirror and shadow settings. The frame rate is usually CPU and mirror-render limited in cities, so a faster GPU alone may not hold 120 in dense areas.
Why does my wheel force feedback feel light after an update?
Check the wheel software profile, the in-game FFB gain, and whether the game reset your controller configuration. Do not immediately max the gain; clipping force feedback feels worse and hides the road surface.
Filed under

Controls & Peripherals

Patch tested: 1.58 — DX12 beta and wheel API update

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.