Official Entities 0.17 changelog

Two years from now Unity emerges from complete silence and are going to suddenly delete all posts on the DOTS forum and post a singular new one:

> DOTS 1.0 Released.

 

One amazing thing is that no critical issue seem to have surfaced between January and now, so the whole DOTS core looks pretty stable to me. We have much more problems with HDRP than DOTS (where we actually have nothing in the way of our consoles submissions).

Looks like there are issues, but also looks like they get fixed for 0.20

 

Can't wait for 0.20.0

 

Entities 0.20.0 confirmed!!!

 

Do you know there are no plans for a new DOTS version this year yes? So it's probably will be 0.25 or even 0.30 when it at last comes.

 

I was being deeply sarcastic.

 

Where this conclusion comes from? I remember only one official statement about incompatibility with new 2021.x unity, but no official information about new Entities versions.

 

It's just my estimation. As you pointed out there is no additional info besides "there will be no update in this year" and "stay in current LTS".

 

From https://forum.unity.com/threads/notice-on-dots-compatibility-with-unity-2021-1.1091800/

 

Well that means not compatible with Unity 2021 until the end of the year, but that says nothing about Unity 2020 or 2022.

 

My theory is that when they mentioned "until the end of the year at the earliest", they are referring to when Unity 2022.1 becomes beta and 2021.2 will be out of beta.
When that time comes, possibly by the end of the year/start of next year, THEN they'll release more DOTS packages updates (Entities, Hybrid Renderer, etc.) along with those Unity versions.

 

From the other thread. The next version may be a mode version of 2020.3 aka 2020.3.19f1-dots

https://github.com/Unity-Technologi...mmit/9fd59f0de752a2d80925a1e562dfb7adb697e72c

 

kinda of confirmed though

 

This may be mean that Unity internally work on latest stable version + some tweaks from Unity 2021 like latest compiler with source generators. If it is than we will see it only when 2021 will be released

 

Right now they seem to still be working with 2020.3

 

I like that we are trickling down our DOTS discussion/detective room from the "compatibility with Unity 2021.1" thread to this one, and then when this thread is finally locked maybe we can go to the next changelog thread. At this rate we may arrive at [Inject] era before the next version is released

 

"State of ECS & DOTS" too. I was starting to wonder if we need a dedicated quarantine/complaint box thread that is nuked when Unity has something to say, it's definitely spilling over.

 

After a month of radio silence on their blog, Unity finally gives us some news!

Over the coming months and into next year, the new branding will appear on Unity products, services, collateral, and swag, to name a few of our brand touchpoints.​

We now have a clear vision and roadmap for the swag, maybe they will talk about the engine next?

 

Why is there even a need for a blog post explaining the meaning behind a new logo? Surely the product behind the logo is more important than the logo; actions speak louder than words.

Are the steps to profitability:

1. Make new logo and branding
2. ???
3. profit

?

I have every faith in unity as an engine and a product, but I don't understand who this swag roadmap is for.

 

Investors most likely.

 

To help anyone else out who is using 0.51...

1) open:

C:\Users\Me\AppData\Local\Unity\cache\packages\packages.unity.com\com.unity.entities@0.51.0-preview.32\Unity.Entities.CodeGen\BlobAssetSafety\BlobAssetSafetyVerifier.cs

2) comment out the foreach loop starting at line 160 which looks like this

Spoiler: foreach

foreach (var arg in genericTargetMethod.GenericArguments)
{
var validatedTypes = new HashSet<TypeReference>();
if (arg.IsGenericParameter)
continue;
if (IsOrHasReferenceTypeField(arg, validatedTypes, method, diagnosticMessages, out var fieldDescription, out var errorString))
{
string errorFieldPath = fieldDescription == null ? arg.Name : arg.Name + fieldDescription;
var message = $"You may not build a type {arg.Name} with {nameof(BlobBuilder.Construct)} as {errorFieldPath} {errorString}";
diagnosticMessages.Add(UserError.MakeError("ConstructBlobWithRefTypeViolation", message, method, instruction));
}
}

3) open C:\Code\MY_PROJECT\Library\PackageCache\com.unity.entities@0.51.0-preview.32\Unity.Entities.CodeGen\BlobAssetSafety\BlobAssetSafetyVerifier.cs

4) repeat step 2 with this file

5) switch back to Unity so it can rebuild cache files