TerraGearTerraGear ran its own mailing lists for most of the 2000s. They are gone, and scenery discussion moved to FlightGear’s channels. This page says which channel suits which question, and what became of the old ones, because their addresses are still printed in documentation people find.
Where to ask now
| Channel | Best for |
|---|---|
| FlightGear forum | “How do I…”, “has anyone built scenery for…”, showing what you made. No account needed to read. The scenery boards are where most TerraGear conversation happens. |
| FlightGear mailing lists | Development discussion, design questions, anything aimed at the people who work on the tools. |
| GitLab issues | A defect with steps to reproduce. Needs a GitLab account. |
| FlightGear wiki | Corrections to documentation, including where it disagrees with itself. |
The tracker moved. FlightGear’s bug tracking ran on
SourceForge for years and has moved to GitLab; the SourceForge tracker is now
read-only and says so. Note also that issues are turned off on the individual
repositories,
gitlab.com/flightgear/terragear/-/issues answers 404, so reports go to the group tracker linked above. Checked 23 August 2026.
What happened to the TerraGear lists
The original site ran two lists, hosted by flightgear.org:
- TerraGear-Devel; announced on 29 November 2000, originally
at
[email protected], later moved with the rest of the project’s infrastructure. - TerraGear-CVSLogs; commit notifications, back when the
source lived in CVS. The site also published a generated
/CVSlogs/tree of per-directory commit histories.
Neither list takes mail now, and the archives are not where the old links point. Commit notification is a GitLab feature these days, and development discussion happens on the FlightGear lists rather than a TerraGear-specific one.
Before you ask
Three things make a scenery question answerable, and this site exists partly because they are hard to establish:
- Which branch you built.
next,scenery/ws2.0andmasterare years apart; see Downloads. - The exact output. Not “it crashed” but the last twenty lines and the exit status. Several TerraGear failures produce partial output and a non-zero exit without an obvious error; Common errors and fixes has the ones met here.
- Your region and data sources. Behaviour differs enormously between a coastal square with a major airport and empty countryside.