Bunch of errors from HDRP on Unity2019.1 update

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.

4555357--422986--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 :smile:

Hope will find out the cause. Thanks!

Show your manifest in Packages folder

oh dang, totally forgot about that

{
  "dependencies": {
    "com.unity.assetbundlebrowser": "1.7.0",
    "com.unity.inputsystem": "0.2.10-preview",
    "com.unity.multiplayer-hlapi": "1.0.2",
    "com.unity.package-manager-ui": "2.1.2",
    "com.unity.postprocessing": "2.2.0",
    "com.unity.probuilder": "4.0.5",
    "com.unity.progrids": "3.0.3-preview.4",
    "com.unity.render-pipelines.high-definition": "5.15.0-preview",
    "com.unity.shadergraph": "5.7.2",
    "com.unity.textmeshpro": "2.0.1",
    "com.unity.timeline": "1.0.0",
    "com.unity.visualeffectgraph": "5.15.0-preview",
    "com.unity.xr.legacyinputhelpers": "2.0.2",
    "com.unity.modules.ai": "1.0.0",
    "com.unity.modules.animation": "1.0.0",
    "com.unity.modules.assetbundle": "1.0.0",
    "com.unity.modules.audio": "1.0.0",
    "com.unity.modules.cloth": "1.0.0",
    "com.unity.modules.director": "1.0.0",
    "com.unity.modules.imageconversion": "1.0.0",
    "com.unity.modules.imgui": "1.0.0",
    "com.unity.modules.jsonserialize": "1.0.0",
    "com.unity.modules.particlesystem": "1.0.0",
    "com.unity.modules.physics": "1.0.0",
    "com.unity.modules.physics2d": "1.0.0",
    "com.unity.modules.screencapture": "1.0.0",
    "com.unity.modules.terrain": "1.0.0",
    "com.unity.modules.terrainphysics": "1.0.0",
    "com.unity.modules.tilemap": "1.0.0",
    "com.unity.modules.ui": "1.0.0",
    "com.unity.modules.uielements": "1.0.0",
    "com.unity.modules.umbra": "1.0.0",
    "com.unity.modules.unityanalytics": "1.0.0",
    "com.unity.modules.unitywebrequest": "1.0.0",
    "com.unity.modules.unitywebrequestassetbundle": "1.0.0",
    "com.unity.modules.unitywebrequestaudio": "1.0.0",
    "com.unity.modules.unitywebrequesttexture": "1.0.0",
    "com.unity.modules.unitywebrequestwww": "1.0.0",
    "com.unity.modules.vehicles": "1.0.0",
    "com.unity.modules.video": "1.0.0",
    "com.unity.modules.vr": "1.0.0",
    "com.unity.modules.wind": "1.0.0",
    "com.unity.modules.xr": "1.0.0"
  },
  "registry": "https://staging-packages.unity.com"
}

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).

[quote=“eizenhorn”, post:4, topic: 743850]
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).
[/quote]

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).

2 Likes

[quote=“elbows”, post:5, topic: 743850]
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).
[/quote]
Yep, mixed up them :slight_smile: anyway SG not needed in manifest, SRP will be manage required version by himself

Thanks guys, it helped

1 Like