Skip to main content
Version: 1.0

Known Issues for VR/MR

There are currently a couple of known issues that may affect the development workflow. These are known issues and will be tackled in future releases of the Unity package or the Snapdragon Spaces Services runtime.

If an issue is not present, check the overall SDK Known Issues.

Gradle Build Issue​

In some instances, adding a custom controller archive might lead to Gradle caching errors. In that case, removing the temporary Gradle project folder generated in the project folder under Temp > gradleOut might resolve the issue.

OpenXR Plugin Issue​

Using Unity's OpenXR plugin version 1.9.1 with Snapdragon Spaces causes a memory leak leading to undefined behavior. Make sure to use the version of the OpenXR plugin set by the Snapdragon Spaces plugin as a dependency.

AR Raycast Hit reports wrong Trackable ID on success​

The ARRaycastHit.trackableId field will always return the trackableId of 0-0 as the session-unique identifier for the trackable that was hit.

AR Raycast Manager added automatically​

With XRIT 2.5.2, if there is an XR Raycast Interactor in the scene, it will programmatically add an AR Raycast Manager to the XR Origin independently from the variable EnableARRaycasting being set to true or false. This will enable Spatial Meshing when this or Plane Detection features are enabled in the Open XR settings. This could potentially result in a reduction of performance.

AR Mesh Manager Properties​

The AR Mesh Manager component has properties that are not supported by the Snapdragon Spaces Unity package's subsystem implementation. Attempting to use any of the unsupported properties will display warnings when a build is run and the Spatial Meshing feature is enabled.

AR Camera Manager and AR Camera Background Issues​

Enabling the AR Camera Manager in a scene will create a connection to physical cameras to retrieve information about their availability. Moving back and forth between scenes with the AR Camera Manager enabled might affect that connection negatively and cause unexpected results, such as application freezes. Consider disabling the AR Camera Manager where it is not needed.

If an AR Camera Background component is enabled, rendering issues such as a frozen image may be visible in certain devices once the ARCameraManager.frameReceived event is invoked. It is recommended to disable this component to ensure that Camera Frame Access behaves correctly on all devices.

Using video capture or streaming services simultaneously with the Camera Frame Access feature may lead to rendering artifacts or unhandled exceptions when reading image data through XRCpuImage.GetPlane(int). It is recommended to handle both YUY2 and Y'UV420sp frame formats in the application, as YUY2 may be available instead of Y'UV420sp in these cases.

Play in Editor Known Issues​

Check the Play in Editor Setup Guide page for information about how to configure a project to use play in editor effectively. See the Unity documentation on using the XR Simulation provider from AR Foundation for further information on how to use XR Simulation.

Memory Leak in Camera Access Simulation​

When playing in the editor and using the XR Simulator provider from AR Foundation, a memory leak can occur. This memory leak is simulation specific and was fixed in version 5.1.4 of the AR Foundation package.

AR Mesh Manager causes a Crash when Normals are not enabled​

When playing in the editor and using the XR Simulator provider from AR Foundation, the AR Mesh Manager can cause a crash when normals are not enabled. Upgrade to version 5.1.4 of the AR Foundation package, or enable normals in the editor.

QR Code Tracking Subsystem is not loaded in Simulation​

There is no QR Code Tracking Simulation subsystem defined for the QR Code Tracking feature. If a check must be made which depends on the QR Code Tracking subsystem running, it is suggested to bypass those checks in the editor.

SpacesQrCodeManager arQrCodeManager;

...
    
bool CheckSubsystem()
{
#if UNITY_EDITOR
    return arQrCodeManager.subsystem?.running ?? false;
#else
    return true;
#endif
}

Saving has no effect - ScriptableSingleton Warning​

Saving has no effect. Your class 'UnityEditor.XR.Simulation.XREnvironmentViewManager' is missing the FilePathAttribute. Use this attribute to specify where to save your ScriptableSingleton.

If this message appears when playing in editor using the XR Simulator provider from AR Foundation, upgrade to version 5.1.2 of the AR Foundation package.