-
Notifications
You must be signed in to change notification settings - Fork 909
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
Scrap Mechanic: "Unable to find suitable graphics adapter." on AMD/Intel Mesa #1129
Comments
Please also post the DXVK log files and an apitrace. |
Can you please not straight-up ignore the issue template and post the DXVK logs? There's a reason why I'm asking for those in the issue template, it's getting really annoying to have to ask twice for them on every single bug report. That said, this looks suspicious:
But again, can't tell what's wrong without at the very least having a log and ideally an apitrace. |
Sorry for not providing the log files directly. I was able to create a API Trace: ScrapMechanic.trace.tar.gz Here's a dump i did:
It seems like there was no DXVK log generated in the game directory though. |
Proton disables those by default, you need to set the Steam launch options for this game to |
|
Error on your end. Do you have the vulkan drivers for 64 and 32 bit installed? |
That's definitely a setup issue on your end then. Make sure you have a 32-bit Vulkan driver and Vulkan loader installed for your distro. |
That was indeed the problem! After installing the 32-bit Vulkan Drivers (which many people don't have apparently), applying the |
Scrap Mechanic refuses to launch with AMD/Intel Mesa. The game crashes with this error:

This has been confirmed by a few AMD/Intel Mesa users on protondb.
System information
Log files
The game works fine on DXVK using the proprietary NVIDIA driver since this patch was introduced, but this is unrelated to this issue since the game still crashes with same error on DXVK master.
The text was updated successfully, but these errors were encountered: