Release Notes v3.1

ARDK 3.1 features a number of small bug fixes and the launch of our Emoji Garden mini game sample. This sample demonstrates end to end flow for using Map, VPS, Shared AR in a single project.

Features/Fixes

• Fixed a scenario where a scene with a LightshipMeshingExtension component could crash if Initialize XR on Startup was disabled.
• Renamed Private Scans to Test Scans in the Geospatial Browser and the Niantic Wayfarer App.
• OcclusionPreferenceMode can now be set to “No Occlusion”, which keeps the OcclusionManager running and producing depth buffers but disables the occlusion effect.
• VPS-Activated Locations have been renamed to Public Locations.
• Shared AR is more performant for users in AMEA and APAC. On average, users in these regions should see a 100ms reduction in RTT. Users in North America (US Central) will continue to see similar performance as before. Clients will automatically route to the best region.
• When using SharedAR, all clients must use the same version of ARDK to join the same Room.
• The API callback RoomManagementService.GetOrCreateRoomAsync() is now deprecated. Instead, please use RoomManagementService.GetOrCreateRoomAsync(), which returns a Task instead.

Known Issues

• When using Emoji Garden, you must add your API license key to both the ARDK and Maps SDK sections. The sample will hang on the loading screen if the Maps API key is missing. (A warning will trigger if the ARDK API key is missing, but not for the Maps API key, so be careful!)
• Developers migrating Shared AR applications or samples from ARDK 3.0 to 3.1 should create a new Lightship API key to avoid potential compatibility issues with the new regional servers.