Troubleshooting the Embedded Linux Unity Editor

Solve the common issues that might occur when using the Embedded Linux Unity Editor.

Read time 1 minute

Last updated 10 days ago

This page lists the common problems that might occur when using the Embedded Linux Unity Editor.

The Player build fails with an error

When exporting the Unity project, the following error appears:

No EmbeddedLinux Burst Support on X86/Arm32 architecture

. Disabling Burst in Settings and removing it from the project doesn't fix the issue because another package has a dependency on it.

Burst isn't supported on 32-bit Embedded Linux platforms. To prevent facing the error, you can disable Burst by starting the Unity Editor with the

--burst-disable-compilation

argument.

Starting the player on the target device fails with: SDL

Error: wayland,x11 not available

although Wayland is available.

This error might occur due to one of the following reasons:

The Wayland library isn't located by SDL2. Make sure that the Wayland library is locatable by
```
dlopen
```
from the player application.
Unity requires at least Wayland version 1.18. Because some systems have only version 1.16 or lower available, ensure to check that at least Wayland version 1.18 is supported on the target device.
The connection to the Wayland display fails. Make sure the Wayland environment is properly set up.

Multisample Anti-aliasing (MSAA) is known to cause rendering issues on i.MX8 Embedded Linux devices.

To avoid rendering issues on i.MX8 devices, disable MSAA in your project's quality settings. Go to Edit >

Project Settings

> Quality, then set Anti Aliasing to Disabled.