Release notes

Version 0.3.0 - September, 2021.

The ArcGIS Maps SDK for Unity Pre-release introduces the ability to access ArcGIS data sources within a scene in Unity to develop 3D and XR applications for a wide variety of devices and experiences.

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

Issues resolved

  • Integrated mesh scene layer lighting issue

    Summary: For some integrated mesh scene layers, the brightness of the surface doesn't match with the lighting direction.


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

Native geospatial placement

Native geospatial placement is required to support accurate geospatial placement of objects and intuitive camera control within a scene. With this release, ArcGIS Maps SDK for Unity delivers initial support for native geospatial placement with the High Precision Framework, which was developed by Unity and integrated within the ArcGIS Maps SDK. This means that global scenes now use a rebasing system and an ellipsoid model instead of a spherical model, which allows you to render large scale worlds and place GIS data more accurately by circumventing single precision issues with the default GameObject and Transform components. It also introduces changes to the relationship between the camera and the scene. Now the camera moves inside the scene instead of the scene and its contents moving towards the camera.

3D object scene layer attributes

The ability to work with 3D attributes is a feature that works with ArcGIS3DModelLayers to allow you to visualize the objects in the layer in a more meaningful way. 3D Object scene layers have attributes with values for each node. Depending on how the layer was authored, the cached attributes can have a variety of different information. For the 3D object scene layer technical information, see specifications in Esri GitHub.

Integrated mesh and 3D object scene layer v1.8 support

A new version of the Indexed 3D Scene Layer (I3S) specification for Scene Layers has been released. I3S specification version 1.8 is supported by ArcGIS Maps SDK for Unity and that includes Basis Universal Texture format in Khronos KTX2 standard. For more information about version 1.8 3D objects and integrated mesh profiles, visit Esri GitHub.

Note: gltf material and material transparency support are not added in this release yet.


  • ArcGISVisualLayer was removed so now all layers inherit directly from ArcGISLayer

  • ArcGISGlobalCoordinatePosition was renamed to ArcGISPosition

  • SpatialReference was added. Layers, Elevation, and Position have a SpatialReference

  • SetMaterialReference and SetAttributesToVisualize methods were added to ArcGIS3DModelLayer to support the 3d attributes.

  • In addition to these methods, new classes, VisualizationAttributeDescription, AttributeProcessor, AttributeProcessorEvent, and VisualizationAttributeType were also added to support 3d Attributes

Inspector UI

  • Layer type selector has been added to have corresponding result for each layer type
  • Layer URL or path is now editable after adding
  • Origin location section that syncs with ArcGIS Root component was added

Android deployment

A message will be logged to logcat when the app fails to load OpenSSL.

Known issues

  • 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 on Esri's Early Adopter website.

  • View state report propagated warning messages

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

    Workaround: No workaround available.

  • Scene layers will be loaded only when the layer ID is 0

    Summary: When a scene service has multiple layers within it, only the layer with an ID of 0 will be displayed. Scene layers with a URL that doesn't have a layer ID or that ends with /0 will be displayed.

    Workaround: Publish each scene layer separately and obtain the URL individually.

  • Tiles render inconsistently with multiple raster tile layers

    Summary: When there are more than eight raster tile layers visible in the viewport, tile composition becomes inconsistent. It is possible to have more than eight layers in your scene, although as soon as your viewport starts to have more than eight raster tile layers to display and there are changes in camera and/or layer visibility, the issue starts to occur.

    Workaround: No workaround available.

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.