Philip Rebohle

> For some reason with apitrace on, the shadows don't glitch because with apitrace (at least on Windows) you'll be using the native D3D9 driver for rendering and not DXVK....

> On the commit, I don't get why it uses float instead of an integer value? Because the LOD bias is not an integer property, it's a float property, and...

> And yes. That is exactly what I'm talking about. IMHO a blacklist for games that ban for this would be a better approach (Or at least a way to...

Looks like a d3dcompiler thing, we don't emit messages like that. Need full wine/proton log to tell what's going on, but this almost certainly isn't our bug.

Probably the same issue as https://github.com/doitsujin/dxvk/issues/2540. TL;DR DXVK will no longer work correctly on Windows AMD drivers in situations where anisotropic filtering is used, and we can't really do anything...

Not sure what we're supposed to do here, the game works fine on other drivers. I can't and also just *don't want to* spend my whole life working around AMD...

Vulkan features are not the issue here, Polaris supports everything we need. DXVK would just not work otherwise. Unless your in-game settings are royally messed up somehow, this is just...

Yeah we don't really support Bay Trail, and quite frankly don't really care. Games that are even remotely playable on that kind of hardware should be doing fine even with...

Works fine on my system with Proton 5.0-10 and DXVK's DXGI. The backtrace doesn't really tell us much except that all threads are waiting for something to happen.

Just use wine's DXGI. I can't reproduce the problem so I can't fix it.