How do I improve FPS in Train Simulator Classic?
To improve low FPS in Train Simulator Classic, start by lowering shadows, anti-aliasing, view distance and scenery density; use the 64-bit executable; run the game from an SSD; and test a repeatable scenario. Busy routes are often CPU-limited, so reducing resolution alone may produce little or no gain.
Which settings improve Train Simulator Classic FPS most?
Shadow quality, anti-aliasing and scenery complexity usually produce the most useful gains. Setting names vary slightly between builds, but we recommend adjusting them in this order:
- Lower shadow quality. Shadows are expensive around large stations, dense scenery and multiple trains. Reduce them one level at a time before disabling them completely.
- Reduce anti-aliasing. Modes that include supersampling can consume substantial GPU performance. Choose a lighter anti-aliasing mode before lowering the display resolution.
- Reduce scenery density and view distance. This cuts the number of objects the engine must draw. It is particularly effective on urban routes, though it increases visible object pop-in.
- Reduce dynamic lighting and advanced effects. These can be costly during rain, darkness and illuminated station scenes. Disabling dynamic lighting may significantly change night-time visuals, so treat it as a last-resort setting.
- Lower water and weather effects. The benefit depends heavily on the route and scenario.
- Lower texture quality only when memory is tight. It can help with limited graphics memory, but usually does little for a CPU bottleneck and noticeably reduces image quality.
Keep the monitor's native resolution while testing unless the graphics card is clearly the limiting component. A large FPS increase after reducing resolution indicates a GPU bottleneck; little or no change usually points towards the CPU, route or scenario.
Is low FPS caused by the CPU, GPU or asset loading?
The location and timing of the slowdown usually reveal the bottleneck more clearly than the average frame rate.
| Symptom | Likely cause | Best response |
|---|---|---|
| FPS drops at large stations or near many AI trains | Main simulation thread or scenery load | Lower shadows and scenery density; compare with a lighter scenario |
| Reducing resolution or anti-aliasing gives a large gain | GPU limitation | Use lighter anti-aliasing, effects or resolution settings |
| Brief freezes occur at the same points along a route | Route-tile and asset loading | Use an SSD and stop background storage activity |
| Only one route, locomotive or scenario performs badly | Content complexity or an add-on problem | Test another scenario and isolate recently installed content |
| Performance falls after several minutes on a laptop | Power saving or thermal throttling | Connect mains power, select the high-performance GPU and check cooling |
Train Simulator Classic relies heavily on work that cannot be spread evenly across every CPU core. A modern graphics card can therefore sit below full utilisation while one demanding route still runs poorly. Our practical CPU, GPU, memory and storage guidance explains which hardware characteristics matter.
What is the best optimisation order?
A controlled test prevents route changes, weather and AI traffic from being mistaken for graphics-setting improvements.
- Create a repeatable baseline. Load the same scenario, use the same camera and observe the same demanding station or route section. Do not compare a quiet rural Quick Drive with a busy timetable scenario.
- Launch the 64-bit version. It can address more memory and is preferable for large routes. It mainly reduces memory pressure and related instability; it does not guarantee higher FPS. Use the legacy executable only when an older add-on explicitly requires it.
- Check graphics selection and power mode. On systems with integrated and dedicated graphics, assign Train Simulator Classic to the high-performance GPU. Connect laptops to mains power and disable battery-saving modes.
- Remove forced graphics overrides. Driver-level supersampling, sharpening or unusual VSync settings can conflict with the game's own options. Return them to application-controlled values while diagnosing performance.
- Lower settings in the useful order. Test shadows first, followed by anti-aliasing, scenery density, view distance and effects. Change one setting at a time.
- Move the installation to an SSD. This improves route loading and tile-streaming pauses, although it will not cure a CPU-limited frame rate at a busy station.
- Close background recording and heavy storage tasks. Video capture, overlays, downloads and security scans can worsen frame pacing even when the average FPS appears acceptable.
- Test standard and custom content separately. Detailed rolling stock, long consists, complex scripts and oversized scenery assets can make one scenario much slower than the rest of the simulator.
If a performance regression began immediately after installing custom content, isolate the newest route or train and reinstall it correctly. Our explanation of Train Simulator Classic add-on installation methods covers the usual package and manual-installation pitfalls.
Why does Train Simulator Classic stutter on a fast PC?
Stuttering usually comes from uneven frame delivery, asset loading or scenario scripting rather than a lack of headline hardware performance.
- Keep the simulator and heavily used route assets on an SSD.
- Leave the Windows page file enabled; disabling it can make memory pressure worse.
- Expect the first run after clearing the cache to load more slowly while asset data is rebuilt.
- Compare the same route with a simpler scenario. Numerous AI services and heavily scripted trains add simulation work that graphics settings cannot remove.
- Use 64-bit mode for memory-heavy routes, but do not expect it to turn the older engine into a fully multi-core application.
If stuttering develops into desktop exits, freezes or memory errors, use our step-by-step crash diagnosis process rather than continuing to reduce graphics settings.
Should I clear the cache to fix low FPS?
No—clearing the Train Simulator Classic cache is not a routine FPS optimisation. Use it after changing assets or providers, or when scenery and rolling stock fail to appear correctly; the following load may stutter more while cached asset information is rebuilt.
The game client's file-verification function is also a repair tool, not a performance tweak. Use it after a failed update or suspected core-file corruption, bearing in mind that it may replace deliberately modified core files.
What frame rate should I target?
A stable frame rate is more useful than a high rural-route peak followed by severe station dips. Choose a limit your PC can sustain through demanding sections—commonly 30, 40 or 60 FPS—and apply it through the graphics driver if needed.
If VSync causes abrupt drops when the simulator cannot hold the monitor's refresh rate, test with VSync disabled and use a separate frame-rate cap. Judge the result by smooth frame delivery and control response, not the FPS number alone.