Search Unity

error trying to add entities package to a new project

Discussion in 'Entity Component System' started by Ahlundra, Jul 1, 2019.

  1. Ahlundra

    Ahlundra

    Joined:
    Apr 13, 2017
    Posts:
    47
    I keep getting this

    Code (CSharp):
    1. Library\PackageCache\com.unity.burst@1.0.4\Editor\BurstAotCompiler.cs(638,32): error CS7036: There is no argument given that corresponds to the required formal parameter 'exceptionType' of 'BuildReport.AddMessage(LogType, string, string)'
    2.  
    and I have no Idea what's doing this, just made a new project and added the mathematics and Entities package

    By itself it also adds burst and jobs packages so I shouldnt be missing anything else, right?
    seems like an error inside the package itself

    i'm running the latest version of unity [3.0a7]
     
  2. RoughSpaghetti3211

    RoughSpaghetti3211

    Joined:
    Aug 11, 2015
    Posts:
    1,705
    Are you using assembly definitions in your project
     
  3. Ahlundra

    Ahlundra

    Joined:
    Apr 13, 2017
    Posts:
    47
    it's a blank project, theres nothing on it yet aside what unity adds by itself
    that means the default camera and a light object

    literally just made a new 3D project and added the packages
     
  4. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    This is an issue with the latest 2019.3 versions, they changed syntax of BuildReport.AddMessage

    Use 2019.2 instead or manually import the burst package and fix up the code. I'd assume next burst version should fix this.
     
    Ahlundra likes this.
  5. Ahlundra

    Ahlundra

    Joined:
    Apr 13, 2017
    Posts:
    47
    Thanks tertle, but would I lose access to the new function of using native arrays with the mesh render? That's the only reason i've updated...

    if that's the case seems like i'll be waiting a little more =|
     
  6. Ahlundra

    Ahlundra

    Joined:
    Apr 13, 2017
    Posts:
    47
    well, just changed the line to
    Code (CSharp):
    1. report.AddMessage(LogType.Error, errorMessageBuilder.ToString(), " ");
    hope it doesnt break anything lmao
     
  7. DevArturio

    DevArturio

    Joined:
    Jan 5, 2019
    Posts:
    2
    Updating Burst package to 1.1.0 solved the issue for me
     
    Ahlundra likes this.
  8. Ahlundra

    Ahlundra

    Joined:
    Apr 13, 2017
    Posts:
    47
    indeed, gives a little warning but atleast it's working for now =p
    thanks arturio
     
  9. WiLLyRS

    WiLLyRS

    Joined:
    Jul 4, 2012
    Posts:
    8
    How to do so? I've added the burst package 1.1.0 to the manifest.json but it can't find it

    EDIT: nvm, i've updated it with the package manager! Thanks for the solution