Search Unity

Bug [Solved] Issues with DOTS Editor Package

Discussion in 'Entity Component System' started by unoctium1, May 10, 2020.

  1. unoctium1

    unoctium1

    Joined:
    Sep 27, 2018
    Posts:
    4
    Hi,

    I saw the DOTS Editor package recently got updated to be compatible with Entities 0.10, so I just tried adding it to a small DOTS sample project of mine. However, upon adding the package to my project, I get several errors that all look like this:
    Library\PackageCache\com.unity.dots.editor@0.6.0-preview\Editor\EntityHierachy\DataDiffers\SharedComponentDataDiffer.cs(195,51): error CS0019: Operator '+' cannot be applied to operands of type 'Chunk.<Buffer>e__FixedBuffer' and 'int'


    I'm using Unity 2020.1.0b8, and Entities 0.10.0-preview. I'm not sure if this is happening due to some incompatibility in my setup, or if this is a bug with the Editor package.
     
    Zagule likes this.
  2. Antoine_B

    Antoine_B

    Unity Technologies

    Joined:
    Jun 26, 2018
    Posts:
    10
    Hi,

    Which `API Compatibility Level` are you using ? (Edit > Project Settings > Player > Other Settings)

    If you're using .NET 4.x try to switch to .NET Standard 2.0 and reimport the DOTS Editor package (Project window > Packages > right click on `DOTS Editor` directory > reimport).
    This should fix these compilation errors.
     
    Zagule, DAcKey and laurentlavigne like this.
  3. unoctium1

    unoctium1

    Joined:
    Sep 27, 2018
    Posts:
    4
    I was using .NET 4.x, changing that worked perfectly. Thank you!
     
    Zagule and Antoine_B like this.
  4. CubeGameStudio

    CubeGameStudio

    Joined:
    Dec 1, 2019
    Posts:
    18
    I just had to restart the editor...

    "it is because it uses a new version of Burst, which requires to restart the editor to work (only once after the library is created)"
     
  5. laurentlavigne

    laurentlavigne

    Joined:
    Aug 16, 2012
    Posts:
    6,363
    When will the DOTS editor work in NET 4.6+?
     
  6. attaway

    attaway

    Joined:
    Nov 12, 2014
    Posts:
    45
    restarting worked for me as well, without having to lower .NET to 2.0
     
    laurentlavigne likes this.
  7. The-Oddler

    The-Oddler

    Joined:
    Nov 26, 2010
    Posts:
    133
    I was having this problem too, though restarting didn't work. Removing the library folder didn't work either.

    What worked for me, was updating from Unity 2020.1b14 to 2020.1b15.
     
  8. DAcKey

    DAcKey

    Joined:
    Feb 11, 2019
    Posts:
    9
    Solved, thanks
     
  9. AlecStone-TLN

    AlecStone-TLN

    Joined:
    Oct 5, 2021
    Posts:
    1
    This worked.

    Why though? (thanks ofc)
     
  10. gabrieloc

    gabrieloc

    Joined:
    Apr 6, 2014
    Posts:
    49
    For anyone running into this - make sure the whole DOTS suite is updated since the packages all ship in lockstep. In my case, I had forgotten to upgrade unity.physics to latest.
     
  11. THE2FUN

    THE2FUN

    Joined:
    Aug 25, 2015
    Posts:
    63
    There is no .NET 4.x or .NET Standard 2.0

    Only have .NET Framework and .NET Standard 2.0