Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Hmm. My 1st guess is your shaders are bonked, or your shader cache got corrupted.
Go to (wherever Steam dirs are on Decks)/steamapps/shadercache/287700/ and delete it's contents, then just Verify Local Files, and start the game so it can re-create or re-download the pre-generated cache libraries, depending.
PS: just for general suggestions, being that it's an AMD Zen2 integrated meant to run on a teeny amount of wattage in a handheld, I would go with a Glorious Eggroll proton build, mostly because it's packager is a maniac,Tom is obsessed with getting AMD the respect and support under linux to match the level of Nvidias... when a regular proton build is good, a GE proton is (usually) better, especially for AMDs. I can't imagine Decks would be any different.
But also, Deck is Valve, who sponsored proton development so even wine itself is leaps and bounds ahead of where it was, pre-2017... there's no way they'd let a proton hit your Deck downloads that wasn't confirmed working for the hardware it was (essentially) created for!
So NOTE - I don't think this is your issue, I still think it's shader / shader caching... just an FYI while I got your attention. https://github.com/GloriousEggroll/proton-ge-custom/releases
Pray more that it doesn't happen for you
I tried different proton versions , reducing res , reducing tdp, frame rate cap, increasing vram among others