Skip to main content

Common Issues - Build Errors

This page is dedicated to common issues surrounding a Luna build not being created. If you are experiencing an issue that does not relate to builds consider looking at one of the other pages in this section, which are also listed here.

Make sure to Update Playable!
A lot of times issues can be fixed by simply updating your plugin to the latest version, please make sure to check you are on the latest release version before looking further into this section. More info on how to do this here

Failed to combine glyphs error shown in console#

This is could be due to a missing default characters in the Font settings tab.

Possible solutions:

  • Make sure that some characters are added to the Alphabet field at the top of the Fonts tab.
  • If you have some non-Latin fonts in your project which are included in the Luna build. You can add characters by using the 'Per-font settings' section. Click on the ttf file and add the non-Latin characters at the bottom.
  • To be sure that it's some font settings not getting applied which is causing the build error, try to exclude the font files from the project and re-build.

X variable default value is unassigned or Never used errors#

Possible solution step-by-step:

  1. Open the folder containing the Luna Playable Plugin
  2. Navigate to pipeline/templates/LunaCompiler/Scripts
  3. Open up Scripts.csproj.template
  4. Where it says <NoWarn>CS0626</NoWarn> replace it with <NoWarn>CS0626;CS7036;CS0649;CS0169;CS0414</NoWarn>


ArgumentException: Getting control 0’s position in a group with only 0 controls when doing repaint#

This could possibly be due to corrupt memory in Unity.

Possible solution:

  • Restart Unity. If that doesn’t work, try to restart PC / Mac.

Can’t compress image#

This could be because you are trying to compress a lightmap in Luna with PNG-32 compression.

Possible solution:

  • Use a different compression, such as PNG-8 (You will lose transparency when not using PNG-32).
  • Enable “sRGB (Color Texture)“ on the lightmap textures.

Luna does not compile, no errors being thrown#

This could be because you are using unsupported C# code that we cannot translate to JavaScript. This is because Luna uses Bridge.NET to transpile JS to C#, and Bridge currently only supports up to C# 7.0.

Possible solution:

  • You will need to refactor your code so that it instead uses C# features from C# 7.0 and previous. We have listed workarounds for some of the more commonly used unsupported C# features here.

Having assets with Asset Bundle labels causes Luna build failure#


Addressable bundle #0 contains multiple assets: x. y, z    at _0x45f89a.<computed>.computeAssetBundleLayout ASSETS_PROCESS    at _0x46868a.action [USER PACKAGE FILE PATH][ Error ] $Assets processing failed

Possible solution:

  • Set Asset Bundle label to 'None' for those assets.

MAP enum causing errors in build#

This is likely due to the fact that 'Map' is a keyword in Bridge.NET, subsequently causing conflicts.

To find out what other keywords to avoid using click here.

Possible solution:

  • Change the name of the enum (or class/variable) to something other than 'Map'.