I keep getting this
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)'
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]
Ahlundra:
I keep getting this
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)'
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]
Are you using assembly definitions in your project
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
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.
1 Like
tertle:
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.
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 =|
well, just changed the line to
report.AddMessage(LogType.Error, errorMessageBuilder.ToString(), " ");
hope it doesnt break anything lmao
Updating Burst package to 1.1.0 solved the issue for me
1 Like
indeed, gives a little warning but atleast it’s working for now =p
thanks arturio
WiLLyRS
September 6, 2019, 12:18pm
9
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