[BUG] Entities error in 2018.2

Unity, this still exists bug! When it will be fixed? It works fine in 2018.2.0b11 but not in any stable versions.

Do you have entities installed correctly?
It works for me, but I have b4 version rather b11

Of course, I’m use ecs from beginning :slight_smile: read my post again - it works in b11, but not works in stable “f” releases, in editor all works fine, only in VS, is known bug from first stable 2018.2.

Oh sorry, my wrong. I must have had something different on my mind, when replaying. :sweat_smile:
Oh well, then I have no idea :eyes:

@MartinGram or any one from Unity can tell, this will be fixed? Because in Rider all works fine, only in VS and only in 2018.2 stable releases.

I’m looking into this but can’t seem to repo it myself on 2018.2.0f2 or 2018.2.2f1.
@eizenhorn what version of the IncrementalCompiler package and Visual Studio 2017 Tools for Unity are you running with?

1 Like

Great thanks for response. Unity 2018.2.1f1, VS 2017 15.5.7 with unity tools 3.5.0.3, Incremental Compiler not installed (because one of latest versions being broken and whole project drops with error on open Unity, but may be it fixed now). On Unity 2018.2.0b11 all works fine.

I had experienced the same issue where I don’t have the proper .Net 4.5 framework installed

I’m working with Unity ECS from beginning and also in enterprise c# development (not related to Unity), of course I have installed .Net 4.5 framework (and all other) :).
3591459--290936--upload_2018-8-9_11-39-46.png
Watch more attentively:

May be problem in VS\UT versions…time to update :slight_smile:

Updating VS\UT not solved problem :frowning:

@eizenhorn you are running the same versions I have now so not sure what makes this not work for you.

Could you try deleting your Library\IncrementalCompiler and Library\ScriptAssemblies folder before starting the editor?

If that doesn’t help could you try to create a new empty project, import the Entities package, set “.NET 4.x Equivalent” scripting runtime version and create a new script to see you get the same problem there?

Yeah cleaning packages, library is firs that i done :slight_smile: scripting runtime version of course .NET 4.x family. But i’m not deleted Library after updating to latest versions (previous post), I’m deleted Library and open project, now is busy (huge amount of assets, and is take time :slight_smile: I’ll tell you results.

Updating to latest VS + UT solved problem (with cleaning Library, Packages and all .csproj), but strange than it works fine in latest beta 2018.2.0b11, that mean backward compatibility is not provided here, anyway not it’s working and we can migrate our production project to 2018.2.2f1 :slight_smile: