Unity 2018.2 beta 1 and ECS

Unity Engine
,
1

Hi.

I just tested to set up the ECS system with the new beta. Updated the maifest file and changed .net version.
I got this error message. Is there a different version of the ecs package in the manifest file needed?

From now. will improvements to the ECS and Job system be in 2018.2 betas or updates to 2018.1 ?

C:/ProgramData/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?

Lennart

2

I got this too. I think they moved Build.Player out of Experimental namespace which broke it.

I fixed this by navigating to folder C:\ProgramData\Unity\cache\packages\staging-packages.unity.com\com.unity.entities@0.0.11\Unity.Entities.Editor and changed ExtraTypesProvider.cs to not be read-only. Then I just changed the line 6 to:

using UnityEditor.Build.Player;

instead of:

using UnityEditor.Experimental.Build.Player;
9 Likes
3

Thanks.

replaced with this to not break my 2018.1 b12 project.

#if UNITY_2018_2_OR_NEWER
using UnityEditor.Build.Player;
#else
using UnityEditor.Experimental.Build.Player;
#endif
8 Likes
4

That did it… Thank you!
The issue is the project. The build has indeed been moved out of experimental, but the project is still looking for experimental. Should be updated in github.

5

I can confirm the same issue on Mac starting with a new project, changing .NET version, and updating the manifest.

The same warning is reported and updating ExtraTypesProvider.cs as provided by @rz_0lento patches it. The location of this file on Mac is in your user Library/Unity/cache/… (the rest of the path) directory in case anyone else runs into this.

6

Which exact JSON you guys have in your manifest? I am getting way more exceptions

Edit:
I forgot to set Scripting Runtime Version to .Net 4.x. Now it’s working

7

We released a new version of the samples and packages today which includes a fix for the namespace issue. So no more modifications required for that.
You can check out the details in this thread:

1 Like
8

I don’t get it. What do we do to fix this? The file is readonly so I can’t edit its contents.

9

You haven’t needed to fix this manually for anything but the old version that was broken with 2018.2 on May. Try any recent version and they work just fine with 2018.2.