Search Unity

Does LWRP rendering use glInvalidateFrameBuffer on Quest/Go?

Discussion in 'AR/VR (XR) Discussion' started by Incode, Sep 25, 2019.

  1. Incode

    Incode

    Joined:
    Apr 5, 2015
    Posts:
    78
    I'm currently building for Oculus Quest and Go, and was wondering if the lightweight pipeline calls glInvalidateFrameBuffer on Android devices. Our profiling showed a number of GMEM load calls occurring which, by my understanding, should not occur if the framebuffer is correctly cleared or invalidated before rendering the next frame.
     
    Incode, Sep 25, 2019
    #1

  2. jykholodia

    jykholodia

    Joined:
    Aug 29, 2018
    Posts:
    13
    Yeah we're having the same issue on Unity 2020.1 with URP 8.2.0.
    At least 5 times per frame. Sometimes more. Which kills our performance.
     
    jykholodia, Oct 26, 2020
    #2
    LaireonGames, AlfredoJimenezDev and AlejMC like this.

  3. Shaunyowns

    Shaunyowns

    Joined:
    Nov 4, 2019
    Posts:
    328
    Hello there!

    Please file a bug so the team can investigate. Thanks!
     
    Shaunyowns, Nov 2, 2020
    #3

  4. LaireonGames

    LaireonGames

    Joined:
    Nov 16, 2013
    Posts:
    705
    Same issue here, was a bug report filed by anyone?
     
    LaireonGames, Nov 22, 2022
    #4

  5. Incode

    Incode

    Joined:
    Apr 5, 2015
    Posts:
    78
    We're no longer using LWRP and never filed a bug report, but I haven't profiled this on URP in a long time. If it still exists in LTS versions with URP it would be good to file a report.
     
    Incode, Dec 1, 2022
    #5
    LaireonGames likes this.

  6. LaireonGames

    LaireonGames

    Joined:
    Nov 16, 2013
    Posts:
    705
    As a note in the profiles I was taking in 2020 I was seeing a Huge cost to invalidate buffers and found that disabling depth + stencil saw Massive gains to rendering times
     
    LaireonGames, Dec 1, 2022
    #6