Unity-Technologies / UniteAustinTechnicalPresentation

Other
761 stars 192 forks source link

Issues with 2018.2.0b7 Beta #5

Open VR-Architect opened 6 years ago

VR-Architect commented 6 years ago

Downloaded and ran in 2018.2.0b7 beta and noticed:

- Read only asset Packages/com.unity.entities/Unity.Transforms/TransformInputBarrier.cs has no meta file.
- C:/Users/Brian/AppData/Local/Unity/cache/packages/staging-packages.unity.com/com.unity.entities@0.0.11/Unity.Entities.Editor/ExtraTypesProvider.cs(6,32): error CS0234: The type or namespace name `Build' does not exist in the namespace `UnityEditor.Experimental'. Are you missing an assembly reference?

Manifest.json

{
  "dependencies": {
    "com.unity.entities": "0.0.11"
  },
  "registry": "https://staging-packages.unity.com"
}

Using .NET 4.0

VR-Architect commented 6 years ago

Did a reinstall of packages and the Job and Package Manager menu items appeared. But error messages remained.

Did an upgrade of Entities to v0.0.12-preview and got these errors:

- C:/Users/Brian/AppData/Local/Unity/cache/packages/staging-packages.unity.com/com.unity.entities@0.0.12-preview.5/Unity.Entities/SerializeUtility.cs(28,73): error CS1644: Feature `out variable declaration' cannot be used because it is not part of the C# 6.0 language specification

- C:/Users/Brian/AppData/Local/Unity/cache/packages/staging-packages.unity.com/com.unity.entities@0.0.12-preview.5/Unity.Entities/SerializeUtility.cs(153,52): error CS1644: Feature `out variable declaration' cannot be used because it is not part of the C# 6.0 language specification

- C:/Users/Brian/AppData/Local/Unity/cache/packages/staging-packages.unity.com/com.unity.entities@0.0.12-preview.5/Unity.Entities/SerializeUtility.cs(153,78): error CS1644: Feature `out variable declaration' cannot be used because it is not part of the C# 6.0 language specification

So added the new incremental compiler to the manifest.json file

{
  "dependencies": {
    "com.unity.entities": "0.0.12-preview.5",
    "com.unity.incrementalcompiler": "0.0.42-preview.3"
  },
  "registry": "https://staging-packages.unity.com"
}

And this resulted a lot of errors saying bool1 type can't be found.

VR-Architect commented 6 years ago

Noticed this forum post regarding bool1 and created a file called bool1.cs with this code:

using System;

public struct bool1
{
    private byte Value;

    public static implicit operator bool1(bool b)
    {
        return new bool1() { Value = Convert.ToByte(b) };
    }

    public static implicit operator bool(bool1 b)
    {
        return b.Value == 1;
    }
}

Now have only one error left and no idea how to move forward: Internal error: Recursion detected while updating scripts (assembly name: Assembly-CSharp-Editor.dll)

Closed the editor and re-opened the project and all errors are now gone. Project ran

Hope this helps others out!

Scott VR Architect

VR-Architect commented 6 years ago

Well, spoke to soon. When Build and Run got a malware message from my anti-virus tool called BitDefender which blocked it:

C:\Users\Brian\AppData\Local\cache\packages\staging-packages.unity.com\com.unity.bur...\.Runtime\bcl.exe
C:\Windows\System32\conhost.exe

Of course, the blocking caused errors in the build:

Failed running C:\Users\Brian\AppData\Local\Unity\cache\packages\staging-packages.unity.com\com.unity.burst@0.2.4-preview.7\.Runtime\bcl.exe @C:\Users\Brian\AppData\Local\Temp\tmp4597fb13.tmp

stdout:
stderr:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Unity.Cecil, Version=0.10.0.0, Culture=neutral, PublicKeyToken=fc15b93552389f74' or one of its dependencies. The system cannot find the file specified.
   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)
UnityEditorInternal.Runner:RunManagedProgram(String, String) (at C:/buildslave/unity/build/Editor/Mono/BuildPipeline/BuildUtils.cs:45)
Unity.Burst.Editor.BurstAotCompiler:OnPostBuildPlayerScriptDLLs(BuildReport) (at C:/Users/Brian/AppData/Local/Unity/cache/packages/staging-packages.unity.com/com.unity.burst@0.2.4-preview.7/Editor/BurstAotCompiler.cs:141)
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()
VR-Architect commented 6 years ago

Guess I will stick with standard Unity for now and move to ECS when it matures.

ArchyInf commented 6 years ago

The recursion stems from UnityUpgrader not really upgrading some new stuff. I think it was PrefabUtility.GetPrefabParent. Just build in your api and fix UnityUpgradable warnings.

After that fix everything works. You should report your false positive virus case.

ArchyInf commented 6 years ago

Bcl.exe is the burst compiler, deactivating burst compilation in Jobs menu might work around it for now.