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 does not support FP16 HDR Mode?

Discussion in 'Universal Render Pipeline' started by terryYang, May 26, 2020.

  1. terryYang

    terryYang

    Joined:
    Apr 9, 2014
    Posts:
    30
    Is it true? I can not find any document about this. From Tier Settings, I selected FP16 HDR Mode, but Frame Debug told me the _CameraColorTexture format was still B10G11R11_UFloatPack32. I tried to build windows and Android player, the FP16 mode will changed to R11G11B10 automatically, it's a limiation of URP?


    1.jpg

    2.jpg
     
  2. BattleAngelAlita

    BattleAngelAlita

    Joined:
    Nov 20, 2016
    Posts:
    400
    Explicitly - nope.
    There is some logic in URP that might give you fp16 framebuffer, but I couldn't get it to work.
     
  3. Alejandro-Martinez-Chacin

    Alejandro-Martinez-Chacin

    Joined:
    Oct 15, 2013
    Posts:
    144
    I actually don't have those options anymore. Did they actually go away?
    The only HDR related checkbox that I can find on URP is the asset itself (the one that has a list of renderers and lights and shadows settings) with an HDR checkbox on it.
    Is this only 'back buffer' HDR setting? Render targets I can create them on my own (via Default or Default HDR enums).
     
  4. Liderangel

    Liderangel

    Joined:
    Jul 8, 2018
    Posts:
    99
    Since this is the only post related to the issue when you search on Google I'm going to leave this here: https://github.com/Unity-Technologies/Graphics/pull/6728

    It shows that they are adding the feature "soon" (they committed it to master 2 months ago but we are still waiting for... something? from master to a Unity build there is an invisible time-gap of stuff)
     
  5. aganm

    aganm

    Joined:
    Sep 25, 2019
    Posts:
    114
    I was trying to figure out why I have this visual artifact. This seems to be it. I guess I just have to wait that it gets released now.

    The pull request says that it fixes the artifact at the cost of performance. I know it will be easy to test when it's out, but in the meanwhile, any idea what kind of performance this fix may cost?