Skip to main content
Version: 0.23.2

Known Issues for Unreal Engine

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 Unreal Engine plugin or the Snapdragon Spaces Services runtime.

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

Spatial Anchor Backwards Compatibility Issue​

For apps built with plugin version 0.12.1 and lower, anchors are incompatible with Snapdragon Spaces Services version 0.13.0 and higher. You will need to compile your app with plugin version 0.13.0 or higher to avoid a crash when destroying an anchor.

Reset Position​

Resetting the map position on map load is currently not working as expected.

Unreal Editor Startup Issue​

Some firewalls could prevent the Unreal Editor from starting up correctly. A way to fix the issue could be by renaming the CrashReportClientEditor.exe to something else in the Unreal Editor's install path under Engine/Binaries/Win64.

Rendering Issues​

Widgets Performance Issue​

When the app is deployed with the default Development configuration selected, the framerate and performance decreases heavily when looking at world space UI (widgets) on the Viewer. Unfortunately, the root cause of this issue is unknown. When encountering issues with widgets, the Shipping configuration should be selected instead.

Crash When Using Vulkan with Mipmapping​

Building Snapdragon Spaces applications that use mipmapping with Vulkan will result in a crash. Disable generating mipmaps by setting the Mip Gen Settings dropdown to NoMipmaps in the texture settings under Level of Detail.

Stereo Layer​

Rapidly changing visibility of a stereo layer component will result in a crash for shipping builds on Vulkan.

AR System Issues​

Crash on App Startup​

Starting an AR Session on the first frame of the application (eg. On initial map's Begin Play) will crash in Unreal Engine 5.0. Build the application in the Shipping configuration or use a different engine version to prevent this.

Crash When Unlocking the Phone​

Unlocking the phone while having an AR Session running will crash in Unreal Engine 5.0. Build the application in the Shipping configuration or use a different engine version to prevent this.

Passthrough Issues​

UE4.27​

In UE 4.27, transparent materials that are not rendered over an opaque material will disappear. This is due to UE OpenXR plugin limitations.

UE5.0 and Higher​

In UE5.0 and higher, every object will be alpha-blended with the passthrough rendering in the background. This is due to UE OpenXR plugin limitations.

UE5.0 Known Issues​

Crash on Resume​

Applications will crash after a power suspend and resume action due to an assertion thrown by the engine. This has been fixed and no longer occurs in applications built with Unreal Engine 5.3.

Controllers in VR Devices​

The response of the controller triggers and buttons on VR devices are not 100% accurate for the button press. This has been fixed and no longer occurs in applications built with Unreal Engine 5.3.

UE5.3 Known Issues​

Controllers​

The response of the buttons of the controllers on VR devices and the host controller on AR devices, are not working with Snapdragon Spaces Services 0.18.0.