20,741
edits
Canvas tile element: Difference between revisions
Jump to navigation
Jump to search
m
→Idea: https://forum.flightgear.org/viewtopic.php?f=31&t=37158
(→Idea) |
m (→Idea: https://forum.flightgear.org/viewtopic.php?f=31&t=37158) |
||
| Line 27: | Line 27: | ||
Given that we do have existing code to render such maps, and that the Canvas system does have support for loading raster images ([[Canvas Image|sc::Image]]), this would be the most straightforward option to ensure that there is no mismatch between a moving map and a corresponding radar display, because it'd be using the same underlying terrain/vector data. | Given that we do have existing code to render such maps, and that the Canvas system does have support for loading raster images ([[Canvas Image|sc::Image]]), this would be the most straightforward option to ensure that there is no mismatch between a moving map and a corresponding radar display, because it'd be using the same underlying terrain/vector data. | ||
== Integrating Atlas == | |||
atlas isn't "obsolete" - it just works "as is". What it provides ? A moving map, and in fact an accurate moving map - because it contains its own terrain processing routines that "parse" FlightGear scenery/terrain to render moving map charts interactively, and it does so in a different process (out of the FlightGear main loop), so can easily use other cores. | |||
These days, it may admittedly seem redundant and even irrelevant thanks to options like Phi and/or Azure. But the truth is, atlas remains relevant, because it processes actual FlightGear terrain files to create those charts, but also because it's an "offline" application, you don't need a high bandwidth internet connection - it will even work without an internet connection. | |||
As a matter of fact, the right thing to do would be absorb atlas/map into simgear and use it in-sim to dynamically create charts "on demand", which would then include "up to date" airport charts (think runways, taxiways, frequencies etc) - but that would also mean updating atlas, because it's still from the early pre-OSG days, i.e. is using legacy OpenGL<ref>https://forum.flightgear.org/viewtopic.php?f=31&t=37158</ref> | |||
== References == | == References == | ||
{{Appendix}} | {{Appendix}} | ||