Assassin’s Creed Mirage is impossible to be played with 565 and the latest dev 550.40.79. There are heavy artefacts. The game is a total mess and looks like this:
The same problem on 565 with AC Mirage (vertex explosion). Arch (CachyOS) + Gnome.
It’s most likely broken in 565 but It “should (?)” be fixed in 550.40.79, at least for Assassins Creed Valhalla, however even with 550.50.79 I got vertex explosions after I changed graphics settings, then I restarted the game again and it was fine. I’m back to 560 now because of these issues.
I’m on CachyOS with 565.57.01 open drivers. After hours of tinkering I got this game working on Heroic Games Launcher using Proton - GE-Proton8-3. With an RTX 3090
Does anyone know if this issue has been fixed or if there is a work around. I am running linux and have the 565.77 driver installed, AC Mirage is completely unplayable, i can’t even load into the settings menu and navigae aroun
No known workaround that I know of other than using the 550 Vulkan dev driver, which should work. But then you lose explicit sync and have to run Xorg for good performance.
Proton - GE-Proton8-1, 8-2 or 8-3 Eliminates the texture problems with the latest drivers 565.77.
Ok, weird tho, I suspect that the shipped vkd3d-proton in GE 8 does something different than the newer versions.
Indeed weird. Another Proton I just found that works: Sarek9-20.1
GE-Proton8-4 is indeed the one that starts showing that glitch (with 565)
it can probably be bisected further than that (easy target being obviously dxvk & dxvk-nvapi (edit: forgot that dx-vk isn’t for dx12 so issue is in there Comparing f125062ee1278ac8508ab5561e289ec4ce0f406e...f52e6482bc63d907054025c5eaf8c0d71a7a9f28 · HansKristian-Work/vkd3d-proton · GitHub )
Some nice Nvidia Art there :D I was in and tested as well. Vertex explotion left and right.
Its not that long ago, that I was playing the game, and it was fantastic
