Main menu and settings
Main menu
Section titled “Main menu”Without arguments the simulator opens on a title screen: wordmark over the backdrop, and five
verbs — Drive, Multiplayer, Mods, Settings, Quit. Multiplayer joins a
server: an address page, then the server’s lobby (see Multiplayer). Drive begins with the run, and
everything else follows from it. The list offers two kinds of run: a scenario, and every
playable service of an operating day — a whole 24-hour timetable that starts over at
midnight (see Timetable runs below). Both stand under the route they take, and picking
one picks that route with them: a scenario names the line it plays on, a service the line of
its plan, so the route is derived rather than asked for. Only what the run leaves open is a
step of its own — the line where the run names none (which is what the free run is), the
vehicle where the run does not bring one, and for a service the date and the weather
before it starts. The steps stand in a numbered rail across the top with what was picked under
each, so a prepared scenario is one question and the free run is three. Beside the list a
detail pane reads the highlighted entry out of the loaded content: length, permitted speed and
signals of a line; mass, running-gear limit, drive and brake of a vehicle; start time,
timetable and events of a scenario; train number, departure and arrival of a service.
↑/↓ or the mouse select, Enter or a left click
confirms, ←/→ dial a setting, Esc goes one step back and leaves at the title screen; F9
opens the mod manager in-game. A .crails mod package dropped onto the window is installed and
the menu turns to Mods with the outcome; dropped during a run it waits for the menu
(Distribution). A controller works the menu the same way: the D-pad is the
arrow keys, A confirms, B goes back. The wheel scrolls the list one row a notch, and a
scroll bar beside it shows how long the list is — its thumb can be dragged. The sliders on the
settings page (view distance, field of view, volume, frame limit, look speed) can be dragged
or clicked as well as dialled; a dragged value lands on the same steps ←/→ walk.
The menu talks to screen readers through AccessKit: every row is announced with its role
(list item, switch, heading, button), label, value and help line, and the highlighted row
holds the input focus, so the reader follows the cursor. The sliders are Bevy’s own slider
widget and report their number, range and step. On Linux this goes through AT-SPI (Bevy’s
accesskit_unix feature); Windows needs nothing extra. Any run flag (--line, --loco, --scenario, --day,
--frames, --screenshot, …) skips the menu entirely, so the invocations above stay
non-interactive — --menu puts it back in front, optionally on a named page
(--menu settings, also root, run, line, loco, setup, mods, server, lobby,
and the settings tabs graphics, display, audio, controls), which is the only way to
photograph the menu itself.
The picture behind the menu lives in crates/app/images/ and is compiled into the binary.
It is a photograph under CC BY 2.0 — source, author and licence are in the README there, and
the menu’s footer credits it. It is cropped to fill whatever shape the window has and drifts
very slowly across it.
Settings
Section titled “Settings”The Settings page of the main menu is split into five tabs — General (language, HUD,
look speed, reset), Graphics (scenery, light and shadow, sky, image quality),
Display (window, vsync, frame cap, field of view), Audio and Controls (the key and
controller bindings). Q/E or the controller’s shoulder buttons switch tabs, a click on a
tab opens it, and Esc on any tab goes back to the title screen. It writes a TOML file into the operating system’s
settings directory for the current user (%LOCALAPPDATA%\dev.vanlueck.connected-rails\settings.toml
on Windows, ~/.config/dev.vanlueck.connected-rails/settings.toml on Linux). It is Bevy’s own
bevy::settings, so the file is plain text and can be edited by hand; an unknown or malformed
key falls back to the built-in default instead of taking the program down.
Every setting applies the moment it is changed — none of them waits for a restart or for the next run. View distance moves the streamer’s load radius while tiles are in the air, bloom is added to and taken off the live camera, and the rest is re-read where it is used.
Esc during a run raises the pause overlay — the world stands still under it — with
Resume, Settings, Back to the main menu and Quit. Its settings page is the
same one, minus the language (not a driving decision) and the reset (too blunt to have under
the cursor while a train is standing on a gradient); everything on it takes effect while you
watch. Esc on the overlay resumes; going back to the main menu ends the run and takes the
built world down with it, so the next one starts from an empty world.
| Section | Setting | Effect |
|---|---|---|
[graphics] |
view_distance |
How far terrain is built and drawn [m], 1000 … 12000. The biggest single cost. |
fov |
Vertical field of view of the cab camera [°], 60 … 120. Applies immediately, also while driving. | |
shadows |
Shadow maps of the sun. Off takes the two contact/headlight rows with it. | |
bloom |
Glow around lamps and signals after dark. | |
shadow_quality |
Edge length of the sun’s shadow map and how far its cascades reach: Low 1024 texels over 600 m, Medium 2048 over 900 m, High 4096 over 1400 m. A step buys both. |
|
contact_shadows |
A short screen-space shadow where an object meets what it stands on — a sleeper end on the ballast, the foot of a signal post — filling in what the cascades are too coarse to resolve. | |
headlight_shadows |
The player’s own headlight casts shadows down the track after dark. One extra shadow pass while the beam is lit, none by day, and only for your own train. | |
ambient_occlusion |
Screen-space occlusion of the sky’s light — the shade under a canopy, in a cutting, beneath a coach, which the sky’s environment map does not know it should be casting. It cannot run beside MSAA, so SMAA takes MSAA’s place while it is on. | |
ao_quality |
How many directions each pixel is measured in: Low, Medium or High. |
|
volumetric_clouds |
Marches the cloud deck as a volume — billows, a lit interior, a silver lining. Off draws the same clouds as one lit sheet at the same resolution, for about a twentieth of the cost. | |
mist |
Ground mist as a volume, with the sun’s shafts through it. | |
mist_quality |
Steps of the raymarch through it: Low 16, Medium 32, High 64. |
|
texture_quality |
Size and filtering of the generated ground textures: Low 128², Medium 256², High 512². |
|
anti_aliasing |
How the edges are smoothed: Off, Fxaa, Smaa or Msaa. MSAA cannot run beside the ambient occlusion, so while that is on SMAA takes its place and the page says so. |
|
aa_quality |
How hard that works: Low, Medium or High — 2×/4×/8× for MSAA, the preset for the other two. |
|
upscaling |
Temporal upscaling of the picture: Off, Fsr (any GPU) or Dlss (an NVIDIA RTX card on Vulkan — offered only where it can run, and only in a simulator built with the dlss cargo feature, which the released Windows and Linux builds are). The page offers a technique only where it can run. An upscaler smooths the edges itself, so it takes MSAA off the camera while it is on. |
|
upscaling_quality |
How much of the picture is really drawn: Low half the edge in each axis, Medium 59 %, High two thirds. |
|
window |
Windowed, Borderless over the whole monitor, or exclusive Fullscreen. |
|
vsync |
Caps the frame rate at the monitor’s. | |
max_fps |
Frames a second the simulator holds itself to, 30 … 240; the top step (250) is no cap at all. | |
[audio] |
master |
Linear master volume, 0 … 1. |
[gameplay] |
language |
en, de, or empty for the system’s. |
hud |
How much of the display is drawn: Full, Reduced or Off (F7 walks the three). |
|
look_speed |
Factor on the mouse look speed, 0.2 … 3.0. | |
[controls] |
binds |
The bindings, one line per rebound row — throttle-up KeyW DPadUp for a button, lever-brake-valve RightTrigger2 for a lever, - for nothing. Only what differs from the default is written, so a new default reaches everyone who never touched that row. |
TRAINSIM_LANG stays the outermost override: where it is set, the stored language is
ignored, so scripted and CI runs are not steered by whatever was last picked in the menu.