maj00r 797e2e70a7 feat(sceneries): a release clears the .sbt files once, and a scenery's menu deletes its own
The simulator makes a scenery's .sbt on its first load and never checks it
against the text again, so an older simulator's file, or one made before a
scenery update, keeps showing the old terrain.

- CleanupGeneration, raised by a release, clears the .sbt files once per
  installation on the first start, ahead of the scenery list. A file goes only
  while its scenery's terrain files (*_ter.scm) are all there and no terrain
  directive brings terrain from elsewhere; an .sbt standing in for missing
  terrain stays, and the log says what is missing. Which cleanup each
  installation had is kept in sbt-cleanup.txt in the user's folder.
- "Delete SBT" in the scenery list's menu does the same for one scenery,
  asking first and refusing where nothing could make the file again.
- The .sbt is among the files a scenery is watched by, so one made or removed
  reaches the list without a reload.
2026-11-17 02:15:45 +01:00
2026-11-07 06:27:16 +01:00
2026-11-07 06:27:16 +01:00
2025-12-23 08:47:36 +01:00
2025-12-23 08:47:36 +01:00
2026-08-30 22:29:45 +02:00

StarterNG

Launcher for the MaSzyna train simulator, written in C# with Avalonia.

Building a native (NativeAOT) build

The project publishes as a self-contained NativeAOT binary — no .NET runtime is needed on the target machine. The commands below are the same ones CI runs, see .github/workflows/dotnet.yml.

Requirements:

  • .NET SDK 9
  • Linux: a native toolchain and zlib headers — sudo apt install clang zlib1g-dev (Debian/Ubuntu) or sudo dnf install clang zlib-devel (Fedora)
  • Windows: the Visual Studio C++ build tools (Desktop development with C++)

Restore for the target runtime first, then publish:

dotnet restore StarterNG/StarterNG.csproj -r linux-x64

dotnet publish StarterNG/StarterNG.csproj \
    -c Release -r linux-x64 --self-contained true --no-restore \
    -p:PublishAot=true -p:PublishTrimmed=true \
    -o publish/linux-x64

For a Windows build swap both linux-x64 occurrences for win-x64 (and the line continuations for PowerShell backticks). NativeAOT does not cross-compile, so the Windows package has to be built on Windows and the Linux one on Linux — that is why CI uses a windows-2022 and an ubuntu-22.04 runner.

The output directory is the whole distributable: the Starter executable, the Skia/HarfBuzz native libraries and startercfg/ with the translations and the default key bindings. The .dbg (or .pdb) file next to it is debug symbols and can be dropped from a release. Trim/AOT analysis warnings during the publish are expected and do not fail the build.

CI builds both runtimes on every push and pull request to main and staging, and on manual dispatch. Pushes additionally replace a rolling pre-release with the packaged artifacts — tagged latest for main and staging for staging.

Development build

dotnet build StarterNG/StarterNG.csproj
Description
No description provided
Readme MPL-2.0 4.5 MiB
Languages
C# 100%