Search Unity

  1. We are migrating the Unity Forums to Unity Discussions. On July 12, the Unity Forums will become read-only. On July 15, Unity Discussions will become read-only until July 18, when the new design and the migrated forum contents will go live. Read our full announcement for more information and let us know if you have any questions.

Postprocessing and render pipeline package error after upgrading

Discussion in '2018.3 Beta' started by 5argon, Sep 25, 2018.

  1. 5argon

    5argon

    Joined:
    Jun 10, 2013
    Posts:
    1,556
    Screenshot 2018-09-25 11.48.10.png

    Screenshot 2018-09-25 11.48.27.png

    The solution which does not work
    • Reimport All : same result
    • Reimport only some script folders : same result
    • Upgrade the package : the Package Manager UI is not available because it hasn't compile yet.
    • Edit the manifest manually to upgrade the package : how can I know the latest version number of a specific package?
     
  2. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    Where did you upgrade it from? You sure you don't have local SRP packages left in your directories in Assets or Packages? If you upgraded from 2018.1, you probably had something in local folders..

    As for knowing the latest packages and their versions, your safest bet is to just search here: https://bintray.com/unity/unity

    Atm latest releases are 3.3.0-preview for SRPs and 2.0.13-preview for PP
     
    LeonhardP and 5argon like this.
  3. 5argon

    5argon

    Joined:
    Jun 10, 2013
    Posts:
    1,556
    Ok... after a series of random Reimport All, the error remains, but after some more Reimport (not all) on certain folders it seems to trigger a sequence of "correct" dll rebuilt. Each time the error change places but eventually I got it all compiled without changes in manifest.

    Really hope there is a "Reimport All Scripts" (without reimporting textures) that works, that is clean all the .dll residues that might cause this kind of problem. (Including packages dll, problem with incremental compiler, etc.)

    Prefab overrides was not correctly migrated though (some previously not overridden field was overrided as null), but I can fix that manually anyways as I refactor things for nested prefabs.
     
  4. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,143
    Thanks for bringing this to our attention!
    Could you please submit a bug report for this issue? A reproduction project would be great, too. It's not possible to tell what's going on from the info you've provided alone.