Number and Description of Issue

1419 Modified the Grid Structure page on the Data Object Editor so it no longer accepts invalid row or column numbers.

5223 Fixed problems in the "Copy by Coverage" option of the statemap extended copy command.

5488 Modified various processes to report the amount of disk space that will be consumed by running that process.

5571 Fixed problem where Project Culture was not finding the correct textures in all cases.

5983 Fixed problems using the Spatial View with Matrox Perihelia graphics cards.

6279 Fixed crash that occurred in some cases when editing a Build Structure process.

6530 Fixed crash during CTS launch caused by corrupted workspace file.

6870 Fixed bug in CTS 3D Viewer where the heading in the viewer does not match the heading displayed in the Spatial View.

7033 Fixed crash in Spatial View when opening Image Grid datasets.

7034 Fixed exception in Tessellate Mesh that occurred in some cases when building irregular mesh terrain.

7141 Fixed resource file. Simple values over oceans was -1000. These values have been corrected in the new image to be 0.

7148 Fixed problem in BuildVT process where it didn't recalculate the number of virtual texels when the grid or tile size changed.

7170 Fixed problem using Chop Image on certain GeoTIFF files.

7241 Fixed an erroneous error message that was reported by the Image Wizard while building the workflow.

7254 Fixed a case in the Terrain Wizard where it produced a terrain design that wouldn't display the full resolution of the virtual texture to which it was tied.

7274 Fixed problems in Map Texture while mapping multiple textures to a terrain.

7276 Fixed bug in Task Explorer where it would not let you delete a task that has another task as its child.

7297 Fixed the Build Structure process so it correctly sets the DB Origin field in the OpenFlight header when using the UTM coordinate system.

7332 Fixed Spatial View so it loads DFD files.

7433 Fixed Data Object editor Coverage page. Coverage extents did not always update when the underlying coordinate system changed.

7479 Fixed Data Object editor Grid Level Data page. Previously, edits were lost if you switched to a different page without clicking the Apply button. This is inconsistent with the behavior of the other pages.

7581 Fixed crash in file name pattern parser when the format string did not match the type of the token variable. For example, you'd get a crash if you used a %s format string with LATDEG (because LATDEG produces numbers, not strings).

7705 Fixed Integrate Sites so that it works with terrain that uses any grid coordinate system. Previously, the terrain's grid coordinate system was required to be Geodetic.

Other fixes that were not added as bugs include:
- Fixed the problem where duplicate ellipsoids were created with the same name.
- Fixed bug in MetaFlight exporter process where it wrote incorrect values for ellipsoid datum shift.

Enhancements

Bilinear Filtering in Chop Image
The Chop Image tool now allows you to turn off the default Bilinear filtering. Bilinear filtering takes surrounding texels and averages their colors to create new texels. Turning off Bilinear filtering means the Chop Image tool uses Nearest Neighbor filtering, which has less of a dramatic effect on the original texels. In other words, the resulting chopped imagery is more like the original imagery, whereas imagery that has been Bilinear filtered is more blurred. The following graphic shows the location of the added Use Bilinear filtering option.

For better looking imagery, you should always use the default Bilinear filtering. You should only turn off Bilinear filtering if you do not want the input texel color to be changed during the Chop. For example, chopping material textures (, such as Blueberry3D Terrain Class Raster files) is a case where you do not want the input texel color to change.

MetaFlight Explorer Improved Performance
This version also includes improved performance of MetaFlight Explorer, especially on launch, when there are many data objects in the POD.

Blueberry3D Launch Terrain Editor
We have removed the Blueberry3D Terrain Editor item from the Processes menu. You can access the Blueberry3D Terrain Editor from Start > Programs > Blueberry3D. If you have installed previous versions of the Blueberry3D Terrain Editor (in CTS v1.1), it is likely that you may experience problems with the CTS Spatial View. We strongly recommend that if you have previously installed versions of the Blueberry3D Terrain Editor that you complete the following procedures:
1. Uninstall any previous version of the Blueberry3D products.
2. Install the CTS v1.1.1 patch.
If you still experience problems with the CTS Spatial View:
1. Uninstall all Blueberry3D products.
2. Uninstall CTS.
3. Re-install CTS.
4. Re-install Blueberry3D plug in.
If the Spatial View instability still persists, contact customer support (toll free at 877-289-5670) and be sure to indicate what steps you have already been taken. We will give you a manual clean-up procedure for the Windows Registry.
Render Textured Polygons White Flag
Two CTS processes have been modified to add the ability to clear the Render Textured Polygons White flag:
- Edit Flt Attributes
- Verify Open Flight

Edit Flt Attributes
The Edit Flight Attributes process has been modified to add the ability to clear the Render Textured Polygons White flag on polygon nodes. CTS generates databases with this flag set on terrain polygons under normal circumstances. Edit Flight Attributes was modified to allow you to clear this flag in your database if desired.
The Render Textured Polygons White checkboxes work as follows:
- If you would like to set the Render Textured Polygons White flag on all polygons, then select the Set "Render Textured Polygons White" flag checkbox.
- If you would like to clear the Render Textured Polygons White flag on all polygons, then select the Clear "Render Textured Polygons White" flag checkbox.
- If you do not want to modify the Render Textured Polygons White flag either way, then uncheck both checkboxes.