Lars Toenning

It seems that the FG C172 was accidentially added to the database as an included model (overwrites the default "exclude" for -set.xml files). Hence it is used for matching in your case and the glider is shown. I will check with the swift database admin if we can change. The default C172 is now excluded for matching. The only other C172 model for FlightGear in the database, that is not exluded is "FG AI C172/C-FGFS". This model is located in $FGDATA/AI/Aircraft/c172.

Any other folder which contains user-flyable airplanes (in separate folders, one per plane). Note, that you need to add the folder containing the actual .ac/xml model, not the one with the -set.xml, as the latter won't work. Have you tested that this works? I just looked at the swift code that parses the model folders and it seems that the following happens: - All paths that contain "/AI/Aircraft" are searched for .xml files. These files are added as "included" models to the model overview - All...

Swift/Vatsim: blue glider instead of Cessna 172

You could add the "FG AI C172/C-FGFS" from $FGDATA/AI to your model set. This renderes fine. You can also test this without connecting to a network by using the model browser (https://swift-project.org/troubleshooting/model_browser/) Regarding using detailed (non-AI) models to display others: If I remember correctly, there were some limitations on how the AI Subsystem (which swift uses behind the scenes) can use these models. Hence, only the AI/not-detailed/non-userflyable planes are available. If...

Fix swift regression

swift: Fix endless loop

Replace deprecated include

swift: Fix unittest