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. Dismiss Notice

URP update from 7.3.1 to 7.6.0 causes black screen rendering on android

Discussion in 'Universal Render Pipeline' started by Buzzrick_Runaway, Apr 27, 2021.

  1. Buzzrick_Runaway

    Buzzrick_Runaway

    Joined:
    Jan 7, 2018
    Posts:
    15
    I'm having major issues trying to update our project from URP version 7.3.1 to version 7.6.0 (or greater)

    With v7.3.1 everything works fine on device, but a simple URP package update to v7.6.0 causes the device to render a completely black screen. I can see that the game is running (via logcat) and the music is running, plus I can tap on the position on screen where I expect a button to be render, and the button triggers, so this is a purely rendering problem.

    I have a "Pipeline Asset (Forward Renderer)" pipeline created via the Create->Rendering->URP menu, with a "2D Renderer (experimental)" renderer assigned. Updating URP is the only thing that changed.

    I have tried with a "Forward Renderer", and that causes the screen to render, but it has transparent sprite artefacts, and none of the 2D lights work.

    I've tried tweaking a million different other settings based on vaguely similar forum posts, and I can't figure out what I need to do to get it working so that we can continue updating our version of Unity. Does anyone have any suggestions
     
  2. Buzzrick_Runaway

    Buzzrick_Runaway

    Joined:
    Jan 7, 2018
    Posts:
    15
    This has just become an urgent issue.

    Whenever I launch our project it insists on upgrading to URP v7.6.0, even though I haven't upgraded our Unity version. We've been running Unity v2019.4.25f1 for months now, and we haven't changed that. I can downgrade URP to v7.3.1 manually, but this is a very slow process and I don't want to have to do that every time that anyone on the team opens the project.

    After doing some more testing, the problem appears to be with rendering using the OpenGLES3 API with URP greater than v7.3.1.
    We're are using OpenGLES3 (Requiring ES3.2) in our project. This was chosen because it was the expected standard when we started this project, and selecting a newer graphics API (i.e.: Vulcan) would reduce the number of older devices we can support.

    We still want to support OpenGLES3. Is there anything that we can do to get it going on the newer version of URP?
     
    Last edited: Jul 12, 2021
  3. Buzzrick_Runaway

    Buzzrick_Runaway

    Joined:
    Jan 7, 2018
    Posts:
    15
    So I have found out what is forcing the update of the URP package every time I launch the application. I was using the 3.0.x beta version of Unity Hub. I've rolled back to using Unity Hub v2.4.4, and it no longer forces the update every launch.

    I am still unable to get rendering working on any version of URP higher than v7.3.1.
     
  4. adamgolden

    adamgolden

    Joined:
    Jun 17, 2019
    Posts:
    1,497
    Have you tried setting Blit Type to Always in Build Settings? Generally it should be set to Auto for a balance of compatibility with higher performance (where supported), but Always is the most compatible.
     
    Buzzrick_Runaway likes this.
  5. Buzzrick_Runaway

    Buzzrick_Runaway

    Joined:
    Jan 7, 2018
    Posts:
    15
    I need to do some more testing to confirm, but it looks like you've solved it!
    This has been a thorn in my side for almost a year now, making it so that I couldn't upgrade. I can't believe it was a simple switch to fix it.
    Thank you @polemical, You're a genius!
     
    adamgolden likes this.
  6. Buzzrick_Runaway

    Buzzrick_Runaway

    Joined:
    Jan 7, 2018
    Posts:
    15
    Tested on more devices, and confirmed that this does indeed fix our issue. Thanks
     
    adamgolden likes this.
  7. DEEnvironment

    DEEnvironment

    Joined:
    Dec 30, 2018
    Posts:
    436

    great you found a solution

    just a heads up
    in 7x some other changes you may find between api versions is related to Xbox X tags

    cheers