lsfg-vk: An error occurred while initializing the Vulkan device layer:
- Failed to create Vulkan device
- Unknown error (error -3)
I blame that lossless-scaling layer. Try uninstalling that.
lsfg-vk: An error occurred while initializing the Vulkan device layer:
- Failed to create Vulkan device
- Unknown error (error -3)
I blame that lossless-scaling layer. Try uninstalling that.
Before I switched to the open Nvidia driver, it worked, even with the lossless layer
It's very possible the layer is broken and only happens to break on the open driver. If it works without that particular layer, it is overwhelmingly likely a bug in that layer. I don't see how vkd3d-proton would be at fault in that situation.
It's very possible the layer is broken and only happens to break on the open driver. If it works without that particular layer, it is overwhelmingly likely a bug in that layer. I don't see how vkd3d-proton would be at fault in that situation.
https://github.com/ValveSoftware/Proton/issues/9329#issuecomment-3695149137
The issue I'm facing prob has to do with this
It's very possible the layer is broken and only happens to break on the open driver. If it works without that particular layer, it is overwhelmingly likely a bug in that layer. I don't see how vkd3d-proton would be at fault in that situation.
ValveSoftware/Proton#9329 (comment)
The issue I'm facing prob has to do with this
Facing the exact same issue. Native vulkan apps work, wine/proton fail to select the correct GPU. Broke almost my entire game library.
On my System76 Adder WS, I'm running Arch Linux and they no longer support the proprietary drivers. I switched to linux-cachyos-nvidia-open and now any game using vkd3d-proton does not work anymore. For example, in Spider-Man Remastered, I get an error saying my system doesn't support d3d12. I attached the log down there as well.
I suspect it's a System76 firmware issue as they had an unrelated Nvidia GPU issue that was fixed recently, albeit with a band aid solution. But I have the log down there to see if it could be of any use in debugging this.
steam-1817070.log