On Fri, Aug 14, 2020 at 10:39 AM Bruno Wolff III <bruno@wolff.to> wrote:
I'm not interested in creating a github account and it looks like one
is required to report problems.

Okay, I (might) be able to test that game/report issues to the dxvk tracker sometime next week.
 
I ended up using alternatives to disable dxvk as I was worried about
the packages getting pulled in again later. I'm running rawhide and
I had this get pulled in during a routine update so I wasn't sure if it
would get pulled in another update later. Sins is the heaviest
graphics game that I play, so I don't think I'll need it for performance
reasons for other games at this time. I would have been interested in trying
it out on a couple of more games. If I end up wanting to do that, it looks
like writing a couple of scripts that use alternatvies to turn it on and
off wouldn't be hard. And would be faster than installing and uninstalling
the dxvk packages and simpler than keeping multiple versions of wine around.

I'll be keeping an eye on it though, as Sins does slow down in the end
game. I think this has more to do with tracking objects than rendering them,
but if it does help, I'll want to use it. I expect I'll test 1.7.1 as
soon as it is convenient, as that is supposed to have a lot of fixes.

I pushed the 1.7.1 into F34-F31 just moments ago. You can grab the rpms from koji or wait till tomorrow (or whenever we get another F33/34 compose).

Btw, you can exclude wine-dxvk through dnf config as per Change Proposal Page: https://fedoraproject.org/wiki/Changes/DXVKwined3d#Upgrade.2Fcompatibility_impact :

"Users would be able to opt-out from using DXVK by adding 'exclude=wine-dxvk*' into /etc/dnf/dnf.conf and removing wine-dxvk package."

Thanks for getting dxvk into Fedora. 

You're welcome :)