Resolved Issues Relating to all Autodesk LandXplorer Products

The following issues have been resolved in this update of the LandXplorer software.

Installation

Improvements to unicode support solves an installation problem encountered on some operating systems

The resolution of unicode issues with the installation wizard now allows all Autodesk LandXplorer products to be successfully installed on system running Asian-language versions of the operating system.

Resolved Issues Relating to Autodesk LandXplorer Studio Professional

The following issues have been resolved in this update of the LandXplorer Studio Professional software.

Images and Graphics

Selection of unsupported image formats for use as a background wallpaper fails.

When attempting to Insert > Background, the Finish button remains inactive when you select an unsupported file format as a background wallpaper.

• When choosing an image to use as a background wallpaper, you can set the file of type to All Files (*.*). This allows you to select unsupported file formats, such as TIF. Making an unsupported file selection causes the Finish button to remain inactive. This is as designed.

  The workaround is to open the unsupported image file in your preferred graphic editor and save it as a supported file format.

Insert Data

The LDX file format is not supported when attempting to insert CityGML models.

• When inserting a CityGML model, only CityGML files (.gml and .xml), and Zip Archive files (.zip) are accepted. The .ldx file format is not supported. This is as designed.

Text strings containing German umlaut characters are now correctly read from SHP files.

• Shapefiles containing attribute data, such as names and values, which use umlaut characters are correctly interpreted when they are inserted into Autodesk LandXplorer Studio Professional.

The Default Height value of inserted city model data cannot be set to a negative number during the insertion process.

When you start the insertion process of city model data, you have the option to specify the Default Height of block buildings. If the height value is left blank, set to 0 (zero), or set to a negative number, the Next button of the insertion wizard will remain inactive. You can proceed after changing the setting to a valid, non-negative value.

• Once the city model data is inserted, you can make adjustments as expected.

  Note: The Default Height value can never be adjusted to 0 (zero), or to a negative value; even after insertion.

Using the grasp handles of 3D objects, labels, etc., no longer cause erroneous height shifts.

Fixes to explicit positioning allow you to successfully adjust the 'Y'-value of objects in the project by means of the grasp handles.

Resolved Issues Relating to Autodesk LandXplorer Xpress Viewer

The following issues have been resolved in this update of the Autodesk LandXplorer Xpress Viewer software.

User Interface

Title bars of projects containing German vowels in their names now display correctly.

When you start the Pack & Go process in Autodesk LandXplorer Studio Professional, you must enter a project name. The project name becomes the name of the exported Xpress Viewer project. Updates to the third-party library that handles XML content in LXPC files now allows German vowels used in the project name to display correctly in LandXplorer Xpress Viewer.

Return to Top

Issues Related to Autodesk LandXplorer Studio Professional 2009 Update 2

The following content clarifies and updates information pertaining to the functions and features of Autodesk LandXplorer Studio Professional 2009 Update 2.

Configuration

Missing graphic card drivers can cause Autodesk Landxplorer Studio Professional to crash.

If Autodesk LandXplorer Studio Professional is installed on a system that is missing graphic drivers, or has outdated graphic drivers, you may encounter program crashes.

• Because Autodesk Landxplorer Studio Professional is a graphic intensive program, ensure that you are using the latest drivers for your graphic card, and confirm that your graphic card meets the system requirements for running the program.

Database

Inability to query city model data that is stored on a MySQL database.

After connecting to a MySQL database and attempting to insert city model data, you are informed that Autodesk LandXplorer Studio Professional 'Could not query city model data with the given settings'.

• This message is a result of a missing DLL file (libmysql.dll) that is required for proper connection to the database. The DLL file is a component of MySQL and added to your system when you download MySQL.

  Once you've downloaded MySQL, copy the libmysql.dll file to the Autodesk LandXplorer Studio Professional install folder. For example, C:\Program Files\Autodesk\LandXplorer Studio Professional 2009.

Documentation

Change in navigation naming not updated in the Button documentation.

Using the currently documented navigation options when creating a command for a button will not work because the navigation option names have been changed.

• In the Main Features > Button topic of the help system, the navigation options for the <token> string currently reads;

  DEFAULTPOSITION | ANIMATION | SPHERENAV | CONENAV | GAMENAV | UFONAV

• The correct navigation options are;

  DEFAULTPOSITION | ANIMATION | EXAMINE | GAME | FLYER | PANNING | ADVANCED

Lack of animation objects renders PLAY action unusable.

Attempting to program a button to use the PLAY action fails because animation objects cannot be referenced.

Web site location for downloading the Database Plug In changed to the Autodesk LandXplorer Product Center.

The Autodesk LandXplorer Studio Professional documentation indicates that the Database Plug In is downloadable from the Subscription Center site if you are a member.

