Aircraft metadata checklist: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Legoboyvdlp (talk | contribs) (→Metadata / -set.xml: Add fallback model, ratins.) |
||
Line 4: | Line 4: | ||
Checking / fixing these items should take about 30 minutes per aircraft (maybe a little longer the first time) | Checking / fixing these items should take about 30 minutes per aircraft (maybe a little longer the first time) | ||
* Ensure the aircraft ratings are set | * Ensure the aircraft ratings are set and not wildly inaccurate. | ||
* Ensure any tags are from the official list of tags (in fgmeta tags.py) | * Ensure any tags are from the official list of tags (in fgmeta tags.py) | ||
* Ensure the aircraft has a suitable name and description | * Ensure the aircraft has a suitable name and description | ||
Line 14: | Line 14: | ||
* Ensure any development files are excluded from the generated .zip (eg XCF or PSD files) | * Ensure any development files are excluded from the generated .zip (eg XCF or PSD files) | ||
* Examine the console log and resolve any reported aircraft issues (e.g. PNG bad color profile, missing files, etc.) | * Examine the console log and resolve any reported aircraft issues (e.g. PNG bad color profile, missing files, etc.) | ||
* Add an appropriate fallback model | |||
= Code changes = | = Code changes = |
Revision as of 21:35, 25 May 2020
This list is various simple checks and modifications to improve user experience with aircraft.
Metadata / -set.xml
Checking / fixing these items should take about 30 minutes per aircraft (maybe a little longer the first time)
- Ensure the aircraft ratings are set and not wildly inaccurate.
- Ensure any tags are from the official list of tags (in fgmeta tags.py)
- Ensure the aircraft has a suitable name and description
- For multi-variant aircraft, ensure the primary aircraft is a sensible choice (eg not a copilot or floats/skis variant)
- Add new-style preview images
- Ensure the thumbnail is the correct size and follows the guidelines (not a logo, not a photograph)
- Set minimum-fg-version and compatible-fg-version values in the -set.xml if required
- Review the 'catalog generator' error messages for the aircraft (eg, XML formatting errors)
- Ensure any development files are excluded from the generated .zip (eg XCF or PSD files)
- Examine the console log and resolve any reported aircraft issues (e.g. PNG bad color profile, missing files, etc.)
- Add an appropriate fallback model
Code changes
- Ensure the aircraft uses the global property for enabling/disabling the pilot model.
- ?