Feedback Entities 0.9.0 fails compilation due to warnings

I've updated to Entities 0.9.0-preview.6, and I'm now unable to enter play mode.

There are 15 errors, which are all actually just warnings about obsolete methods, but I can't find a way to disable warnings-as-errors.

I'm at the latest for all other packages.

Library\PackageCache\com.unity.entities@0.9.0-preview.6\Unity.Scenes.Editor\BuildStepCreateResourceCatalog.cs(18,51): error CS0619: 'BuildStep' is obsolete: 'Replace with BuildStepBase. (RemovedAfter 2020-07-01)'

Library\PackageCache\com.unity.entities@0.9.0-preview.6\Unity.Scenes.Editor\LiveLink\BuildStepBuildClassicLiveLink.cs(17,50): error CS0619: 'BuildStep' is obsolete: 'Replace with BuildStepBase. (RemovedAfter 2020-07-01)'

Library\PackageCache\com.unity.entities@0.9.0-preview.6\Unity.Scenes.Editor\Steps\BuildStepSubSceneBundles.cs(19,45): error CS0619: 'BuildStep' is obsolete: 'Replace with BuildStepBase. (RemovedAfter 2020-07-01)'

Anyone else having this problem?

 

Try to downgrade the Platforms package to version preview.7-0.2.2.

 

Had the same issue after updating the platforms package to 0.3. Stick with the recommended dependency version for entities 0.9 to avoid those errors.

 

LMAO NOPE - downgrading Platforms generates even MORE errors.
Now I'll try downgrading EVERYTHING to satisfy Entities 0.9.0 - I have no hope whatsoever.

 

I've removed my manual reference to Platforms, and Entities 0.9.0 is now fine.

However, the DOTS Editor 0.4.0 package is now broken. All of its dependencies are being pulled in automatically.

Here's my manifest.json:

 

Yes dots editor is broken.

 

It was fine before I messed around with my manifest.

 

I would suggest removing ALL Entities dependencies from the manifest file - when loading into the editor, namespaces of the packages you'll have to put back into the manifest cannot be found until you do so(cs0246), for me it was Jobs and Netcode i think.
@Joachim_Ante basically said it all. There's just no mention of what you have to do (or must not do) anywhere, leading to days/weeks/months of frustration. I hope that the huge amount of fantastic work that went into DOTS will be accessible to more people with 2020.1. either because we won't have to download 184516649 dependencies anymore or because we get some kind of update for the package manager, which enables it to show incompatible packages.

 

I think something perhaps @Joachim_Ante missed in my original post was that I only saw warnings, but the warnings were being processed as errors, and there's seemingly no way to disable the package using warning-as-errors. Personally, I 100% don't care about warnings in packages - it's internal code, and shouldn't affect me in any way. If we could have the package as a DLL instead, that would be perfect. And having its dependencies as versioned DLLs too, so that we can have multiple versions coexisting, would be the icing on the cake.

Anyway, between this and the GetSingleton exception spam (https://forum.unity.com/threads/nul...tsingleton-t-in-a-systembase-in-0-9-0.865036/), I have no choice but to remain on 0.8.0 for now.

 

It would be quite useful if we could get an occasional snapshot of which dots packages are known to work without issues. I was looking forward to the DOTS Editor 0.4.0 because I saw it included a SystemDependency viewer , but instead I wasted an hour up and down grading packages semi-randomly