Screen Melt Way Too Slow

[Graf Zahl]

It's something directly affecting performance settings, so, yes that is possible. Do you use VSync or other frame rate limiting options?

I'll run some tests myself at home.

[Redneckerz]

So I wonder will this bug be fixed in 4.5?

Given you have this issue, but also this hardware, the bug and eventual fix is just a positive byeffect for GZDoom.

For you, however, its still recommended to use LZDoom, because Intel Baytrail graphics is beyond slow.

[sinisterseed]

It's something directly affecting performance settings, so, yes that is possible. Do you use VSync or other frame rate limiting options?

I'll run some tests myself at home.

Framerate set to Unlimited, but the default 200 makes no difference.

Naturally using VSync .

[Graf Zahl]

For me (Geforce 1060) this makes no difference at all. Weird.

[sinisterseed]

And I might now why.

I think none of your are having issues because you're all too fast. This may be similar to the tearing videos in Blood, which only us with slower machines used to experience, apparently.

[drfrag]

The original commit when it was added in may 2018 says:

Code: Select all

- added CVAR to disable WGL_EXT_swap_control_tear.

At least on faster NVidia hardware, setting this to false and gl_finishbeforeswap to true gives a better experience because it reduces screen tearing - but the same setting will reduce frame rate quite dramatically on Intel and can cause bad stalls on some older GPUs when rendering camera textures.

For me it was already false dunno why and makes no difference.

[sinisterseed]

Hm, no idea what's up with finishbeforeswap, haven't checked that one.

[Graf Zahl]

The original commit when it was added in may 2018 says:

Code: Select all

- added CVAR to disable WGL_EXT_swap_control_tear.

At least on faster NVidia hardware, setting this to false and gl_finishbeforeswap to true gives a better experience because it reduces screen tearing - but the same setting will reduce frame rate quite dramatically on Intel and can cause bad stalls on some older GPUs when rendering camera textures.

For me it was already false dunno why and makes no difference.

Yes, I know. Note the word "Camera textures" and "Intel". Definitely not "melting".

Back then I was using a Geforce 550Ti on which it caused major issues with camera textures. But it still gave the best experience because it avoids frame drops and has no tearing.
I find tearing the most distracting render artifact out there.

Hm, no idea what's up with finishbeforeswap, haven't checked that one.

It shuffles around some operations on a screen swap. The results are very hardware dependent.

[sinisterseed]

I'll later if I get on my PC again before I go to sleep if it changes anything, I expect nothing but who knows.

[sinisterseed]

Alright, so gl_finishbeforeswap set to "true" also fixes the melt screen crawl, so it's either that, or setting gl_control_tear to "true" to fix it for some of us, looks like.

[Graf Zahl]

I am actually a bit puzzled. The melt effect is as cheap as they come - after reading the images into two textures all it does is render 320 strips of image each frame.

[sinisterseed]

I can only tell what I see, and this is it, with gl_control_tear set to false, setting gl_finishbeforeswap to true fixes the crawl here .

[Starisma1]

So I wonder will this bug be fixed in 4.5?

Given you have this issue, but also this hardware, the bug and eventual fix is just a positive byeffect for GZDoom.

For you, however, its still recommended to use LZDoom, because Intel Baytrail graphics is beyond slow.

alright i just installed the newest version of LZDoom so ill see if theres a screen melt bug there

[Starisma1]

Update: I tried out gzdoom 4.5 and i no longer have a slow screen melt so i guess 4.4 must of been buggy for my system because 4.5 completely fixed the bug even though my computer has slow hardware

[sinisterseed]

Since this is still open.

As of g51adcd45e I am no longer experiencing the melt crawl either, it's back to normal.