Render bug, large black box occluding screen

[V-Man339]

This seems to happen while leaning forward and frobbing, possibly in noclip?

Will edit if I can replicate/get it to occur.

Solved by restarting the game.

 

Happened on Requiem and Perilous Refuge.

 

Update: I have recorded the bug in action.

 

My settings.

My specs.

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 7 3700X 8-Core Processor             
    CPU Family:  0x17
    CPU Model:  0x71
    CPU Stepping:  0x0
    CPU Type:  0x0
    Speed:  3593 Mhz
    16 logical processors
    8 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Supported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Windows 10 (64 bit)
    NTFS:  Supported
    Crypto Provider Codes:  Supported 311 0x0 0x0 0x0

Video Card:
    Driver:  AMD Radeon RX 5600 XT
    DirectX Driver Name:  aticfx32.dll
    Driver Version:  27.20.14501.18003
    DirectX Driver Version:  27.20.14501.18003
    Driver Date: 11 13 2020
    OpenGL Version: 4.6
    Desktop Color Depth: 32 bits per pixel
    Monitor Refresh Rate: 59 Hz
    DirectX Card: AMD Radeon RX 5600 XT
    VendorID:  0x1002
    DeviceID:  0x731f
    Revision:  0xca
    Number of Monitors:  2
    Number of Logical Video Cards:  2
    No SLI or Crossfire Detected
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 3840 x 1080
    Primary Display Size: 23.54" x 13.23" (26.97" diag)
                                            59.8cm x 33.6cm (68.5cm diag)
    Primary Bus Type Not Detected
    Primary VRAM Not Detected
    Supported MSAA Modes:  2x 4x 8x

Memory:
    RAM:  16292 Mb

Edited February 16, 2021 by V-Man339

[noni]

Strangely, the bug doesn't appear to me. I have a much weaker system than you.

[noni]

I think it's a problem with AMD or Windows drivers. After the last windows update MSI Afterburner has an error message (but it continues to work).

[HMart]

Have you updated the AMD GPU drivers recently? If you didn't and they worked before in TDM than imo it can't be the GPU drivers. Not really connected to TDM but after some recent windows 10 updates, I started having serious problems in visual studio 2015, so is no surprise to me that recent windows updates could be f things up on TDM, because of messing with OpenGL. 

edit: 

Tested Requiem and did everything you said, lean forward, frob and no clip and saw no black box.  TDM 2.09/64 (not final version) my GPU AMD RX 570X, so if it ends being the GPU, perhaps this only happens on modern Vega cards? 

Edited February 17, 2021 by HMart

[stgatilov]

Here is one way to diagnose the problem.

Go to 2.09 beta testing thread, and look at the list of cvars in the first/second post.
Try setting them on/off and see which how they affect your problem.

[V-Man339]

7 hours ago, noni said:

I think it's a problem with AMD or Windows drivers. After the last windows update MSI Afterburner has an error message (but it continues to work).

It would appear my drivers are up to date.

 

2 hours ago, stgatilov said:

Here is one way to diagnose the problem.

Go to 2.09 beta testing thread, and look at the list of cvars in the first/second post.
Try setting them on/off and see which how they affect your problem.

Could I get a link to this thread?

[nbohr1more]

 

There ya go.

 

You can try toggling some or all of these:

 

r_useNewBackend 0

r_fboColorBits 32

r_useBindlessTextures 0

r_postprocess_sharpen 0

r_useMultiDrawIndirect 0

r_usePersistentMapping 0

r_ssao 0

r_tonemap 0

r_softShadowsQuality 0

 

 

[V-Man339]

1 hour ago, nbohr1more said:

 

There ya go.

 

You can try toggling some or all of these:

 

r_useNewBackend 0

r_fboColorBits 32

r_useBindlessTextures 0

r_postprocess_sharpen 0

r_useMultiDrawIndirect 0

r_usePersistentMapping 0

r_ssao 0

r_tonemap 0

r_softShadowsQuality 0

 

 

Attempted the list of commands to fix, no shift. The solution was to restart game, the cause/prevention has still not been found.

[noni]

4 ore în urmă, V-Man339 a spus:

Se pare că șoferii mei sunt la zi.

 

 

Am o altă versiune de driver.

[stgatilov]

Try "r_skipGuiShaders 1" and check if the black quad is gone.
Since it overlaps console, I think it is some GUI element, which is for some reason.
Also, various backend switches don't help.

Also it is worth trying to set "com_smp 0" and "r_useParallelAddModels 0" (this one is "Frontend Acceleration") before the quad appears and see if it will show up again.
I have a feeling that when the quad appears, toggling options is already too late.

[stgatilov]

I assume that if you save the game, then restart TDM and load it, the quad is gone, right?

[HMart]

Unless is me seeing things, for a "quad" it looks very strange it has flat corners?! Isn't the gui quads normal squares? 

[V-Man339]

On 2/17/2021 at 9:50 PM, stgatilov said:

I have a feeling that when the quad appears, toggling options is already too late.

 

Confirmed more or less.

Once the bug is in effect it won't go away based on console command.

[stgatilov]

In fact, r_skipGuiShaders does not help. So this quad is not a GUI element.

[nbohr1more]

I encountered a similar bug in with totallytubular's "Messin with Shaders" glprogs

Setting r_bloom 0 cured it.

[stgatilov]

Hmm... the shape of this black thing might be explained by how bloom blurs light.

Does disabling bloom really help to remove it once it appears?
Does enabling it back restore the artifact?

[nbohr1more]

It does for totallytubular's shaders. I have not encountered this issue with the default shaders.

[stgatilov]

50 minutes ago, nbohr1more said:

It does for totallytubular's shaders. I have not encountered this issue with the default shaders.

I doubt @V-Man339 had these user-made shaders when he discovered the problem.

[nbohr1more]

Another possible clue:

This only happens when both 64-bit and Bloom are active.

I suspect that this is some sort of artifact of exceeding data or instruction limits...

[V-Man339]

On 3/3/2021 at 11:54 AM, stgatilov said:

I doubt @V-Man339 had these user-made shaders when he discovered the problem.

Correct, I have not modified The Dark Mod with anything resembling that which people would not have in base install.

[nbohr1more]

@cabalistic

I fixed a similar bug in my silly fresnel mod.

What are the chances that this line in bloom_blur.glsl can have a negative result?

FragColor += texture(u_source, (fragCoord - u_axis * offset[i]) * invImageSize) * weight[i]

 

[cabalistic]

Since the weights are positive, this can only be negative if the source texture is already negative.

[V-Man339]

Not sure how helpful it is but it is possible to get multiple squares.

It is also possible for a square to pop up much later than another square.

[V-Man339]

UPDATE:

They do not just come in black.

I'm getting semi-transparent red blocks here.

They were gained while staring in this direction, I am unable to replicate this on video.

Edit: Better view here, angle of execution. Lower right.

Edited March 28, 2021 by V-Man339

[nbohr1more]

Try this package. It's not much, I just added a negative number guard to the bloom blur and ambient rim color.

It's a quick repack of my fresnel mod. If it cures the issue then maybe that is all we need.tdm_base01.pk4

 

@V-Man339 ?