Closed mjr4077au closed 3 years ago
The operative term being "behind".
Yes.
Mark did mention anisotropic filtering too. I wonder if that plays some role in this.
I think we found the culprit.
I've been testing other things which involved lots of game restarts and switching between games, and I decided to turn Anisotropic Filtering off to see what happens. After considerable amount of time and continuous switching between games, I have to say I have not experienced the corruption again.
I think it happens with the PE as well despite it being physically unable to use the feature because the engine initializes it at startup anyway, then turns off because it says "no". Texture filtering seems to play no role in this whatsoever.
Huh, good job @markanini , you might have actually found it 👍 .
Nah, spoke to soon it seems...
It manifested again eventually...
I just started up BloodGDX to check something out and got similar effects all over in palette emulation mode - all at the borders of individual texels. Changing anisotropic filtering does not change anything there - but the latest Raze works fine. This is actually the same effect I once saw on the weapon which made me disable palette emulation there. This is really weird.
It doesn't have anything to do with Win 10 because it happened to me when I downloaded Raze and tried Blood a couple of days ago. On fully updated Win 8.1. Nvidia driver version ... not sure, probably a few months behind, not at my PC now.
The screen steadily gets cleared up as the viewport changes and the correct colored pixels get drawn over the weirdness, lol :D
Another victim 😩 : https://www.doomworld.com/forum/topic/118220-powerslave-the-fps-now-available-on-gog/?do=findComment&comment=2220982
"Yes, it looked like that. This comment is accurate: 'It's only on the initial viewport of a fresh load.' And yes, Windows 10. I do indeed have an NVIDIA card, a 1650 Super."
Still no idea. I can reproduce the bugged palette emulation in BuildGDX, but never saw this effect in Raze. And not being able to see it in motion means I do not have any idea what might be causing it.
Still no luck with a W10 machine, I take it?
Seems to be most common there.
Make that "W10 machine with NVidia graphics". I have access to two laptops, one has AMD graphics and the other Intel only. And obviously on both the corruption does not happen.
Mighty convenient then, how it's so oddly specific to NVIDIA.
It's a driver bug - but since it only appears to happen with software that's not commercially relevant there's no pressure fixing it.
Are you sure? It may be relevant to file a bug report if that is indeed the case.
If it isn't hardware specific there must be a difference in the driver. Of course, being unable to reproduce it I can only guess.
Puzzling, trying to find where the bug is located will be like roulette then. We'd at least know how to proceed from that point. I could file a bug report but without knowing for certain it won't be of much use. BTW for me GDX never corrupts, it's solid.
But, well, all good roulette fun at least - that is, before it turns Russian 😉 .
I still doubt it's driver related though, mainly because the backend is the same as GZDoom now. Technically this corruption should exist there as well in that case, but it doesn't, it's only Raze. I have never seen it in the other ports either, not just GDX.
And I have not, not once, seen it in the old base. It never happens in 0.6 for me.
Just advising that this still occurs as of Windows 10 20H2 and NVIDIA 460.89 drivers. Still working like a champion under Linux as well.
The beginning or this youtubers playthrough in GDX showed some steps he made to get palette emulation to work: https://www.youtube.com/watch?v=KKluaKMCtq4 Needs the be redone each time a map loads. Hope it can help this project.
Fixed with a12f2778460ccc17a55e3eff1d8f8a2a66e7f140
Lodging here from Discord. Below is what a user gets. He's using a GTX 1060 and I can corroborate this with the latest drivers on my GTX 970.