Run Microsoft Train Simulator in 4K using the correct launch switch and DPI settings, with Open Rails and black-screen fixes when the old engine fails.
Microsoft Train Simulator can request 3840 × 2160 with its -vm:3840,2160,32 launch switch, but the original 2001 engine does not handle 4K reliably. Try the switch first, apply Windows high-DPI compatibility settings, and use Open Rails if the menus, cab views or stability remain poor.
How do I force MSTS to run at 3840 × 2160?
Use MSTS's video-mode switch if 3840 × 2160 is absent from its Display options. If the resolution is already listed, select it there and restart the simulator before modifying a shortcut.
- Exit Microsoft Train Simulator. Do not change its video mode while the simulator or launcher is open.
- Locate
train.exe. It is inside your Microsoft Train Simulator installation folder. Create a new desktop shortcut to this executable so the original shortcut remains available for recovery. - Open the shortcut's Properties. In the Target box, append
-vm:3840,2160,32after the closing quotation mark. - Check the complete target. It should resemble
"[MSTS installation folder]\train.exe" -vm:3840,2160,32. The space before the switch matters, and the switch must not be placed inside the quotation marks. - Set Windows to its native 4K mode. Confirm that the intended monitor is running at 3840 × 2160 and is selected as the primary display.
- Test a default route first. This separates a display problem from a fault in an add-on route, cab or activity.
The final 32 means 32-bit colour; it is not a refresh-rate setting. The old renderer may reject the mode even when Windows and the graphics driver support it.
Which Windows compatibility settings help at 4K?
Let the application control high-DPI scaling so Windows does not substitute a scaled virtual resolution. Right-click train.exe, open Properties and Compatibility, select Change high DPI settings, then enable the override with scaling performed by Application.
If full-screen MSTS opens as a black window, flickers or behaves badly after switching applications, test Disable fullscreen optimisations. Avoid enabling 640 × 480 mode or reduced-colour mode, because either can override the requested 4K settings. Our MSTS compatibility guidance for modern Windows covers the other launch and display settings that may be needed.
Change one compatibility option at a time. A mistake we see constantly is enabling every legacy setting together, making it impossible to identify which one fixed—or caused—the problem.
Why are the menus and cab view wrong at 4K?
Native 4K increases the resolution of the rendered 3D scene, but it does not recreate MSTS's fixed-size interface and cab artwork. Text and controls may therefore become extremely small, while older 2D cabs designed around a 4:3 display can appear cropped, zoomed or stretched on a 16:9 screen.
Driver-forced anti-aliasing can also become unnecessarily expensive at 4K. Disable that first if performance falls sharply; reducing the simulator's view distance or shadow settings is usually preferable to abandoning the native resolution immediately.
Should I use Open Rails for MSTS in 4K?
Open Rails is usually the better choice when sharp 4K output matters more than reproducing the original MSTS engine exactly. It can use compatible Microsoft Train Simulator routes, rolling stock and activities while providing a renderer designed for newer Windows versions and modern display modes.
Install it separately, point it towards your MSTS content, and choose 3840 × 2160 in its video settings. Our Open Rails installation and configuration guide explains that process without requiring you to remove the original simulator.
Keep MSTS installed because Open Rails is an alternative engine, not a patch for train.exe. Most content transfers well, but specialised activities, signalling logic, physics and cab behaviour may not match the original engine perfectly.
| Display method | Choose it when | Main compromise |
|---|---|---|
| Original MSTS at 3840 × 2160 | You need the original engine and the mode works reliably | Tiny interface, legacy cab scaling and possible crashes |
| Original MSTS at 1920 × 1080, upscaled | Stability and readable controls matter most | The 3D image is not rendered at true 4K |
| Open Rails at 3840 × 2160 | You want the clearest result on modern hardware | Some content may behave differently from MSTS |
What if MSTS shows a black screen or will not restart?
Remove the -vm:3840,2160,32 switch first; that immediately tells you whether the requested display mode caused the failure. Then test 2560 × 1440 or 1920 × 1080 using the same syntax.
- If a lower resolution works, the legacy DirectX renderer or driver is rejecting 4K. Use the lower mode with display scaling, or move that content to Open Rails.
- If multiple displays are connected, make the 4K screen primary and temporarily disable mirrored output. Mirroring can restrict applications to modes shared by both displays.
- If MSTS saved an unusable display configuration, follow our registry recovery procedure for MSTS rather than deleting unrelated registry entries.
- If it still fails without the 4K switch, work through the MSTS crash troubleshooting checks; the underlying fault is then unlikely to be resolution alone.