20,741
edits
m (https://sourceforge.net/p/atlas/hgcode/ci/default/tree/src/GetMap.cxx) |
m (https://www.mail-archive.com/flightgear-devel@flightgear.org/msg16345.html) |
||
Line 6: | Line 6: | ||
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> | 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> | ||
The nice thing about Atlas is that it uses the current FlightGear scenery for generating it's maps. If we get better scenery, Atlast produces better maps.<ref>https://www.mail-archive.com/flightgear-devel@flightgear.org/msg16345.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> | 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> |