Is it temporarily removed? Can I still download via editing the packages json?
Added it via json but apparently, it didn’t work well. It showed up in packages window but I’m getting about 8 compile errors from the package: C:/ProgramData/Unity/cache/packages/staging-packages.unity.com/com.unity.burst@0.2.1/Editor/BurstReflection.cs(19,67): error CS0246: The type or namespace name `AssembliesType’ could not be found. Are you missing an assembly reference?
1 Like
I might be mistaken but I believe you have to use a special Beta version found here in order to fix those compilation errors. Hope that helps! 
1 Like
Oh, I am using b12 from the official download page because otherwise, the LWRP (rendering pipeline) doesn’t compile. LOL, so apparently I have to choose between LWRP and ECS 
Thank you. It is a bit confusing because technically they both are b12
It was unfortunate that the special build that had ECS stuff in it was labelled beta 12, and the actual beta 12 is missing that stuff.
I believe this situation may be rectified by beta 13.
2 Likes
I get this on b12 and b13. Was so looking forward to testing out examples 
1 Like
@Rennan24 How are you enjoying ECS so far? Also, did you have to do any extra setup with the ECS build?
By the way, Entities package won’t show up in the Packages window on any version until it is added. To add it you need to have all these lines in your ProjectFolder>Packages>manifest.json
{
“dependencies”:{
“com.unity.entities”:“0.0.11”
},
“testables”: [
“com.unity.collections”,
“com.unity.entities”,
“com.unity.jobs”
],
“registry”: “https://staging-packages.unity.com”
}
And of course, the Unity editor downloaded specifically from here: https://beta.unity3d.com/download/ed1bf90b40e6/public_download.html
Not sure about b13, haven’t tested.
1 Like
@illinar Thank you! That fixed the issue
Realizing that there are two beta 12’s after spending hours pulling my hair out… you know, at least this is a rare moment where it turns out I’m not stupid. Why would they do such a thing? It’s already such a huge learning curve.
Anyhow, if this hasn’t been fixed in beta 13, does that mean that there is no beta 13 which supports ECS?
If I have both beta 12s on my machine, what will this look like to and inside Unity Hub?
Seriously grumpy about all of this.
Nope. No b13 for ETC. I have downloaded and found it the hard way.
Sounds like it will make it to beta 14:
2 Likes
Oh, thank fuck. I am looking forward to the day when technology allows us to have software with support for two experimental features at once.
2 Likes
For the record, I’m sympathetic to them having an ECS branch.
I’m just thoroughly unimpressed that they:
- Call them both “beta 12”
- Don’t put “if you want to try ECS you need to download this specific build at this link that is meaningfully different from the current beta build that you can access via Unity Hub” in comically large bold-face text at the top of the forum, on the Youtube videos and in the readme.md files on GitHub.
Like, seriously: wtf? They can create a modern wonder of software engineering but they can’t rename an installer “UnityDownloadAssistant-2018.1.0b12-ECS”?
5 Likes
I have same issue like this,did you find solution?
This post is ancient in terms of ECS.
Which version of Unity you work with?
if you don’t get the package to show up in package manager now, it implies you haven’t enabled the preview packages on it. Unity stopped showing them by default. To enable them, look at the package managers top bar, there’s “advanced” dropdown right next to search, you should be able to enable preview packages from that.
2 Likes
i solved this,thank you all
1 Like