since @xoofx is enjoying his holidays, I am opening this thread as a reminder one of our users experiences hard crashes on his PhenomII. The dump files should help.
If you can switch to a burst version below the 1.1.x series, then this will work around the broken cpu detection which is causing issues like this, otherwise, we have a fix, but still no eta on a new package.
We tried to downgrade to 1.0.4 but we're getting this compile error: 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) I'm using Unity 2019.2.1. Is there any way that we can fix this? Edit: I hacked BurstAotCompiler. Changed the following line: Code (CSharp): // From this report.AddMessage(LogType.Error, errorMessageBuilder.ToString()); // To this report.AddMessage(LogType.Error, errorMessageBuilder.ToString(), "Don't know what to specify here");
Unfortunately, I'm now getting these errors: Unexpected exception System.IO.FileNotFoundException: Could not load file or assembly 'Smash, Version=0.3.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. File name: 'Smash, Version=0.3.0.0, Culture=neutral, PublicKeyToken=null' at Burst.Compiler.IL.Jit.JitCompiler+CachedMethodKey..ctor (System.String methodFullName, Burst.Compiler.IL.Jit.JitOptions options) [0x00007] in <3179d4839c86430ca331f2949f40ede5>:0 at Burst.Compiler.IL.Jit.JitCompiler.CompileMethod (Mono.Cecil.MethodReference methodReference, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x0001f] in <3179d4839c86430ca331f2949f40ede5>:0 at Burst.Compiler.IL.Jit.JitCompilerService.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x002ce] in <3179d4839c86430ca331f2949f40ede5>:0 While compiling job: System.Void Unity.Jobs.IJobParallelForExtensions/ParallelForJobStruct`1<Unity.Entities.GatherChunks>::Execute(T&,System.IntPtr,System.IntPtr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,System.Int32)
Temporary workaround would be to comment out the above line in the package. this should remove that blocker.
I don't think this can be done successfully with a workaround. Modifying local code would imply that I should create my own local version of burst to share the change with my colleagues, however this would mean, as far as I understand, that other unity packages will not find the burst dependency anymore.
You only should move burst from package cache to Packages folder (where manifest.json) other packages will find dependency correct.
it seems there are problems, but we are testing more com.unity.physics@0.1.0-preview\Unity.Physics\Collision\Colliders\Physics_TerrainCollider.cs(225,24): error: Unexpected error while processing instruction IL_003c: call System.Void Unity.Mathematics.int4::.ctor(System.Int32,System.Int32,System.Int32,System.Int32) args(IL_003c, IL_000b, IL_0019, IL_002a, IL_003b). Reason: The argument System.Int16 for the constructor IL_003c: call System.Void Unity.Mathematics.int4::.ctor(System.Int32,System.Int32,System.Int32,System.Int32) args(IL_003c, IL_000b, IL_0019, IL_002a, IL_003b) is not supported by burst edit: it seems it was an one off issue, keeping an eye on it
The compiling error seems to pop up randomly, therefore there is something wrong I am not sure I can rely on the downgrade. Edit: for safety we are going to upgrade again, hence the Phenom issue is still open for us.
We will release a preview version (1.1.3-preview.1) today or tomorrow that should fix the issue for Phenom