2.12 lessons learned
See Release plan.
We still keep seeing issues due to aircraft developers contributing resources with files, file names, paths that would break support on OS with case-sensitive OS or a different locale setting, it would make sense to add some form of optional and automated/scripted validation during startup to detect such issues, without requiring a manual review, possibly through Catalog metadata 
Things that could be checked by using Nasal and corresponding SimGear bindings:
- XML validation
- file/path look-up
- texture dimensions
- max texture size
- check for rgb, png, dds textures
- check for stereo files
- try to resolve shader references
- try to compile shaders
- validate effects
- resolve dependencies to external resources (aircraft, instruments)
What is this?
The purpose of this may need further explanation. From this page alone I am not able to figure out the purpose of this, only make educated guesses. My best guess is that this is about a more or less fixed set of tags that probably is added to aircraft in the
aircraft-set.xml that may or may not be parsed as of now, in essence being an experimental or developing feature.
- It's basically Formalizing Aircraft Status, but more in line with the original proposal. The whole idea is to allow aircraft to be categorized and classified based on meta information, i.e. for downloading/installing (GUI frontend, integrated GUI and/or website) (Simplifying Aircraft Deployment). --Hooray (talk) 16:35, 12 March 2014 (UTC)
- I have now added a first section describing what the article is all about, an example of how to use the metadata tags and tried to link together some other resources and a relevant devel list thread.
- Smoke (if an aircraft can make smoke trail. E.g. Alphajet)
- Rotary (engine). This is a wildly different type of engine than a radial engine, so definitely deserving of a separate entry. https://en.wikipedia.org/wiki/Rotary_engine#Distinction_between_.22rotary.22_and_.22radial.22_engines