Transport Fever 3 Steam Deck: Compatibility and Settings

Transport Fever 3 is unverified on Steam Deck: bSteamDeck false, resolved_category 0, zero user reports. What the Deck can run, and what to change.

Last Updated: 2026-09-30

Transport Fever 3 Steam Deck: Compatibility, Settings, and an Honest Verdict

Quick answer: Transport Fever 3 is neither verified nor rated on Steam Deck. The live store page carries bSteamDeck=false and bSteamOS=false in its data-hwinfo block and resolved_category=0 plus steamos_resolved_category=0 in its data-hardwarecompatibility block, which in Valve's own four-tier vocabulary means the game has not been checked at all. Worse for anyone hunting for proof: all four compatibility arrays are empty, so not one Deck owner has filed a report. There is no benchmark to quote. What you can do instead is compare the hardware honestly, and that comparison is where this page stops being ambiguous.

  • It installs, and it is controller-complete. TF3 ships a native Linux build, and the store reports controller_support: full plus Full controller support, DualShock and DualSense categories.
  • The silicon sits well under the official minimum. Valve's spec sheet lists a 4c/8t Zen 2 CPU and 8 RDNA 2 compute units at 1.6 TFLOPS on a 4-15 W envelope, with 16 GB of LPDDR5 shared with the GPU. The minimum asks for a GTX 1060, RX 480 or Arc A380 with 4 GB of dedicated VRAM.
  • The ceiling is a CPU problem long before it is a GPU problem. The publisher's own diagnostic splits into two branches, and a simulation that models every inhabitant lands in the second one.
  • Save transfer between PC and Deck is unresolved. No Steam Cloud tag appears on the store page, and the only official save-portability commitment covers PC-to-console, not PC-to-handheld.

Wide aerial view of a Transport Fever 3 town with roads rail line and industry
Wide aerial view of a Transport Fever 3 town with roads rail line and industry

What the Store Page Actually Says About the Deck

Four flags decide everything a buyer needs to know, and all four point the same way.

Store page field Live value on 3493540 What it means for a Deck buyer
bSteamDeck false Not flagged as Deck-compatible
bSteamOS false Not flagged as validated on SteamOS generally
resolved_category 0 No Deck compatibility rating assigned
steamos_resolved_category 0 No SteamOS compatibility rating assigned
resolved_items plus three sibling arrays empty Zero users have submitted any report

Valve's own scale has four tiers: Verified, Playable, Unsupported, and Unknown, which the Deck Verified documentation defines as "We haven't checked this game for compatibility yet." A resolved_category of 0 with empty item arrays is the Unknown end of that scale, not the Unsupported end. Nobody has measured TF3 on Deck hardware and concluded it fails. Nobody has measured it at all.

The empty report arrays are the real story here

A single community report would give you a data point to argue with. The empty arrays mean the honest answer to "does it run on the Deck" is unknown, and any specific handheld frame rate attributed to TF3 two days after launch is someone's unsourced guess. A search does turn up competitor guide pages publishing confident handheld frame rates for this game; none of them can point at a Valve record, a ProtonDB report, or an official test either.

ProtonDB is not the place to look, and its silence is expected. TF3 is not a Proton-dependent Windows title: the store flags linux: true and publishes a native Linux requirement block. The ProtonDB summaries endpoint for appid 3493540 returns HTTP 404, which for a native build means no reports yet, not does not work.

Official source: Transport Fever 3 on Steam

Deck Hardware Against the Official Minimum

