home *** CD-ROM | disk | FTP | other *** search
-
-
- EARTHVIEWER 3D NVIDIA RELEASE NOTES
- VERSION 1.4.1
-
-
- Welcome to EarthViewer 3D, the most exciting way to view the planet! These
- release notes identify the system requirements for the application.
- They also list any issues that may affect the use of the application and
- any work arounds or corrective measures (if any exist).
-
-
- OPERATING SYSTEM REQUIREMENTS
-
- This version of EarthViewer 3D has been tested on the following versions
- of the Windows operating system.
-
- - Windows 98 SE
- - Windows Me
- - Windows 2000 with Service Pack 2
- - Windows XP
-
- This version of the application is only available on systems with NVIDIA
- GeForce 2, NVIDIA nForce or higher NVIDIA graphics cards or chipsets.
-
-
- COMPUTER SYSTEM REQUIREMENTS
-
- The EarthViewer 3D application requires a computer system that is capable of
- hardware accelerated 3D rendering and the ability to handle its large data
- demands. It is recommended that your system have at least the following
- characteristics to realize the full power of the EarthViewer 3D application.
-
- - Intel Pentium II processor or higher with a clock speed of at least 300 MHz.
- - At least 128 MB of memory (256 MB preferred).
- - NVIDIA GeForce 2, nForce or higher graphics card.
- - The latest NVIDIA Detonator driver (EarthViewer 3D was tested against
- version 28.32).
-
- Please note that many features have been added that potentially tax system
- resources, especially memory. While EarthViewer 3D has been tested with the
- minimum memory configuration, the preferred configuration of 256 MB of memory
- is recommended especially if terrain is used.
-
-
- PERFORMACE INFORMATION AND KNOWN ISSUES
-
- Using the application with the minimum supported memory configuration will have
- acceptable results if used with default settings. Increasing the detail area,
- enabling terrain elevation, enabling roads, using high resolution printing or
- adding significantly to the load of the application warrants the recommended
- memory size. Configurations with the minimum supported memory configurations
- may experience significant performance degradation.
-
- We have improved memory consumption within the application, but more is always
- better when using high detail texturing (1Kx1K detail area), anisotropic
- filtering with 32-bit textures. In general, if you try it and performance
- drops dramatically, you are resource constrained and should reduce one or more
- of these parameters in the preferences dialog.
-
- Enabling roads when terrain is enabled can cause minor anomalies in some
- areas, especially in areas with pronounced elevation changes.
-
- Viewing of cities with a large number of popular places is difficult due to the
- heavy grouping of labels. Also, the placement of labels is often times confusing.
-
- When the network is not connected, the Keyhole logo may spin constantly. This
- indicates that the application is attempting to fetch data from the network and
- cannot.
-
- Running the application with 16-bit textures results in slower application
- response time. While this does not limit the utility of the application, it
- can be annoying if the expectation is high frame rates. Using 32-bit textures
- fixes this performance problem at the expense of additional memory requirements.
-
-