UWP build failing - burst compiler not running

Hi everyone

I'm trying to build my project for UWP but I get the errors in the attached images.
I'm using Unity 2018.3.0b6 with ECS 0.0.12preview16 and IL2CPP as scripting backend.
The build completes successfully and works in all the scenes that don't use entities or systems (the introduction for example) but as I load the main scene (with entities and systems) everything is black....which is kind of strange since it works perfectly in the editor

Thanks for your help

 

This may have changed, but as far as I'm aware burst currently only works with

- Windows
- MacOS
- Linux
- Xbox One
- PS4
- Android (ARM v7 and v8+)
- iOS (ARM v7 and v8+)

at the moment

 

I have the weird feeling that UWP is not a priority Yet, if it does not run with UWP it means that it cannot run on **any** Microsoft VR visor, nor Hololens, where performance is more critical than in other platforms.

 

Do you need anything else that is not in the attached screenshots?

 

As previously noted, the build succeeds but then all the scenes with ECS are not working in the build so we can visualize the non ECS scenes but the ECS scenes are not working. We attached below the error messages Unity outputs. They are the same we get when we compile the ECS example scenes.

Failed running D:\Projects\Thesis\Library\PackageCache\com.unity.burst@0.2.4-preview.31\.Runtime\bcl.exe @C:\Users\ERICAS~1\AppData\Local\Temp\tmp45eafcd2.tmp

stdout:
stderr:
'x86-64' is not a recognized processor for this target (ignoring processor)
'+fxsr' is not a recognized feature for this target (ignoring feature)
'+mmx' is not a recognized feature for this target (ignoring feature)
'+sse' is not a recognized feature for this target (ignoring feature)
'+sse2' is not a recognized feature for this target (ignoring feature)
'+x87' is not a recognized feature for this target (ignoring feature)
'x86-64' is not a recognized processor for this target (ignoring processor)
'x86-64' is not a recognized processor for this target (ignoring processor)
'+fxsr' is not a recognized feature for this target (ignoring feature)
'+mmx' is not a recognized feature for this target (ignoring feature)
'+sse' is not a recognized feature for this target (ignoring feature)
'+sse2' is not a recognized feature for this target (ignoring feature)
'+x87' is not a recognized feature for this target (ignoring feature)
'x86-64' is not a recognized processor for this target (ignoring processor)
'x86-64' is not a recognized processor for this target (ignoring processor)
'x86-64' is not a recognized processor for this target (ignoring processor)

UnityEngine.Debug:LogError(Object)
UnityEditorInternal.Runner:RunProgram(Program, String, String, String, CompilerOutputParserBase) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:128)
UnityEditorInternal.Runner:RunManagedProgram(String, String, String, CompilerOutputParserBase, Action`1) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:73)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@0.2.4-preview.31/Editor/BurstAotCompiler.cs:220)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

Exception: D:\Projects\Thesis\Library\PackageCache\com.unity.burst@0.2.4-preview.31\.Runtime\bcl.exe did not run properly!
UnityEditorInternal.Runner.RunProgram (UnityEditor.Utils.Program p, System.String exe, System.String args, System.String workingDirectory, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:130)
UnityEditorInternal.Runner.RunManagedProgram (System.String exe, System.String args, System.String workingDirectory, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser, System.Action`1[T] setupStartInfo) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:73)
Unity.Burst.Editor.BurstAotCompiler.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) (at Library/PackageCache/com.unity.burst@0.2.4-preview.31/Editor/BurstAotCompiler.cs:220)
UnityEditor.Build.BuildPipelineInterfaces.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:452)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

@Tautvydas-Zilys I tried creating a new (empty) project on both 2018.3.b6 and b7 and installing only the Entities package 0.0.12preview16. I switched the platform to uwp (IL2CPP scripting backend) and tried to build but I still get the following errors:


Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Burst.Backend.StandardCompilerBackend.WriteModuleObject(TargetMachine targetMachine, Module module, StringBuilder filename)
at Burst.Backend.ChainCompilerBackend.WriteModuleObject(TargetMachine targetMachine, Module module, StringBuilder filename)
at Burst.Compiler.IL.Aot.AotCompiler.Link(Module module, AotCompilerOptions compilerOptions)
at Burst.Bcl.Program.Main(String[] args)

Failed running D:\Projects\ECSTestb6\Library\PackageCache\com.unity.burst@0.2.4-preview.31\.Runtime\bcl.exe @C:\Users\ERICAS~1\AppData\Local\Temp\tmp7f1bf3b8.tmp

stdout:
stderr:

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Burst.Backend.StandardCompilerBackend.WriteModuleObject(TargetMachine targetMachine, Module module, StringBuilder filename)
at Burst.Backend.ChainCompilerBackend.WriteModuleObject(TargetMachine targetMachine, Module module, StringBuilder filename)
at Burst.Compiler.IL.Aot.AotCompiler.Link(Module module, AotCompilerOptions compilerOptions)
at Burst.Bcl.Program.Main(String[] args)