Component Steam Deck (Valve spec sheet) TF3 PC minimum TF3 PC recommended
CPU AMD Zen 2, 4 cores / 8 threads, 2.4-3.5 GHz Core i5-8400 or Ryzen 5 2600X, AVX2 required Core i7-13700K or Ryzen 7 7800X3D
GPU 8 RDNA 2 CUs at 1.6 GHz, 1.6 TFLOPS FP32 GTX 1060 / RX 480 / Arc A380 RTX 3070 / RX 6800 / Arc A770
Memory 16 GB LPDDR5, shared with the GPU 8 GB system RAM 16 GB system RAM
Graphics memory None dedicated 4 GB VRAM 8 GB VRAM
APU power 4-15 W Not stated Not stated
Display 1280 x 800, up to 90 Hz on the OLED model Not stated Not stated
Storage 512 GB or 1 TB NVMe SSD, plus microSD 90 GB, SSD required 90 GB, SSD required

Three gaps matter most. The core count is four against a six-core minimum CPU, and the developer has been explicit that the game uses multiple cores while acknowledging that "one core always acts as the governor over the others in order to preserve proper synchronisation" and that this function "cannot be spread over multiple cores". Second, the minimum names a discrete card with 4 GB of VRAM; the Deck has none of its own, so texture and geometry work compete with the simulation for the same 16 GB. Third, 90 GB of storage on a 512 GB drive is a purchase decision, softened by the microSD slot.

A current laptop integrated GPU such as the Radeon 780M sits in the same class as the Deck's RDNA 2 part: shared memory, no dedicated VRAM, a power envelope nearer the Deck's 15 W ceiling than a GTX 1060. That is why the minimum spec's GTX 1060 line should not be read as roughly handheld-class.

The Settings That Buy Frames, and What They Cost

Resolution is the one setting where the Deck and the game's own guidance line up exactly. Valve's Deck Verified criteria require a title to support the default Deck resolution of 1280x800 or 1280x720, and the game's guidance notes that dropping from 3840x2160 to 1920x1080 "can significantly reduce GPU load". On a 1280x800 panel, render at the panel's native resolution with the scale at 100 percent and never go above it.

Change Direction What you give up
Render at 1280x800, scale 100 percent Strongly recommended Nothing; this is the panel's native resolution
Shadow quality low or off Large GPU saving Contact shadows under vehicles and buildings soften or vanish
Reflections and water quality down Large GPU saving on coastal maps Harbors lose the mirror surface that makes them readable
Level of detail down Moderate GPU saving Distant buildings and vehicles flatten out as you zoom out
Texture quality down Frees shared memory Surface detail softens; the win matters more than on a PC
Cap the session at 30 FPS in the OS overlay Battery and frame-time stability You give up the 60 Hz half of the panel's refresh

The frame rate cap is the one row the game cannot give you, because it lives in SteamOS rather than in TF3. The dynamic-weather toggle is in-game, and a launch-day player report recommends pausing it; community-observed, and it may change with patches.

Use the publisher's two tests before you touch anything

Pause the simulation. If the frame rate is still low while paused, the GPU is the limiter and resolution, anti-aliasing, shadow quality, texture quality and level of detail are all fair game. If it is only low while unpaused, the simulation is the limit, and the publisher states plainly that "reducing graphics settings usually has little effect on this type of CPU limitation". On a Deck you land in the second branch sooner than you expect. The same page names the CPU-side aggravators: many cities, dense transport networks, large numbers of vehicles, complex road traffic, many industries and cargo connections, and large or demanding mods.

Where the Deck Runs Out of Steam

Desktop launch-day reports put the boundary in a useful place. One player on a Ryzen 7 7800X3D with an RX 7900 XT and 32 GB of RAM reported 55-75 FPS on the High preset at game start, then 35-45 FPS with heavy stutter by 1902, with two towns of roughly 500 inhabitants, four trains and about 50 wagons on the map. The overlay showed GPU load at 45-70 percent while the CPU never exceeded 25 percent, and the lowest preset made no perceptible difference. Community-observed; it may change with patches. The combination is the important part: the map was neither GPU-starved nor fixed by shedding graphics work.

A 7800X3D is a far stronger CPU than the Deck's four Zen 2 cores, so the Deck hits the same wall earlier. The developer has conceded the shape of it: city populations grow without limit, making "an eventual overload in the amount of citizens being processed by the game inevitable", and the studio does "not prevent players from growing beyond the capability of their hardware".

