20,741
edits
FG1000: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Layers) |
No edit summary |
||
| Line 96: | Line 96: | ||
}}</ref> | }}</ref> | ||
== Performance == | == Background == | ||
{{Main article|Complex Canvas Avionics}} | |||
== Challenges == | |||
=== Performance === | |||
it's a lot of work to code all these displays which someone has to do, but there's no reason to assume it'd be hopeless performance-wise.<ref>{{cite web | it's a lot of work to code all these displays which someone has to do, but there's no reason to assume it'd be hopeless performance-wise.<ref>{{cite web | ||
| Line 118: | Line 122: | ||
}}</ref> | }}</ref> | ||
=== Route Manager === | === Route Manager === | ||
that's exactly the kind of device James hopes the new code can support. He's read the G1000 pilot's manual, and *thinks* that nearly all the functions can be provided by the current GPS code It would be great if people could look over the current GPS features and indicate any pieces you think might be missing - additional commands, additional search features, extra data, or anything really. <ref>{{cite web | that's exactly the kind of device James hopes the new code can support. He's read the G1000 pilot's manual, and *thinks* that nearly all the functions can be provided by the current GPS code It would be great if people could look over the current GPS features and indicate any pieces you think might be missing - additional commands, additional search features, extra data, or anything really. <ref>{{cite web | ||