• The download location of the Database Plug In was changed to provide easier access. You can now download the plug in from www.Autodesk.com/LandXplorer.

Insert Data

Filenames of inserted data cannot contain '#' characters.

If you insert a file whose filename contains '#' characters, the name of the object is truncated when displayed in the Objects window.

• Ensure that files you want to insert do not contain '#' characters. For example, My#Building.3ds or My#Terrain.ltt.

Unable to control the pole height of text or symbol labels.

There appears to be an uncontrollable height offset (the pole height) for text and symbol labels. Setting the height or elevation to values less than 0 (zero) shifts the text or symbol closer to the ground plane, but rotating the project shows that the associated poles simply protrude below the terrain instead of getting shorter.

• At present, there is no control over the pole height. This is a wishlist request for future releases.

Recording

Using non-4:3 aspect ratios with the Live Record feature results in poor quality videos.

Attempts to generate live recordings using 1:1 aspect ratios, such as 500x500, 487x487, or 363x363, produce very poor quality videos.

• Whenever possible, stick to using output resolutions that conform to a 4:3 aspect ratio, such as 640x480, and 320x240, for best results.

Pack & Go

Redundant label groups appear for Trees and Points of Interest during Pack & Go procedure.

The Main Selection page of the Pack & Go process displays duplicate label groups for Trees and Point of Interest when you attempt to insert trees from a database.

• This is expected behavior. Label groups are treated differently by Autodesk LandXplorer Studio Professional and Autodesk LandXplorer Xpress Viewer. Tree groups and any labels are recognized as label groups by Autodesk LandXplorer Studio Professional. In Autodesk LandXplorer Xpress Viewer, label groups are delineated as trees (3DModels of any kind) and points of interest (Images and Text of any kind).

Self-intersecting polygons cannot be exported as water.

A polygon that intersects itself is not a valid object for exporting as a water object. The water is not displayed when the exported project is opened in Landxplorer Xpress Viewer. Furthermore, if you export a project to be hosted by Autodesk LandXplorer Server, the water layer is created, but the renderer will not support it and an error message is displayed. Until the water layer is disabled, Autodesk LandXplorer Server will not display any images.

• To ensure that this situation never occurs, refrain from drawing polygons that intersect themselves.

Performance

Performance becomes very slow when inserting SHP files containing large amounts of vector data.

When inserting an SHP file containing a very large amount of vector data to a vector layer, Autodesk LandXplorer Studio Professional slows down. Some may mistake this slow down with a program freeze.

• Autodesk LandXplorer Studio Professional is a memory intensive program. The management and display of large amounts of 2D vector data can use a lot of your system resources and cause the program performance to suffer. Ensure that your system meets or exceeds the recommended amount of system memory, or work with SHP files containing less data.

Server Plug In

WPVS Management Client fails to launch in Chinese version of Windows XP.

Due to a missing mscoree.dll file in the Chinese version of Microsoft Windows XP, you must install Microsoft .NET Framework 3.0. Once installed, the WPVS Management Client starts as expected.

Issues Related to Autodesk LandXplorer Xpress Viewer 2009 Update 2

The following content clarifies and updates information pertaining to the functions and features of Autodesk LandXplorer Xpress Viewer 2009 Update 2.

Project File

Projects containing Unicode Supplementary Characters fail to open.

Unicode characters, stored in the supplementary character plane, should not be used to name Objects in the Objects window of LandXplorer Studio Professional.

• When preparing a project for output to LandXplorer Xpress Viewer, ensure that objects are not named using unicode characters stored in the supplementary character plane. Many Chinese, Japanese, and Korean characters are stored in this plane and due to a lack of unicode support by one of the third-party libraries, projects will fail to open.

Issues Related to Autodesk LandXplorer Server 2010 Update 1

The following content clarifies and updates information pertaining to the functions and features of Autodesk LandXplorer Server Update 1.

Installation

The documentation cannot be accessed directly from the DVD.

During the Landxplorer Server installation, you are expected to configure the product. Without access to the documentation, it is unclear what you need to set.

• While you cannot access the LandXplorer Server documentation from the DVD, you can access the documentation online at Autodesk LandXplorer Server 2010.

Clarified IIS 7.0 installation for Windows Server 2008.

The documented procedure for installing IIS 7.0 for Server 2008 is confusing and inadequate. Follow these steps for correct installation:

1. Open the Server Manager.
2. Navigate to Features and then click Add Features.
3. Enable all three features listed under 'Windows Process Activation Service'.
4. Under Remote Server Administration Tools and Role Administration Tools, enable 'Web Server(IIS) Tools'.
5. Navigate to Roles and then click Add Roles.
6. Enable 'Web Server(IIS)'.
7. Enable 'IIS Metabase and IIS 6 configuration compatibility'.

