Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Issues getting ECS samples to work

Discussion in 'Entity Component System' started by TheBiter, May 13, 2018.

  1. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    Hey guys, I've been really excited to start working with ECS with Unity ever since I've been reading about better practices. However, I am currently having issues getting to ECS samples to work, namely the Two Stick Shooter Pure ECS sample. I've tried all the things I managed to dig up from the forums but without much success.

    I am running Unity 2018.1.0f2 Personal and cloned the ECS samples github via Sourcetree. When I loaded the sample project, I noticed that none of the ECS scripts were properly loaded and I get the following console errors:

    I've double checked the manifest JSON under the /Packages/ folder to be correct to version 2018.1.0f2 and set the Player setting's scripting runtime version to ".NET 4.x equivalent". I also tried to check to see if Entities package was properly loaded via Windows->Package Manager but I could not find such an option. I am using Visual Studio version 15.7.1. I've also deleting the Library folder to rebuild the solution all to no avail. I've run out of ideas.

    I've attached screenshots of my Unity screen for reference. If anyone knows anything I've missed it would be greatly appreciated. Thanks in advance.

    2018-05-12_22-10-00.png Unity_2018-05-12_22-07-28.png
     
  2. avvie

    avvie

    Joined:
    Jan 26, 2014
    Posts:
    74
    Can you tell me the installed packages from the package manager?
     
  3. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    Hey avvie, thanks for responding. Unfortunately I have no idea how to access the package manager, which is likely the issue here. When I click on the "Window" tab I don't see an option for the package manager. You can see it in the attached image of the original post, there is no Package Manager option. If this is located somewhere else then I have no idea where it is.
     
  4. avvie

    avvie

    Joined:
    Jan 26, 2014
    Posts:
    74
    try deleting the library and project setting folder.
    the screenshots you provide show the entity scripts in the inspector in a different way than is supposed and you dont get the package manager window, which should be there.
    How you modified the Package\manifest.json ?
     
  5. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    So I've tried deleting the Library and Project Settings folders and I noticed that it reset the scripting runtime version to ".NET 3.5 equivalent", which allowed me to access the Package Manager. It shows that the Entities is installed with version 0.0.12-preview.1.

    However, being on 3.5 equivalent gives me compile errors for the C# incremental compiler so I switch it back to 4.x equivalent but then I return to my original issues.

    I have attached screenshots of what I'm observing below. A screenshot of the manifest json is also included.

    2018-05-13_12-40-43_red.png 2018-05-13_12-42-13_red.png notepad++_2018-05-13_12-28-34.png
     
  6. avvie

    avvie

    Joined:
    Jan 26, 2014
    Posts:
    74
    the only thing i can think of is that you havent installed the .net 4 framework. if that isnt the case i dont think i can help
     
  7. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    After checking just now, I should have .net 4.7 framework.
     
  8. avvie

    avvie

    Joined:
    Jan 26, 2014
    Posts:
    74
    I dont think i know enough to help you further sorry
     
  9. Kelos

    Kelos

    Joined:
    May 27, 2014
    Posts:
    12
    Have the same issue with 2018.1.0f2 and 2018.2.0b3
     
  10. Kelos

    Kelos

    Joined:
    May 27, 2014
    Posts:
    12
    That was at home.
    Today i tryed this at work with the same Unity versions and it worked. So this is defenately something with the environment.
    I have Window 7 at home and Windows 10 at work. Both have all default windows updates.
     
  11. Kelos

    Kelos

    Joined:
    May 27, 2014
    Posts:
    12
    .Net Framework versions

    Home:
    Client 4.7.02558 461310
    Full 4.7.02558 461310

    Work:
    Client 4.7.02556 461308
    Full 4.7.02556 461308
     
  12. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    I'm running on Windows 10 with the following .Net Framework versions:
    Client 4.7.03056 461808
    Full 4.7.03056 461808

    and get the issues I've listed. I'll try rolling back the .Net Framework the 461308 and see if it resolves my issues. Seem's I'm stuck waiting for .Net Framework 4.7.2 compatibility fixes as it seems I'm not allowed to rollback versions on win10.
     
    Last edited: May 18, 2018
  13. starikcetin

    starikcetin

    Joined:
    Dec 7, 2017
    Posts:
    335
    The Incremental Compiler package is causing these issues when you have spaces in the project path.

    I decided not to use the Incremental Compiler, for now, I suggest you do so as well.

    You might need to do an Import All after removing the Incremental Compiler package otherwise the errors don't go away.
     
  14. Dom_Laflamme

    Dom_Laflamme

    Unity Technologies

    Joined:
    Sep 25, 2013
    Posts:
    27
    what version of the IC are you using?
    A similar bug was fixed in version 0.0.42-preview.2
     
  15. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    For these issues, all I did was install newest Unity version (2018.1.1f1 personal), clone the repository, and then open the Pure version of the ECS sample for the two stick shooter. Basically I get these issues the moment I open the project without doing anything.

    This is my project source path, which doesn't contain any spaces:
    C:\Users\biter\Documents\EntityComponentSystemSamples\TwoStickShooter\Pure
     
    Last edited: May 31, 2018
  16. TheBiter

    TheBiter

    Joined:
    May 29, 2013
    Posts:
    14
    I just tried disabling the Incremental Compiler (version 0.0.42-preview.1) as shown in the Package Manager under scripting runtime 3.5 equivalent (package manager doesn't show up otherwise) and that seems to have fixed the issues I was describing. Now the Package Manager properly shows up under scripting runtime 4.x equivalent also.

    Thank a bunch for helping me resolve this issue.
     
  17. starikcetin

    starikcetin

    Joined:
    Dec 7, 2017
    Posts:
    335
    I basically cannot run any sample projects as-is. They are all broken for me. I go and manually delete the incremental compiler package from manifest to get them working.
     
  18. starikcetin

    starikcetin

    Joined:
    Dec 7, 2017
    Posts:
    335
    You can also edit the manifest file manually to add or delete lines as long as you keep the JSON format intact.