2019.4.20f1 Compiler Errors after importing the installer package

[ThanosRestas]

Describe the bug
After importing the recommended installer package from main I get compiler errors related to the BurstAotCompiler

Screenshots

• glTFast version : 2.0
• Unity Editor version : 2019.4.20f1

[De-Panther]

Had the same issues with Unity 2019.4.7f1.
It's a bug in the Unity Burst package.
Reported a bug to Unity - 1371912
Hope it'll get to their priority

[ThanosRestas]

Apparently I get similar bugs in 2020.2.3f1 too.

[De-Panther]

And if you update to a more recent version of burst?

[ThanosRestas]

And if you update to a more recent version of burst?

Same unfortunately :(

[atteneder]

@ThanosRestas Thanks for reporting!

I'm not having this error, so until the original problem is fixed we might figure out why it's not compiling for you, shall we?

What is your active build platform?
What packages are activated/installed in your project?

I'm using 2019.4.31f1 and Burst 1.4.11 with Standalone(macOS) as the active target. Here's the list of the packages:

    "com.atteneder.draco": "3.3.1",
    "com.atteneder.gltfast": "4.3.1",
    "com.atteneder.ktx": "1.1.1",
    "com.unity.burst": "1.4.11",
    "com.unity.ext.nunit": "1.0.6",
    "com.unity.ide.rider": "3.0.7",
    "com.unity.jobs": "0.2.10-preview.13",
    "com.unity.performance.profile-analyzer": "1.1.0",
    "com.unity.test-framework": "1.1.29",
    "com.unity.test-framework.performance": "2.8.0-preview",
    "com.unity.testtools.codecoverage": "1.1.0",
    "com.unity.ui.builder": "1.0.0-preview.17",
    "com.unity.modules.animation": "1.0.0",
    "com.unity.modules.imageconversion": "1.0.0",
    "com.unity.modules.imgui": "1.0.0",
    "com.unity.modules.jsonserialize": "1.0.0",
    "com.unity.modules.physics": "1.0.0",
    "com.unity.modules.physics2d": "1.0.0",
    "com.unity.modules.unitywebrequest": "1.0.0",
    "com.unity.modules.unitywebrequesttexture": "1.0.0"

Could you try and figure out if you still have the error when using a similar setup?
Also, whenever you install or up-/downgrade Burst, make sure to restart the Editor.

[De-Panther]

I think that in the middle of ths major versions, Unity added some platforms (new xbox, ps5...).
So in later versions of 2019.4 or 2020.2 it'll work, but on earliers it won't

[atteneder]

That would make sense! Too bad the Burst minimum required version doesn't reflect it out-of-the-box. A better error would avoid the confusion.

[ThanosRestas]

@atteneder Thanks for chiming in to help 😊. So :

Apparently on Unity version 2019.4.29f1 it works perfectly.

On Unity version 2020.2.3f1 the issue persists. This is the version I need to work on though so compatibility is a must.

The details you asked:

• Version: 2020.2.3f1
• Active Build: PC (although the final project I'm aiming to make will be on Android)
• Packages Installed from (manifest.json) :

{
  "dependencies" : {
    "com.unity.collab-proxy" : "1.3.9",
    "com.unity.ide.rider" : "2.0.7",
    "com.unity.ide.visualstudio" : "2.0.5",
    "com.unity.ide.vscode" : "1.2.3",
    "com.unity.test-framework" : "1.1.20",
    "com.unity.textmeshpro" : "3.0.1",
    "com.unity.timeline" : "1.4.5",
    "com.unity.ugui" : "1.0.0",
    "com.unity.modules.ai" : "1.0.0",
    "com.unity.modules.androidjni" : "1.0.0",
    "com.unity.modules.animation" : "1.0.0",
    "com.unity.modules.assetbundle" : "1.0.0",
    "com.unity.modules.audio" : "1.0.0",
    "com.unity.modules.cloth" : "1.0.0",
    "com.unity.modules.director" : "1.0.0",
    "com.unity.modules.imageconversion" : "1.0.0",
    "com.unity.modules.imgui" : "1.0.0",
    "com.unity.modules.jsonserialize" : "1.0.0",
    "com.unity.modules.particlesystem" : "1.0.0",
    "com.unity.modules.physics" : "1.0.0",
    "com.unity.modules.physics2d" : "1.0.0",
    "com.unity.modules.screencapture" : "1.0.0",
    "com.unity.modules.terrain" : "1.0.0",
    "com.unity.modules.terrainphysics" : "1.0.0",
    "com.unity.modules.tilemap" : "1.0.0",
    "com.unity.modules.ui" : "1.0.0",
    "com.unity.modules.uielements" : "1.0.0",
    "com.unity.modules.umbra" : "1.0.0",
    "com.unity.modules.unityanalytics" : "1.0.0",
    "com.unity.modules.unitywebrequest" : "1.0.0",
    "com.unity.modules.unitywebrequestassetbundle" : "1.0.0",
    "com.unity.modules.unitywebrequestaudio" : "1.0.0",
    "com.unity.modules.unitywebrequesttexture" : "1.0.0",
    "com.unity.modules.unitywebrequestwww" : "1.0.0",
    "com.unity.modules.vehicles" : "1.0.0",
    "com.unity.modules.video" : "1.0.0",
    "com.unity.modules.vr" : "1.0.0",
    "com.unity.modules.wind" : "1.0.0",
    "com.unity.modules.xr" : "1.0.0",
    "com.atteneder.gltfast" : "4.3.1",
    "com.atteneder.draco" : "4.0.0-preview.3"
  },
  "scopedRegistries" : [
    {
      "name" : "OpenUPM",
      "url" : "https://package.openupm.com",
      "scopes" : [
        "com.atteneder"
      ]
    }
  ]
}

[EDIT] The burst package seems to not be included here even though it's installed and can be seen inside the editor's package manager. I updated the burst package to the latest version from the package manager and now the manifest.json looks like this
(still facing the same compiler issues though):

{
  "dependencies": {
    "com.atteneder.draco": "4.0.0-preview.3",
    "com.atteneder.gltfast": "4.3.1",
    "com.unity.burst": "1.6.0",
    "com.unity.collab-proxy": "1.3.9",
    "com.unity.ide.rider": "2.0.7",
    "com.unity.ide.visualstudio": "2.0.5",
    "com.unity.ide.vscode": "1.2.3",
    "com.unity.test-framework": "1.1.20",
    "com.unity.textmeshpro": "3.0.1",
    "com.unity.timeline": "1.4.5",
    "com.unity.ugui": "1.0.0",
    "com.unity.modules.ai": "1.0.0",
    "com.unity.modules.androidjni": "1.0.0",
    "com.unity.modules.animation": "1.0.0",
    "com.unity.modules.assetbundle": "1.0.0",
    "com.unity.modules.audio": "1.0.0",
    "com.unity.modules.cloth": "1.0.0",
    "com.unity.modules.director": "1.0.0",
    "com.unity.modules.imageconversion": "1.0.0",
    "com.unity.modules.imgui": "1.0.0",
    "com.unity.modules.jsonserialize": "1.0.0",
    "com.unity.modules.particlesystem": "1.0.0",
    "com.unity.modules.physics": "1.0.0",
    "com.unity.modules.physics2d": "1.0.0",
    "com.unity.modules.screencapture": "1.0.0",
    "com.unity.modules.terrain": "1.0.0",
    "com.unity.modules.terrainphysics": "1.0.0",
    "com.unity.modules.tilemap": "1.0.0",
    "com.unity.modules.ui": "1.0.0",
    "com.unity.modules.uielements": "1.0.0",
    "com.unity.modules.umbra": "1.0.0",
    "com.unity.modules.unityanalytics": "1.0.0",
    "com.unity.modules.unitywebrequest": "1.0.0",
    "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    "com.unity.modules.unitywebrequestaudio": "1.0.0",
    "com.unity.modules.unitywebrequesttexture": "1.0.0",
    "com.unity.modules.unitywebrequestwww": "1.0.0",
    "com.unity.modules.vehicles": "1.0.0",
    "com.unity.modules.video": "1.0.0",
    "com.unity.modules.vr": "1.0.0",
    "com.unity.modules.wind": "1.0.0",
    "com.unity.modules.xr": "1.0.0"
  },
  "scopedRegistries": [
    {
      "name": "OpenUPM",
      "url": "https://package.openupm.com",
      "scopes": [
        "com.atteneder"
      ]
    }
  ]
}

[ThanosRestas]

After tinkering around for a while, updating my project to version 2020.3.20f1 works perfectly and also supports the rest of my workflow. Probably related to what @De-Panther mentioned here:

I think that in the middle of ths major versions, Unity added some platforms (new xbox, ps5...). So in later versions of 2019.4 or 2020.2 it'll work, but on earliers it won't

Still the issue exists on some Unity versions so I guess it can be noted on the repo or something ? I guess the issue can be closed for now but I wouldn't want anyone else to face the issue I was having and lose his precious time from creating ! 😅

[atteneder]

@ThanosRestas Glad you got it working!

Upgrading to the most recent LTS (of the series you're working with) is a good advice in general!

While I get your point (of avoiding the confusion), I'm not convinced it is up to glTFast. For the 2019 series i could raise the minimum required version (with the downside that users of older versions silently won't get updates anymore). For 2020 or 2021 series I don't even know how to raise the build version requirement.

Imho this has to be solved by Burst. Users who search for this error (on this GitHub page) should be able to find this issue and the solution it offers.

[De-Panther]

Version 2019.4.7 has the issue, needs to check which 2019.4 version introduced those platforms

[atteneder]

@De-Panther I rushed and misread the information from the fogbugz issue, believing 2019.4.7 solved this :/

I tried to find out which exact version would be correct (by scanning the release logs), but found nothing.

I'm leaning towards raising unityRelease to whatever the current LTS is in the next minor release (4.5.0).