20,741
edits
FG1000: Difference between revisions
→Motivation
| Line 36: | Line 36: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
== 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 42: | Line 45: | ||
air navigation </nowiki> | air navigation </nowiki> | ||
|author = <nowiki> Thorsten Renk </nowiki> | |author = <nowiki> Thorsten Renk </nowiki> | ||
|date = Jul 4th, 2017 | |||
|added = Jul 4th, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
we need to be realistic here: The G1000 is a fairly significant piece of computer hardware that we're going to emulate. It's not going to be "free" particularly for those on older hardware that's already struggling. However, hopefully we can offload a chunk of the logic (route management, autopilot/flight director) to the core, and do things like offline generation of terrain maps to minimie the impact.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35926745/ | |||
|title = <nowiki> Re: [Flightgear-devel] RFD: FlightGear and the changing state of | |||
air navigation </nowiki> | |||
|author = <nowiki> Stuart Buchanan </nowiki> | |||
|date = Jul 4th, 2017 | |date = Jul 4th, 2017 | ||
|added = Jul 4th, 2017 | |added = Jul 4th, 2017 | ||