Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Bunch of errors from HDRP on Unity2019.1 update

Discussion in 'Graphics Experimental Previews' started by Deadcow_, May 18, 2019.

  1. Deadcow_

    Deadcow_

    Joined:
    Mar 13, 2014
    Posts:
    135
    I found here the same errors I have.
    It's good to knew I'm not the only one with this problem, but... I found no helpful info about it too.

    So, I'm trying to update from 2018.3 to 2019+ Unity version and after while when I updated all packages and referenced Timeline package where needed, after final "Reimport All" I'm still have this errors.

    2019-05-18_15-21-44.png

    It's a pain to see how you guys using all this fancy things shipped in 2019+ while I'm not able to update my project and check them by myself :D

    Hope will find out the cause. Thanks!
     
  2. eizenhorn

    eizenhorn

    Joined:
    Oct 17, 2016
    Posts:
    2,683
    Show your manifest in Packages folder
     
  3. Deadcow_

    Deadcow_

    Joined:
    Mar 13, 2014
    Posts:
    135
    oh dang, totally forgot about that

    Code (CSharp):
    1. {
    2.   "dependencies": {
    3.     "com.unity.assetbundlebrowser": "1.7.0",
    4.     "com.unity.inputsystem": "0.2.10-preview",
    5.     "com.unity.multiplayer-hlapi": "1.0.2",
    6.     "com.unity.package-manager-ui": "2.1.2",
    7.     "com.unity.postprocessing": "2.2.0",
    8.     "com.unity.probuilder": "4.0.5",
    9.     "com.unity.progrids": "3.0.3-preview.4",
    10.     "com.unity.render-pipelines.high-definition": "5.15.0-preview",
    11.     "com.unity.shadergraph": "5.7.2",
    12.     "com.unity.textmeshpro": "2.0.1",
    13.     "com.unity.timeline": "1.0.0",
    14.     "com.unity.visualeffectgraph": "5.15.0-preview",
    15.     "com.unity.xr.legacyinputhelpers": "2.0.2",
    16.     "com.unity.modules.ai": "1.0.0",
    17.     "com.unity.modules.animation": "1.0.0",
    18.     "com.unity.modules.assetbundle": "1.0.0",
    19.     "com.unity.modules.audio": "1.0.0",
    20.     "com.unity.modules.cloth": "1.0.0",
    21.     "com.unity.modules.director": "1.0.0",
    22.     "com.unity.modules.imageconversion": "1.0.0",
    23.     "com.unity.modules.imgui": "1.0.0",
    24.     "com.unity.modules.jsonserialize": "1.0.0",
    25.     "com.unity.modules.particlesystem": "1.0.0",
    26.     "com.unity.modules.physics": "1.0.0",
    27.     "com.unity.modules.physics2d": "1.0.0",
    28.     "com.unity.modules.screencapture": "1.0.0",
    29.     "com.unity.modules.terrain": "1.0.0",
    30.     "com.unity.modules.terrainphysics": "1.0.0",
    31.     "com.unity.modules.tilemap": "1.0.0",
    32.     "com.unity.modules.ui": "1.0.0",
    33.     "com.unity.modules.uielements": "1.0.0",
    34.     "com.unity.modules.umbra": "1.0.0",
    35.     "com.unity.modules.unityanalytics": "1.0.0",
    36.     "com.unity.modules.unitywebrequest": "1.0.0",
    37.     "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    38.     "com.unity.modules.unitywebrequestaudio": "1.0.0",
    39.     "com.unity.modules.unitywebrequesttexture": "1.0.0",
    40.     "com.unity.modules.unitywebrequestwww": "1.0.0",
    41.     "com.unity.modules.vehicles": "1.0.0",
    42.     "com.unity.modules.video": "1.0.0",
    43.     "com.unity.modules.vr": "1.0.0",
    44.     "com.unity.modules.wind": "1.0.0",
    45.     "com.unity.modules.xr": "1.0.0"
    46.   },
    47.   "registry": "https://staging-packages.unity.com"
    48. }
    49.  
     
  4. eizenhorn

    eizenhorn

    Joined:
    Oct 17, 2016
    Posts:
    2,683
    Remove "com.unity.shadergraph": "5.7.2", cos if you use HDRP\LWRP it's already inside, if I remember right (don't remember from which version this behaviour starts).
     
  5. elbows

    elbows

    Joined:
    Nov 28, 2009
    Posts:
    2,502
    Its the postprocessing that is now built into HDRP and so the version that is a separate package needs to be removed from manifest.

    Shadergraph entry is also unnecessary but not because shadergraph itself is included in HDRP code (it isnt), rather because it is listed as a dependency of HDRP so it will be included automatically via that mechanism when HDRP is included. This also ensures that version number will be matching properly, since at the moment the shadergraph entry in that manifest is for an older version (needs to be 5.15 just like HDRP and VFX graph).
     
    Last edited: May 18, 2019
    Peter77 and eizenhorn like this.
  6. eizenhorn

    eizenhorn

    Joined:
    Oct 17, 2016
    Posts:
    2,683
    Yep, mixed up them :) anyway SG not needed in manifest, SRP will be manage required version by himself
     
  7. Deadcow_

    Deadcow_

    Joined:
    Mar 13, 2014
    Posts:
    135
    Thanks guys, it helped
     
    elbows likes this.