Search Issue Tracker

Fixed in 5.2.3

Votes

0

Found in [Package]

3.3.0

Issue ID

1077472

Regression

Yes

[Android][LWRP] Black Screen if HDR and MSAA are enabled

Package: Scriptable Render Pipeline Lightweight

-

1) Download attached project and open in Unity
2) Make sure that Graphics API is set to Gles3 in the Player Settings
3) Make sure both, Allow HDR and Allow MSAA are enabled on the Main Camera
4) Build and Run Sample Scene on a device
Note: Black Screen

Devices under testing:
Reproduced with:
VLNQA00006 Samsung Galaxy S7, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880
VLNQA00178 Xiaomi Redmi Note 4*, GPU:Mali-T880, OS:6.0

Not reproduced with:
VLNQA00099 Google Pixel XL, GPU: Adreno (TM) 530, OS:9
VLNQA00009 Samsung Galaxy Note8, GPU: Mali-G71, OS:8.0.0
VLNQA00003 Razer Phone, GPU: Adreno (TM) 540, OS: 7.1.1
VLNQA00024 Xiaomi MI 5*, GPU:Adreno (TM) 530, OS:7.0

Reproduced with:
2018.3.0a7, 2018.3.0a11, 2018.3.0b4, 2019.1.0a2

Not reproduced with:
2018.2.9f1

Regression since:
2018.3.0a1 - 2018.3.0a7

Note: Reproduced using Gles2 and Gles3 Graphics APIs

Comments (4)

  1. sonofbryce

    May 16, 2019 04:56

    FYI, I seem to have had a similar issue. In Unity 2019.1.2f1, opening a new LWRP project and switching to Android made the camera in the sample scene render black. Turning Post Processing on the Camera off would render correctly.

    My fix seems to be switching LWRP package to 5.10.0 from the default and/or updating Post Processing stack to 2.1.6. I was getting a weird shader compilation error on project load, so in addition to that I deleted the Library folder. One of those things seems to have fixed the issue on Unity restart.

    Thankfully my first experience with LWRP was so pleasant...

  2. pixelR

    Mar 24, 2019 11:12

    I can confirm: even if this was fixed before in 5.2.3 it came back with 5.6.1 and even 5.10.0 has this problem.

  3. stefan-velnita

    Mar 15, 2019 08:18

    Still reproducible with HDR enabled in 2019.1.0b7 with LWRP 5.6.1.

  4. mfurio

    Jan 30, 2019 05:36

    Hi, Just wondering if this fixed is implemented in 2018.3.3 unity version. Have experience this issue in Unity version 2018.2 and tried to test it in higher version up to latest 2018.3.3.
    And still experiencing it . It says here that the issue is fixed.

    My test device is SAMSUNG Tab S2
    specs :
    SM-T715
    203.1mm (8.0'') QXGA (2048x1536) Super AMOLED Display
    1.9GHz + 1.3GHz octa Core Processor
    3GB LPDDR3 RAM
    UHD Playback & QHD recording
    32GB Memory

    Thanks.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.