580
edits
Aircraft testing checklist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 62: | Line 62: | ||
* Check appearance under a compositor build | * Check appearance under a compositor build | ||
* Check appearance under very high ALS settings? | * Check appearance under very high ALS settings? | ||
* failures: if the aircraft supports them, are they plausible. (eg overspeed with flaps extended). Especially, can they be reset back to working from a UI dialog, and does re-positioning cause them to trigger incorrectly. | |||
= Autopilot checks = | = Autopilot checks = | ||
* If the aircraft has an autopilot implemented in the cockpit, check controls work for basic modes (ROLL, PITCH). If the aircraft does not have an autopilot implemented, there is no requirement for the generic autopilot menu item to work successfully. | * If the aircraft has an autopilot implemented in the cockpit, check controls work for basic modes (ROLL, PITCH). If the aircraft does not have an autopilot implemented, there is /no/ requirement for the generic autopilot menu item to work successfully. | ||
* Intercept a VOR / leg : check the turning to intercept, and overshoot / roll out when reading the correct position | * Intercept a VOR / leg : check the turning to intercept, and overshoot / roll out when reading the correct position | ||
* check the AP is stable at 2x time acceleration, and see if it is at 4x or 8x (lots aren't....) | * check the AP is stable at 2x time acceleration, and see if it is at 4x or 8x (lots aren't....) | ||
* Setup a basic route in the route-manager, and check interaction with the AP if supported: especially following waypoints and sequencing above them. This is more important for glass cockpits. | |||