The trace is working fine and it seems like DF24 is not being used, so i guess this was created with wined3d, can you record one with dxvk?
The order/swizzle on my FETCH4 might be incorrect -- but thats an easy fix if I can get a trace to figure that out.
Here it is!
https://mega.nz/file/z2AR1Q4K#q59hYHn710svdelHsXvnqs2kbTBF95LfY7F0K1gRkxk
(sorry, I'm late)
Should be fixed now :)
It's way better!
But when I look closer, the issue is still here:
dxvk:

wined3d:

Tested with dxvk v1305
Can you try reverting 2fc00a331b952b1ecba9813d892f1edf80688c68? Otherwise at this point I do not know :<
also if you can can you provide a trace close up with DXVK so I can check it against AMD native? It could just be like that...
Nope, it's the same thing as the first screenshot:

I think you have to reopen the issue 🤷
edit: ok, I will make a new trace
can you provide a trace close up with DXVK so I can check it against AMD native? It could just be like that...
if it is, then i can fudge it to use the path it does in wined3d
Should be fixed for good now :)
Again, it's better!
BUT (I know..) there is still a difference with wined3d:
With wined3d, you have a lot of "noise":

Which is not here with dxvk:

Plus, you can notice there are black lines we shouldn't see.
iirc the game uses a different method to sample shadows on dxvk compared to wined3d, so differences are expected.
If you can get a dxvk trace super up close I can validate that on native and see if anything is amiss. Sorry to be a pain
https://mega.nz/file/rn4jwbTB#K7c9HP8ndCIgsp3qjhRMr7Jv7SyBFgf5tkAcJAfsD-w
(sorry, it's very long to upload at home)
Can this issue be reopened?
This should be fixed now 👍
The black bars are gone!
But he "noise" is still not here:
WINED3D:

DXVK:

Which one is supposed to be the right one?
Its a different shadow path.
What's does it mean? Is the "noise" not being here normal?
For the shadow path on AMD, yes.
But I have a Nvidia GPU.
It's using D3D9 driver hacks that Nvidia usually doesn't have.
Buy I have this "noise" with my Nvidia GPU with WINED3D. Why not with DXVK? I don't understand :/
Because we expose DF24 which uses a different shadow path.
I guess everything's normal then.
Let's say Duke Nukem Forever is... done™
Duke Nukem Forever has two different ways to filter shadows:
With DXVK the game uses the one primarily built for AMD GPUs. That is because DXVK supports D3D9 driver hacks that typically Nvidia's Windows D3D9 driver doesn't support. DXVK also supports those on Nvidia GPUs.
When those hacks (DF24 in particular here) aren't present (as would be the case on Nvidia Windows D3D9 drivers), the game does something else to filter shadows.
With DXVK:

With WineD3D:

It's not the same bug as https://github.com/doitsujin/dxvk/issues/1639, it would be like this instead:

System information
Apitrace file(s)
https://mega.nz/file/yzYXDQha#tSJKWoMY2xDloDO-6RkSKUanxKk_CA8yz7yIx-Vrjb4
Log files
steam-57900-wined3d.log
steam-57900-dxvk.log