Release notes

Version 1.1.0 - December, 2022.

This page provides details about enhancements in ArcGIS Maps SDK for Unity version 1.1.0. It also lists this release's resolved issues, and known issues.

Enhancements

This section describes new features and improvements (what's new).

Vector tile layers support

A vector tile layer references a set of web-accessible vector tiles and a corresponding style that dictates how the tiles will draw. The vector tile layers can adapt to any display resolution, which can vary across devices. A vector tile layer can be stored as a vector tile package (.vtpk file) on disk. You can use vector tiles layers from online services as well as from local file packages in Unity.

Basemap layer service support

Support for the basemap layer service has been added. The Esri curated basemap layers listed in the World basemaps for developers group can be used as a basemap in a Unity scene.

Scene layers support

• Draco geometry compression support has been added. Draco is a library for compressing and decompressing 3D geometric meshes and point clouds to improve storage and transmission of 3D graphics. ArcGIS Maps SDK for Unity can read the compressed geometries in this format from 3D object scene layers and integrated mesh scene layers to improve performance.

• PBR metallic roughness material model support has been added. The defined metallic-roughness material model parameter values are supported by ArcGIS Maps SDK for Unity.

API key improvements

• A global API key can be set in Unity's Project Settings and used in multiple scenes in the same project.

C# API

• Added a new basemap constructor that uses the basemap style services.

Components

• Quality Scaling Factor has been added to the ArcGIS Camera component to allow control of the quality of the GIS content being rendered.

Map Creator UI

• The basemap gallery has been updated and contains more basemap options per the basemap layer service support.

Issues resolved

• ArcGIS Hit Test Sample returns an incorrect number instead of the feature ID

  Summary: ArcGIS Hit Test Sample returns an incorrect number instead of the feature ID when clicking on a building while pressing the shift key during play mode.

• Tile flashing

  Summary: While navigating in the scene, a few tiles flash occasionally and image tiles are missing when the elevation is enabled. (There is a different tile flashing issue in the known issues.)

• Map extent configuration via C# script being ignored

  Summary: The map extent configuration via the C# script is overwritten by the ArcGIS Map component, and has no effect in both the play mode and the editor mode.

• The Android compiling errors

  Summary: Compiling for Android fails with RenderTexture.Create failed: stencil texture format unsupported.

• The Sample OAuth script used in the OAuthAPISample conflicts with the map component's authentication configuration list.

  Summary: The map component clears all existing configurations from the ArcGISAuthenticationManager and then adds its list from the UI. If another script adds a configuration, the map component will destroy it.

• An error is logged after removing a component.

  Summary: Modifying values in the Map Creator UI prints the error messages in the Console window after removing a component from the game object.

Known issues

• A basemap that fails to load will cause all layers in the ArcGIS Map to fail to display.

  Summary: If you are using a basemap that fails to load (for example, a preset basemap that requires an API Key, but no API Key is set) then the loading of the ArcGIS Map will be interrupted and it will appear blank. This also impacts the SDK samples that use a preset basemap.

  Workaround: Be sure to set an API key when using one of the preset basemaps.

• View state report propagated warning messages

  Summary: When you subscribe to error messages by using the view state report, propagated error messages are logged in the Console although it's not an error.

  Workaround: No workaround available.

• Layer with non-standard metadata loading, position, and LOD tile issue

  Summary: Some layers which render correctly in other Esri products are not rendered or rendered in an incorrect position in Unity, or with incorrect LOD tiles, although the service is in the supported layer type and spatial reference.

  Workaround: Case by case. If you have this issue, provide the detail via support.

• Changes on the component not reflected in the Map Creator UI.

  Summary: After making changes to the component, the Map Creator UI does not automatically update with the new values.

  Workaround: Click on a different tab in the Map Creator UI to pull the new values from the component.

• The extent dimension values are incorrectly applied in the scene when the extent center is away from the Equator.

  Summary: When you set an extent in the area away from the Equator in an ArcGIS Map with a geographic coordinate system, the shape dimension is bigger than the values set for the extension.

  Workaround: No workaround available.

• One image tile layer is still visible in the Scene view window even after removing all during the editor mode.

  Summary: One image tile layer remains visible after removing all the image tile layers in the level.

  Workaround: Play the scene once or reload the scene.

• Setting opacity to scene layers has no effect.

  Summary: Opacity does not work if Unity material for the scene layer is opaque.

  Workaround: Change the scene layer material to the one that has transparency.

• Some parts of integrated mesh scene layers flash while navigating around the area.

  Summary: When elevation is enabled in the scene, some parts of the integrated mesh scene layers flash.

  Workaround: Disable the elevation.

• Image tiles flashing when the basemap is a vector tile layer.

  Summary: While navigating in the scene, several image tiles flash if the basemap is a vector tile layer.

  Workaround: Use an image tile layer as the basemap and add the vector tile layer as the first layer on top of the basemap with full opacity.

• The layer management popup of the Map Creator UI stays visible.

  Summary: The layer management popup of the Map Creator UI stays visible even after clicking outside of it.

  Workaround: Click again on the ⋮ icon in the layers panel.

• The layer management popup of the Map Creator UI is covered by other Unity Editor tabs.

  Summary: The layer management popup of the Map Creator UI is covered by other Unity Editor tabs and is not fully visible.

  Workaround: Adjust other tab sizes to display all layer management options.

• Not be able to deselect the original tiles or select new tiles while selecting a group of tiles in the Scene view.

  Summary: While selecting a group of tiles in the Scene view by holding the Shift key, transform.localPosition assign attempt for ... error message logged in the Console window. Once the errors come up, you cannot select anything else until you restart Unity, attempting to press play will cause Unity to crash.

  Workaround: No workaround available.

• The default layer opacity is set to 0 instead of 1 in the ArcGIS Map component.

  Summary: When you add the first array element in the Layers section or the ArcGIS Map component, the default layer opacity is set to 0 instead of 1.

  Workaround: Manually change the layer opacity value to make it visible after adding the row.

• Adding a new layer array row in the ArcGIS Map component duplicates the layer that is already added.

  Summary: When you add a new layer array element in the ArcGIS Map component, it duplicates the last row with its values.

  Workaround: Replace values with new values after adding the row.

• Generated normal maps have geometric patterns when the elevation is enabled.

  Summary: When an elevation is enabled, generated normal maps have geometric patterns and are visible on the surface.

  Workaround: No workaround available.

• Scene layer packages with non-ASCII characters in their file name or in the path cannot be loaded.

  Summary: When there are non-ASCII characters in the scene layer package name or the scene layer package is located in the path that contains non-ASCII characters, the layer cannot be loaded.

  Workaround: Rename the file or folder.

• Mesh collider/Terrain occlusion issue

  Summary: When using an integrated mesh layer that dips below the elevation, the terrain occlusion mechanism is not showing the elevation, but the collider still exists which in some small cases can make objects float above the integrated mesh.

  Workaround: No workaround available.