Search Unity

Package Manager/Compile Errs after ECS install attempt

Discussion in 'Package Manager' started by Xblade-Imperium42, Jun 30, 2019.

  1. Xblade-Imperium42

    Xblade-Imperium42

    Joined:
    Jan 12, 2016
    Posts:
    605
    In Unity 2019, I tried following this recent vid:



    All packages seemed fine until I installed Hybrid Renderer - after that, I got a spam of errors not finding dependencies ... but I thought the entire point of packages is that dependencies are already gathered? I'm confused --

    I closed Unity >> Opened >> Now I see this:



    How to fix this?

    I don't even see com.unity.test-framework.performance or com.unity.collections o_O

    BUT... I did find it in /Library/PackageCache/ :



    Code (CSharp):
    1. {
    2.   "dependencies": {
    3.     "com.unity.analytics": "3.3.2",
    4.     "com.unity.burst": "1.0.4",
    5.     "com.unity.collab-proxy": "1.2.16",
    6.     "com.unity.entities": "0.0.12-preview.24-timestampfix",
    7.     "com.unity.jobs": "0.0.7-preview.13",
    8.     "com.unity.mathematics": "1.0.1",
    9.     "com.unity.multiplayer-hlapi": "1.0.2",
    10.     "com.unity.package-manager-ui": "2.1.2",
    11.     "com.unity.rendering.hybrid": "0.0.1-preview.13",
    12.     "com.unity.textmeshpro": "2.0.1",
    13.     "com.unity.timeline": "1.0.0",
    14.     "com.unity.xr.legacyinputhelpers": "2.0.2",
    15.     "com.unity.modules.ai": "1.0.0",
    16.     "com.unity.modules.animation": "1.0.0",
    17.     "com.unity.modules.assetbundle": "1.0.0",
    18.     "com.unity.modules.audio": "1.0.0",
    19.     "com.unity.modules.cloth": "1.0.0",
    20.     "com.unity.modules.director": "1.0.0",
    21.     "com.unity.modules.imageconversion": "1.0.0",
    22.     "com.unity.modules.imgui": "1.0.0",
    23.     "com.unity.modules.jsonserialize": "1.0.0",
    24.     "com.unity.modules.particlesystem": "1.0.0",
    25.     "com.unity.modules.physics": "1.0.0",
    26.     "com.unity.modules.physics2d": "1.0.0",
    27.     "com.unity.modules.screencapture": "1.0.0",
    28.     "com.unity.modules.terrain": "1.0.0",
    29.     "com.unity.modules.terrainphysics": "1.0.0",
    30.     "com.unity.modules.tilemap": "1.0.0",
    31.     "com.unity.modules.ui": "1.0.0",
    32.     "com.unity.modules.uielements": "1.0.0",
    33.     "com.unity.modules.umbra": "1.0.0",
    34.     "com.unity.modules.unityanalytics": "1.0.0",
    35.     "com.unity.modules.unitywebrequest": "1.0.0",
    36.     "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    37.     "com.unity.modules.unitywebrequestaudio": "1.0.0",
    38.     "com.unity.modules.unitywebrequesttexture": "1.0.0",
    39.     "com.unity.modules.unitywebrequestwww": "1.0.0",
    40.     "com.unity.modules.vehicles": "1.0.0",
    41.     "com.unity.modules.video": "1.0.0",
    42.     "com.unity.modules.vr": "1.0.0",
    43.     "com.unity.modules.wind": "1.0.0",
    44.     "com.unity.modules.xr": "1.0.0"
    45.   },
    46.   "registry": "https://staging-packages.unity.com"
    47. }
    ______________________________

    # Updates

    EDIT 1: Tried deleting everything in PackageCache. No dice.
    EDIT 2: Tried deleting manifest.json -- Unity opened! ...but not sure if I broke anything.
    EDIT 3: Removed all the ECS stuff, but also removed and added some more -- not sure if this is a good or bad thing?
     
    Last edited: Jun 30, 2019
  2. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    527
    Hi @Xblade-Imperium42 ,

    What is happening here is that you have two packages at the same depth in the dependency graph asking for the same dependency but at different major version. The Package Manager is stopping the resolution to let you know it cannot chose one. But, the package manager is doing a really poor job to give you proper context so you can better decide on the action to take. Here, we don't know where is the
    com.unity.collection
    is coming from and also which other packages that requested
    com.unity.test-framework.performance
    at version
    0.0.15
    . :(

    One way to solve this issue is to explicitly add the package
    com.unity.test-framework.performance
    at the highest version listed in the conflict in your project. Though, you may end up with compilation errors.

    This is a great reminder that we need to improve the package conflicts error messaging.

    Regards,

    Pascal