The rendering service fails to start when run with the Chinese version of Windows Server 2003.

After connecting to a server installed with the Chinese version of Windows Server 2003, and uploading a project, attempts to start the rendering service causes the rendering service to stop.

• When a project is loading, the rendering service gets configured. During the time it takes to load the project, all rendering requests are denied and the rendering service stops. Once the project has completed the uploading process, the rendering service starts displaying pictures. The rendering service remains stopped until the project loading is complete, so the size of the project delegates how long it takes for the rendering service to become active. You can check the status of the rendering service by clicking Refresh. Should an error occur, you can also review the renderer log file by right-clicking the renderer item.

Configuration

Inability to connect to the Server using an Administrator account other than the default account.

Access is denied when attempting to connect to the server from the Management Client dialog box if you've created a new system account and assigned it to the Administrator group.

• During the installation and configuration of Autodesk LandXplorer Server, a user group named LdxServerAdmin is automatically created. By default, the person (with Administrator rights) who is performing the installation is added to this group. If you want more users to administer Autodesk LandXplorer Server, you must to add them to the LdxServerAdmin group. They do not need to be actual members of the Windows Administrator group.

The installation process stalls when entering a Rendering Service Name containing Asian characters.

When configuring the Server Installer, during the Installation process, entering a Rendering Service Name containing Asian characters will not allow you to finish the installation.

• If you must change the name of the rendering service while installing and configuring Autodesk LandXplorer Server, refrain from using Asian characters. If an unsupported character is entered in the Rendering Service Name field, the background color changes to red and the suspicious character is selected. Change the offending character and proceed with the installation process.

Issues Related to Autodesk LandXplorer Publisher 2010 Update 1

The following content clarifies and updates information pertaining to the functions and features of Autodesk LandXplorer Publisher Update 1.

Documentation

Building color is not set as expected when using the FormatColor property.

The implementation of the color channel order is alpha, blue, green, red (ABGR) instead of the documented alpha, red, green, blue (ARGB). This means the examples given will not produce the documented building color.

• FF00FF00 = Opaque green
• 880000FF = Semi-transparent red

The alpha channel value of the RoofColor property is always opaque.

The RoofColor property requires an alpha channel value, similar to the FormatColor property. However, transparency is not supported and all values result in opaque colors.

Typo found in the Block Buildings; Height topic pertaining to the FormatDropToTerrain attribute.

The documentation incorrectly names the FormatDropToTerrain attribute as FormatDropOnTerrain.

• The correct name of the attribute is FormatDropToTerrain and it controls the placement of objects on the terrain.

Description missing for the '...' formatable boolean settings of some attributes.

Some attributes, such as FormatSelected, FormatOutline, FormatConvertToBlackAndWhite, FormatBackFaceCulling, FormatUseLowerBBoxCenterAsOrigin, FormatDropOnTerrain, FormatExtrude, IsAbsoluteHeight, FormatFillColorAsRandom, FormatLineColorAsRandom have a '...' setting that is not described in the documentation.

• Aside from having 'true' and 'false' settings, these attributes allow you to set a formatable boolean by setting the '...' value. This value is editable, and you can define data mapping to any source attributes, such as [shp_attr_name].

Generate

Generating a project fails when operating with less than Administrator rights.

Attempts to generate a project with less than Administrator right, for example, PowerUser, result in a project generation failure.

• In order to successfully generate a project for viewing with Google^™ Earth, you must have Administrator right. Furthermore, Google Earth must also be installed and run by users with Administrator rights. Autodesk LandXplorer Publisher does not support cross-privilege groups between your Google Earth installation and Autodesk LandXplorer Publisher operation.

Properties

Default KML attributes are used when optional properties are deleted and a project is generated.

If attributes are deleted for optional properties, like FormatLineWidth, FormatFillColor, or FormatLineColor, and the project is generated, the corresponding KML attribute is not created and the default KML attribute is used for visualization. There are no warnings entered into the log file. Furthermore, the properties are not reset to their original values.

• At present, not all properties are validated as some are required, while others are optional. Only required properties are checked for empty values. If required properties are found to be empty, they are noted in the log file.

Return to Top

Before You Begin

As you prepare to install, or update, Autodesk LandXplorer software, keep the following in mind:

Close all Autodesk LandXplorer software family products before updating

Before installing any updates, ensure that the Autodesk LandXplorer software you are updating is not running.

Administrative Privileges

In order to install, or apply updates to, any Autodesk LandXplorer software, you must have administrative privileges to install and uninstall programs.

Return to Top