UnityEngine.Debug:LogError(Object)
UnityEditorInternal.Runner:RunProgram(Program, String, String, String, CompilerOutputParserBase) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:128)
UnityEditorInternal.Runner:RunManagedProgram(String, String, String, CompilerOutputParserBase, Action`1) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:73)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at Library/PackageCache/com.unity.burst@0.2.4-preview.31/Editor/BurstAotCompiler.cs:220)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

Exception: D:\Projects\ECSTestb6\Library\PackageCache\com.unity.burst@0.2.4-preview.31\.Runtime\bcl.exe did not run properly!
UnityEditorInternal.Runner.RunProgram (UnityEditor.Utils.Program p, System.String exe, System.String args, System.String workingDirectory, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:130)
UnityEditorInternal.Runner.RunManagedProgram (System.String exe, System.String args, System.String workingDirectory, UnityEditor.Scripting.Compilers.CompilerOutputParserBase parser, System.Action`1[T] setupStartInfo) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:73)
Unity.Burst.Editor.BurstAotCompiler.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) (at Library/PackageCache/com.unity.burst@0.2.4-preview.31/Editor/BurstAotCompiler.cs:220)
UnityEditor.Build.BuildPipelineInterfaces.OnPostBuildPlayerScriptDLLs (UnityEditor.Build.Reporting.BuildReport report) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildPipelineInterfaces.cs:452)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

@Tautvydas-Zilys I made a very simple project with one cube rotating. In one scene the cube is still, in the other one it rotates with ECS. Press 0 to switch between the two. If you play it in the editor everything works fine. If you generate the UWP, install it and play it, when you switch to ECS it crashes. I'm using Unity 2018.3.0b7 and ECS 0.0.12preview16.

 

Any update on this?

 

We are building for x86 and x86-64 (the HoloLens and microsoft headsets) so if you can send us a package to make it work or make it available ASAP (by Monday? would be wonderful and I would be eternally grateful

 

@xoofx do you have any updates on the release of the package?
I'm having the same issue with the latest beta (2018.3.0b8) so I assume I should be waiting for a new ECS package, correct?

 

Any update? It looks like nothing is still working. So no building for *any* Microsoft visor if you use ECS.

 

Any update?

 

Updates about this? We are quite desperate since we cannot build the ecs project for any Microsoft visor (not asus not hololens)

 

Here is my build IL2CPP log.

1 Deleted VS 2017
2 Reinstalled it from Unity Installer
3 Installed all UWP modules from VS 2017 Installer

 

Microsoft SDKs directory and Windows Kits one are exist



All available Libs installed too. These libs all have Kernel32.lib for both x86 and x64. I spent a day to find out whats wrong, but have no any success result

 

Hi! After a half of day of searching the problem I found that it is need to be installed all Windows SDK packages in Visual Studio. Now the burst compiler is working for Mono backend! But for IL2CPP there are still some problems. Here is a IL2CPP build log info:

 

Hello. I'm trying to build UWP project for hololens, and have issue with burst.
When i add burst in package manager - all fine in editor, but error when try to build.
tested in empty project
unity 2018.4.14f
empty UWP project with empty scene - build is going
when add burst - error.

 

.Net

 

same error.
why shouldn't it work on .net?
I saw the messages above, from 2018, the guys tried to add a burst on hololens (holotoolkit requared .net backend, i think they used it at that time).

 

Can somebody tell me if DOTS works on HoloLens 2?
I don't have a device yet but I believe it is ARM based.

 

Just tried with Burst 1.3.6 in Unity 2020.1.0b5 it compiles with default scene. But if use other features got:

Burst.Backend.CompilerBackendException: Unable to find sleef function `Sleef_fmodd4_neon, Sleef_fmodd2_neon, Sleef_fmod_neon, Sleef_fmodd4_, Sleef_fmodd2_, Sleef_fmod_`

   at Burst.Bcl.BclApp.CompileAndLink(List`1 libraryCompilationRequests)

   at Burst.Bcl.Program.BuildTheThing(BclOptions options, Stopwatch& individualTimer)

   at Burst.Bcl.Program.Main(String[] args)

 

No problem! Do you need some sample code? One thing i found was playing with the settings. I could get the error to change. From listing these:

`Sleef_fmodd4_neon, Sleef_fmodd2_neon, Sleef_fmod_neon, Sleef_fmodd4_, Sleef_fmodd2_, Sleef_fmod_`

To these:

Sleef_cinz_fastfmodd4_u3500neon, Sleef_cinz_fastfmodd2_u3500neon, Sleef_cinz_fastfmod_u3500neon, Sleef_cinz_fastfmodd4_u3500, Sleef_cinz_fastfmodd2_u3500, Sleef_cinz_fastfmod_u3500, Sleef_cinz_fmodd4_neon, Sleef_cinz_fmodd2_neon, Sleef_cinz_fmod_neon, Sleef_cinz_fmodd4_, Sleef_cinz_fmodd2_, Sleef_cinz_fmod_`

Using different [BurstCompile(FloatPrecision.Low,FloatMode.Fast)] and [BurstCompile(CompileSynchronously = true)] settings seemed to change the error output. The later Burst 1.3.6 gave better error messages. But I think the problem has been around since 1.2.0 but that is a big assumption as specifics of the error were not given back then.