-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nvidia 565 - AC Valhalla has vertex explosions #2254
Comments
Got exactly the same problem, was working well (except the freeze when GPU load at 100%) on version 560: GPU: 2080Ti |
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. 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. |
@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. |
Thank you for that answer! Then I'll keep that issue open until the next driver release |
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 f125062...f52e648
(GE-Proton8-3 isn't usable since the game doesn't capture my mouse & i have a multi-monitor setup)
Software information
Assassin's Creed Valhalla
Seems to also affect AC Mirage
System information
Log files
steam-2208920.log
The text was updated successfully, but these errors were encountered: