Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
almost everytime you crash out at starting a new game before you see the cart, it's prerequisites, but the install script should have taken care of that...
try going into properties and specifically picking which proton to use under compatibility, which doesn't really matter, but for the hell of it pick proton-7 or 8, OK that, and try again. It's probably not it, I mean the defaults are probably set for Decks now, which are linux AMDs, but it's worth a shot.
LOTS of people have issues with an AMD update that came out back in Jan I think, be it microcode or something specific to CPU or GPU, I don't know, but I know lots of discussions of older games with AMD users in them, have a lot of unhappy players. I assume this will affect linux gamers as well.
On linux, you have something called libraries, and certain system libraries can affect playing games on steam. It usually only affect native games but considering the bug reports I have seen on proton's github, older libraries do affect proton 9 and probably 8 as well. So old libraries or simply mismatched libs can lead to a game crashing. Deabian 11 is 5 years old now, and the kernel it uses is 7 years old now. So something that old is bound to cause issues with modern proton versions, since some of the optimizations implement since then weren't a thing at the time. And to give you a perspective, debian 11 is EOL this year.
So I honestly recommend updating it to debian 12 and use the mesa drivers if possible, because in terms of gaming they are better than AMD's and even AMD's devs acknowledge that. So as I said before, unless you have a professional reason, you should just use mesa instead.
I would start by looking at what vulkaninfo says. It should report a Vulkan version of 1.3.x. If it is not even installed chances are that Vulkan has not been installed yet. Once it has a usable Vulkan version installed would I test with vkcube if it can actually render a simple Vulkan test demo. Then at least OP would know whether his system supports Vulkan rendering or not.
I highly doubt it's got anything to do with your vulkan implementation, but that's easy enough to test, just pass "PROTON_USE_WINED3D=1 %command%" as your runtime parameters to fall back to OpenGL rendering and see if that gets rid of your black screen, or set a proton lower than 5.0 where it wasn't the default yet.
It could be anything graphically related, for all we know you're on an AMD iGPU since you didn't give us one technical specification...
I was using the default Proton version (Experimntal) and this is why it didn't work. I updated to Proton 7 and the game worked! Thank you so much for your help.
Death Approaches is however not wrong and you could go without it if you forced Steam's Proton to fallback to the old OpenGL code. But you do not want to do this, because it is a lot slower. Make sure to use the latest graphics driver and to support the latest Vulkan version. This will keep DXVK happy and get you the best performance.