Quoting: Ofca...although after playing a bit, some kind of timings seem to be off. The game plays slow. It's not frame rate, just everything seems slow compared to Windows on Geforce Now; did you notice anything similar?

Not sure. I did have something like this while vkd3d had logging enabled, but not since disabling that. It was not playable on Windows here because for some reason animations were glitching out, getting stuck in T-poses etc.

I did have some debugging enabled, but turning it off didn't improve things. Oh well. I'll wait for few days for things to settle and if it persists, I'll give it a deeper look.

Got it working using lutris

wine-tkg-staging-fsync-git-5.22.r2.g0ae73155-309-x86_64
vkd3d-proton git - build: 22794c67a4442af
NVidia Drivers 455.46.02

set the version of wine in lutris , disabled "dxvk/vkd3d" option in lutris so it will use the native one. and set it to use d3d12.dll native in winecfg

Tried it enough to benchmark high 50fps with my setup on medium/high settings. Will try actually playing it tonight.

Last edited by TuxThePenguin on 25 November 2020 at 4:07 pm UTC

Unfortunately after some testing benchmark works great, but crashes out when starting a game

Interesting. I've read the same report on reddit. Could you try beginning your game on geforce now (it can be done for free), and then attempt loading a save of a game already in progress on your local box?

Tried that , got a little way in , saved it and started locally. Crashed out after the loading bit immediately ( animus as a boy ) Unhandled page fault on read access

Try with https://github.com/GloriousEggroll/proton-ge-custom/releases/download/5.21-GE-1/Proton-5.21-GE-1.tar.gz - I've confirmed that it works with this runner and vkd3d dropped in to AC Valhalla's directory (64 bit version d3d12.dll)

GloriousEggroll's version breaks identically :-)

Then I don't know what's different. I'm using drivers 455.45.01, although I doubt newer drivers would cause the breakage. My Lutris settings are pretty much default: Proton-5.21-GE-1 as runner, Esync on, Fsync off (my stock 5.9.0 kernel doesn't support that)

Quoting: TuxThePenguin455.46.02

Hmm... Turns out my doubts were misplaced. It would seem that problem lays within beta drivers and you may want to try the stable ones. At least according to one of redditors.