Transport Fever 3 DLSS Frame Generation

The Transport Fever 3 DLSS option covered here is WhiteTortoise's unofficial DLSS Frame Generation mod. Its documented setup requires Windows, the Steam game, an NVIDIA RTX 40 or 50 GPU, hardware-accelerated GPU scheduling, Resolution Scale at 100%, and MSAA enabled. It inserts generated frames to improve visible motion; it does not make a large transport simulation or station construction run faster.

Start with the author's project and requirements. This is a separate renderer mod, not an official in-game DLSS setting or a normal Mod Hub subscription. The requirements below describe the author's current implementation; they are not a claim about every DLSS feature or future game update. We have not independently benchmarked or security-tested its executable.

Check whether your PC fits this mod

The author documents the following conditions together. Meeting the GPU requirement alone is insufficient if a required Windows or in-game setting remains disabled.

The current instructions do not establish support for macOS, Linux, consoles, GOG or Epic installations. A compatible graphics card in a different environment does not verify that the installer and renderer hooks work there. Use the general performance guide if your system falls outside these requirements.

The author says unsupported Resolution Scale/MSAA combinations leave Frame Generation off. Do not apply a generic low-FPS checklist that lowers Resolution Scale and then assume this particular mod is still active. Choose between testing its required configuration and testing lower rendering resolution as separate comparisons.

Separate generated FPS from simulation speed

Frame Generation creates an additional displayed image between rendered frames. The author describes a renderer integration that supplies scene depth, camera-based motion vectors and the scene before the interface is drawn. It is intended to improve motion presentation while keeping interface elements readable.

That work also uses GPU time. A higher displayed FPS count does not mean the game produces the same number of new simulation steps or responds to input at that displayed rate. NVIDIA Reflex is included to help control latency, but the author's detailed notes say input still responds at the real rendered frame rate. Do not read a short “no input lag” download description as a guarantee of zero latency.

Before considering the mod, pause your affected save and compare the view. If rendering is still slow while paused, graphics load is a useful starting point. If the paused view is smooth but 2× or 4× simulation speed barely advances the world faster, follow the CPU and simulation checks. The mod author specifically identifies station construction and editing as CPU-heavy operations that Frame Generation cannot fix.

The game's FPS readout helps identify the measurement being discussed. This illustration is not a benchmark of the DLSS mod or evidence that Frame Generation is active.

The game can show its own FPS counter through the experimental debugInfoShowFps setting. For this mod, the author recommends the Steam FPS counter and reports that the NVIDIA overlay shows N/A. Keep the counter, save, camera position and simulation state consistent when comparing the mod on and off.

Review the release before installing

Use the author's GitHub releases and read the notes for the version you intend to install. The inspected README lists changes through 0.2.0, including smoother camera movement for city names, station signs and vehicle icons. A later game update can change the rendering code and require a corresponding mod update.

The Nexus listing also offers the author's package. At this review it displayed “Some suspicious files” in its virus-scan status. That label does not identify whether a particular detection is a false positive, and this site has not assessed the binary. If your browser, antivirus or Windows blocks the file, stop and review the current file report and author response rather than bypassing the warning to follow this guide.

This mod's installer and runtime files belong in the game's installation, beside TransportFever3.exe. They do not follow the userdata/mods folder instructions used by ordinary script and vehicle packages. Do not copy its DLL into a Mod Hub download directory or expect it to appear as a selectable vehicle mod.

For a release you have reviewed and chosen to use, the author's installation workflow is:

1. Close Transport Fever 3 and obtain TF3-FrameGen-Setup.exe from the author's release.
2. Check the Windows scheduling setting under Settings → System → Display → Graphics → Change default graphics settings. Restart Windows if you change hardware-accelerated GPU scheduling.
3. Open the installer and check the Steam game directory it detects. If necessary, its Browse control selects the folder containing TransportFever3.exe.
4. Use Install. The author says the installer downloads NVIDIA Streamline runtime files from NVIDIA's release and checks their checksum.
5. Start the game, set Resolution Scale to 100% and enable MSAA, then load a map.
6. Compare the result in the same view, keeping the recovery steps below available if startup or rendering changes unexpectedly.

The author's runtime checksum step does not independently certify the installer itself. There is no need to download or redistribute NVIDIA runtime DLLs from a separate third-party mirror to follow this workflow.

Toggle Frame Generation and keep the comparison consistent

The default toggle is Ctrl + Alt + backslash. The mod creates tf3_framegen.ini beside the game executable; its start_enabled option controls whether Frame Generation begins enabled when a map loads. The hotkey option changes the key used with Ctrl + Alt.

The author says Frame Generation switches off in menus and loading screens, and pauses when the game window is not focused. Compare it while a map is loaded and the game has focus. Looking at a loading screen or an unfocused window can produce a misleading “not working” result.

Disable NVIDIA Smooth Motion for this game if you have enabled it; the author warns against running two frame generators together. The mod also turns VSync off while active, so visible tearing is a possible tradeoff. Judge camera movement, text, moving vehicles and input response as well as the displayed frame count.

The author's motion vectors describe camera movement, while moving objects rely on optical flow. Very fast objects may therefore show artifacts even if an ordinary camera pan looks acceptable. No universal FPS increase or artifact-free result is established across hardware, saves or graphics configurations.

Resolve a missing FPS increase or failed startup

The author identifies tf3_framegen.log as the mod log and framegen/sl.log as the NVIDIA Streamline log. The mod log's frame generation inputs found message indicates that it detected a map's required inputs. Its absence is a reason to recheck settings and compatibility; it is not by itself a diagnosis of every possible failure.

If you report a problem to the author, include the GPU, Windows and driver versions, game build, mod version, required settings and relevant log output. State whether the problem also occurs with this mod disabled. Those details are more useful than the displayed FPS number alone.

Disable or uninstall the mod

To disable the entire mod temporarily, create an empty file named tf3_framegen.disable in the game folder. To disable only Frame Generation, the author provides tf3_framegen.nofg instead. Removing the corresponding marker enables that function again; check which marker is present before troubleshooting a missing toggle response.

For a full uninstall, use the author's installer and choose Uninstall. Its documented removal targets are winhttp.dll, the framegen folder, tf3_framegen.ini and tf3_framegen.log from this mod. Confirm the folder and package before removing files manually, particularly if another tool also uses a proxy DLL there.

After disabling or uninstalling, repeat the same save and camera comparison. If the slowdown remains, continue with the performance diagnosis. If only the modded configuration fails after an update, keep it disabled until the author documents support for that game build.