The most-repeated launch-day remedy, from several players independently, is turning grass off: "Just turn off grass and everything runs smooth as butter." Community-observed; it may change with patches. The Known Issues page lists no grass option, so treat it as a strong signal rather than a documented lever. The structural answer on a handheld is smaller maps and fewer compounding towns.

Symptom on Deck Limiter Move that actually helps
Low frame rate while paused GPU Native resolution, shadows and reflections down
Low frame rate only while running CPU simulation Fewer towns, shorter lines, fewer vehicles
2x and 4x speed change nothing CPU simulation Same as above; graphics settings will not move it
Frame rate degrades year over year Population growth Cap town count, retire redundant lines
Texture stutter while panning Shared memory pressure Texture quality down, lower zoom range

Saves Between PC and Deck

Not yet confirmed. The store page carries no Steam Cloud tag anywhere and the appdetails payload has no cloud field, so Valve has not advertised cloud saves for this title. The game's only documented save-portability problem is a different one: PC saves uploaded to the mod hub are not available on PlayStation or Xbox, and the publisher's sole post-launch commitment is that "compatibility will be added post-launch" for that console path. It does not mention handhelds.

PC and Deck both install the same Steam build, so no save format problem exists between them; the issue is file transfer, not conversion. All three official known issues on the launch list are console-side, and none is a Linux or SteamOS bug. If you need to move a campaign, treat it as a file copy through the microSD card or a synced folder, and back up first. The exact save path is something this page cannot confirm from official sources, so verify it on your own machine rather than trusting a forum path.

Frequently Asked Questions

Is Transport Fever 3 verified for the Steam Deck?

No, and at launch it is not even rated. The store page reports bSteamDeck=false and resolved_category=0, which in Valve's four-tier scale is Unknown, defined as "We haven't checked this game for compatibility yet". It is not an Unsupported rating, which would mean Valve tested it and it failed.

Does it even launch on Steam Deck?

Nobody has confirmed that, which is the honest answer. The game ships a native Linux build with published Ubuntu 24.04 requirements, and the publisher's Linux startup guidance is a generic checklist: verify game files, install updates, update drivers, disable mods, and start from a terminal to read the error output. The publisher also warns that Transport Fever 2 era fixes, including hand-copying libstdc++ libraries, "should not be used unless specifically instructed for Transport Fever 3". A thread on the game's Reddit community claims it runs and is playable capped at 30 FPS on default low settings; that page could not be opened for verification, so treat it as unverified community-observed data that may change with patches.

What settings should I change first on the Deck?

Render at the panel's native 1280x800 with the scale at 100 percent, then drop shadows, reflections and level of detail. Then run the pause test from the known-issues page: a low frame rate while paused is a GPU problem, and a low frame rate only while running means no graphics slider will help you.

Are my saves shared between my PC and my Deck?

Unconfirmed, and probably not automatic. No Steam Cloud tag is present on the store page, and the only official save-portability commitment covers PC-to-console transfers. Since both machines run the same build, manual file transfer should work, but check the save location yourself before relying on it.

Is the Steam Deck worse than the PS5 or Xbox version?

A different failure mode. The console versions have three official known issues, including a controller softlock on empty construction menus, and the Deck has a hardware shortfall instead. A handheld is the weaker machine for a CPU-bound simulation; a console is a fixed-spec target the developers tuned against. The console release breakdown covers that side, and the system requirements breakdown has the full spec tables.

  • System Requirements - the full minimum, recommended, Mac and Linux spec tables behind every comparison here.
  • Performance and Lag Fix - the desktop version of the CPU-versus-GPU split and the settings order that matters.
  • Console PS5 and Xbox Release - the other branch of the can-I-play-it decision, including the official save gap.
  • Which Edition to Buy - the price ladder across the three tiers, what Deluxe and Collector's actually add, and the TF2 loyalty discount.

More Transport Fever 3 Guides