Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

What should our expectations be wrt patch releases? (ie, pink stuff)

Discussion in 'Universal Render Pipeline' started by hertz-rat, Apr 7, 2020.

  1. hertz-rat

    hertz-rat

    Joined:
    Nov 3, 2019
    Posts:
    71
    I am slightly new to Unity release cycles. At my last job, we used a versioning scheme X.Y.Z, where X was a major breaking change, Y was a new feature with a small risk of breakages, and Z was strictly for non-breaking patch changes.

    For 2019.2.X and 2019.3.X in Unity, it seems like every patch change has a risk of breaking all your shaders in the URP/HDRP workflows.

    Is this something I should be expecting? What should my expectations be wrt patch releases? I'm just a little unfamiliar with this scheme

    I ask because I was experimenting with URP this week and upgraded to 2019.3.8 because .7 was crashing constantly. All my stuff is pink, like in the 2019.2.X days between updates. It is just an exploratory project, but I wasn't able to revert back to the working versions of the assets, which could be a bit of a pain for my main project if it came up (yeah, I have backups).
     
    Last edited: Apr 7, 2020
    hertz-rat, Apr 7, 2020
    #1

  2. erikabar

    erikabar

    Unity Technologies

    Joined:
    Jan 26, 2017
    Posts:
    36
    hi @hertz-rat, for packages we have a separate release cycle and upgrading Unity version should not break your shaders if the package is compatible with that version. The latest 2019.3 stream URP(and HDRP) package right now is 7.3.1 which is compatible with Unity 2019.3.2f1 and up (which means it has to work on both 2019.3.7 and 2019.3.8) and it is also the only one available in 2019.3.8 - please check if you have a correct version in the Package Manager.
    If the version is correct and the problem still persists, would you mind reporting a bug so we could investigate?
     
    erikabar, Apr 9, 2020
    #2