Download and unpack the archive (e.g., “gzcat | tar xf -” or whatever is appropriate in your environment).
ANTHEMSCORE NOTES DELAYED MANUAL
No manual modifications should be necessary to produce an executable program on any of the tested operating system environments. The source distribution archive contains the code, a Makefile and a few helper scripts.
To use xplage, you need to download it from one of the distributions on this page, configure X-Plane to transmit data to it, and then set up Google Earth to read and display the files that xplage produces.
A man page describing the program's run-time options is included in both the source and binary distributions, as is a ReadMe file which provides supplemental information about using xplage in your environment.
ANTHEMSCORE NOTES DELAYED CODE
Both the source code and the distributed binaries by default listen on UDP port 49000 and place their output in an “xp2ge” subdirectory of the standard HTML document hierarchy for the Apache web server on the target platform: i.e., /xp2ge/overhead.kml for the overhead map view and /xp2ge/perspective.kml for the perspective view. Unsupported and minimally tested binaries compiled for X86 target platforms (the OS X executable is a “universal binary”) may also be downloaded from this page. It should require no more than minimal coaxing to compile the source code on other platforms that support the POSIX application programming interface. Compilation with GNU C has also been verified on Apple OS X (release 10.6), Ubuntu Linux (release 11.2), and-using the Cygwin development suite-Microsoft Windows NT (release 6, a.k.a. The program was designed and tested on Solaris/X86 (release 10) with both Oracle’s native compiler and the GNU C compiler. The xplage program is distributed primarily as open source code in the C programming language subject to the terms of the GNU General Public License. Delays in fetching satellite imagery through the public Internet from Google's servers may also contribute to the time lag. In other words, if xplage is set to refresh at one-second intervals and Google Earth is set to refresh at two-second intervals, the moving map images may lag as much as three seconds behind the actual position of the simulated aircraft. This delay can be as great as the sum of the two refresh intervals. In effect, they represent still photo frames that capture the position of the aircraft a short time before they are displayed. Note that because the refresh rates of xplage and Google Earth are independent and asynchronous, these moving map images lag slightly behind the flight simulation. Each refresh cycle repaints the perspective based on the simulated aircraft's roll and pitch orientation. In this view, the eye may be thought of as being directly in front of the airplane and pointing slightly downward. The second KML file is used by Google Earth to display a perspective view of the terrain ahead of the simulated aircraft. Each refresh cycle shifts the map in the direction of the flight path so as to keep the icon centered.
In this view, the Google Earth “eye” is fixed directly above the airplane. The first is used by Google Earth to display an overhead map with North at the top and an icon in the center of the satellite image to indicate the position of the simulated aircraft. Xplage repeatedly generates two different KML files at a refresh interval specified by the user. Albuquerque Toward Sandia, Map View (left) and Perspective View (right)
0 kommentar(er)
