protonscr

Nvidia 565 - AC Valhalla has vertex explosions

vkd3dclosed
HansKristian-Work/vkd3d-proton#2254 · opened 2024-12-13 by Lifeismana · updated 2025-01-31 · 6 comments · github
LLifeismana 2024-12-13 github

Vertex explosions on game launch (happens in the main menu & in the loading screen but i couldn't check in game since i get a black screen before it load screen ends (reports from other says it does))

These started happening with nvidia 565 driver (supposedly this issue should have been fixed but it's still hapenning 🤷‍♂️)

Oddly enough GE-Proton8-3 doesn't have that issue (i wasn't able to bisect it on base Proton, uplay blocks the game's launch), it starts happening with GE-Proton8-4 (proton ge diff) which is this diff for vkd3d-proton https://github.com/HansKristian-Work/vkd3d-proton/compare/f125062ee1278ac8508ab5561e289ec4ce0f406e...f52e6482bc63d907054025c5eaf8c0d71a7a9f28
(GE-Proton8-3 isn't usable since the game doesn't capture my mouse & i have a multi-monitor setup)

Screenshot_20241213_134336

Screenshot_20241213_165432

Software information

Assassin's Creed Valhalla
Seems to also affect AC Mirage

System information

Log files

steam-2208920.log

Rromalb47 2024-12-14 github

Got exactly the same problem, was working well (except the freeze when GPU load at 100%) on version 560:

GPU: 2080Ti
Driver nvidia-open 565.77
Linux bazzite 6.11.10-304.bazzite.fc41.x86_64
Proton Experimental

Sshelterx 2024-12-19 github

It's a driver issue, it started in 565 beta but was also present in Vulkan Dev 550.40.75 which was released in september.
I think using a really old vkd3d-proton version gets rid of the Vertex explosions, that's why older proton versions work.
@esullivan-nvidia said he had a fix coming in for this...

Btw, I thought I had it working once with 565.77 but it turns out it's only partly working, lauching the game from Ubisoft Connect launcher a second time makes the menu screens work ..but if you load into a game, the vertex explosions are there again.

Eesullivan-nvidia 2024-12-21 github

@shelterx is correct about this being a driver issue. The change fixing it unfortunately didn't make it into the r565 branch. It will ship in the next major release branch though. Sorry for the confusion.

LLifeismana 2024-12-21 github

Thank you for that answer! Then I'll keep that issue open until the next driver release

Sshelterx 2025-01-24 github

@Lifeismana You can close this, it's fixed in 570.86.10.

Thanks for the fix Eric!

LLifeismana 2025-01-31 github

I'll close this since 570.86.16 officially shipped today with a profile for valhalla

Proton versions