Search Unity

Black growing dot eats up the entire screen bug

Discussion in 'High Definition Render Pipeline' started by BigRookGames, Mar 13, 2020.

  1. BigRookGames

    BigRookGames

    Joined:
    Nov 24, 2014
    Posts:
    330
    I am experiencing a problem where a tiny part of the screen turns black and then anytime the character moves it gets bigger until it eats the entire screen. What is going on here? It randomly happens and seems to happen about 1 time per minute while playing. If i look the other way and get the black portion out of the field of view then it is no longer there until it shows up again. Any ideas?
     
    BigRookGames, Mar 13, 2020
    #1

  2. ALaramee

    ALaramee

    Joined:
    Jan 8, 2019
    Posts:
    3
    Old post but for those who end up here, this issue (or a very similar issue) has been reported.
    And here is a similar forum post.
     
    ALaramee, Mar 23, 2023
    #2

  3. chemicalcrux

    chemicalcrux

    Joined:
    Mar 16, 2017
    Posts:
    720
    This kind of smells like a NaN artifact. If one pixel gets a screwy value, then it'll propagate to other pixels that sample its value.

    Does checking Stop NaNs on the Camera do anything?

    upload_2023-3-23_15-27-51.png

    (oh, wait, this is a very old post, so the OP might not be quick to answer :p )
     
    chemicalcrux, Mar 23, 2023
    #3
    DevDunk likes this.

  4. KangManJyn

    KangManJyn

    Joined:
    Sep 29, 2022
    Posts:
    7
    I have the same problem in my project.
    Unity 2021.3.19f1, HDRP, DLSS, Direct11, window10 game.
    A black screen appears intermittently on some PCs.
    It could be a shader NaN issue.
    Enable 'Stop NaNs' in camera component options.
    My project is still reporting the same symptoms.
    I am looking for a solution to the problem.
     
    KangManJyn, May 10, 2023
    #4

  5. seoyeon222222

    seoyeon222222

    Joined:
    Nov 18, 2020
    Posts:
    187
    seoyeon222222, May 15, 2023
    #5

  6. Julien_Unity

    Julien_Unity

    Unity Technologies

    Joined:
    Nov 17, 2015
    Posts:
    72
    One thing to note with the "Stop NaNs" option is that it's only fixing the consequence and not the cause.
    This pass has a cost (a small one but that's still a cost) so you may not want to use that in production.
    It's almost always a problem with user content like Shader Graph doing division by zero with values coming from textures for example. So the proper way to fix that is to use a tool like Render Doc, do a capture and try to track the objects that does this (this can be helped with the debug mode that shows NaN in HDRP as well). Once you know which objects output NaNs you need to find in the shader where this could come from.
     
    Julien_Unity, May 15, 2023
    #6
    Remy_Unity likes this.