Any terrain directive kept the scenery's .sbt, as if it brought the terrain
from elsewhere. The directive names either .sbt files, which nothing makes
again, or terrain files (.txtf) with their binary copies (.btf). A scenery
with the terrain files has no use for its own .sbt: the simulator never
writes one for it, and an old one keeps the terrain files from being used.
- An .sbt named by the directive still keeps the scenery's own.
- A .txtf, or its .btf, on disk lets the scenery's .sbt go; with neither,
the .sbt stays and the missing .txtf is given as the reason.
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.