580
edits
Aircraft testing checklist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
For aircraft in FGaddon which have been claimed for testing, see the [[aircraft_tester_list|tester list]] | For aircraft in FGaddon which have been claimed for testing, see the [[aircraft_tester_list|tester list]] | ||
= Metadata = | |||
* does the aircraft have a clear name (not so long it overflows) | |||
* is the description appropriate? Long enough to be relevant but not an essay.. | |||
* does it have new-style previews / splash screen in the launcher? | |||
= Basic experience = | |||
* start on a runway, and start the engine manually | * start on a runway, and start the engine manually | ||
| Line 7: | Line 15: | ||
* start in-air: eg use the 'on approach' feature of the launcher | * start in-air: eg use the 'on approach' feature of the launcher | ||
(note different aircraft may not work for an in-air start) | (note different aircraft may not work for an in-air start) | ||
* if the aircraft has terrain variants (eg, skis, floats) and you have time, check they work as expected (eg seaport takeoff and landing for floats). | |||
* check throttle (and pitch and mixture) work as expected (Eg, does the engine cut out at full lean? Does it redline at full throttle on the ground?) | * check throttle (and pitch and mixture) work as expected (Eg, does the engine cut out at full lean? Does it redline at full throttle on the ground?) | ||