20,741
edits
m (Hooray moved page Canvas Terrain Element to Canvas Tile Element without leaving a redirect: seems more appropriate) |
m (https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33880.html) |
||
Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
Some contributors have been experimenting with | Some contributors have been experimenting with atlas based moving map displays (with pre-rendered Atlas images), but with nasal code.<ref>https://sourceforge.net/p/flightgear/mailman/message/20010870/</ref> <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33880.html</ref> | ||
James originally implemented the a moving navigational [[Map]] as a custom PUI widget - it's *not* an Atlas-replacement, or an MPMap replacement, i.e. not intended to also display terrain elevation <ref>https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27097.html</ref> | |||
An Atlas- style renderer as another layer is possible, it'd also let me build the one GUI element I've been wanting for ages, a 'map' dialog box with navaids and airways overlaid, like the map UIs in MSFS / X-Plane / Fly. <ref>https://sourceforge.net/p/flightgear/mailman/message/20012110/</ref> | |||
In order to feed imagery from tools like Atlas or moving maps in general from a network server, you'd want to look at protocols like WMS and the servers which | In order to feed imagery from tools like Atlas or moving maps in general from a network server, you'd want to look at protocols like WMS and the servers which |