UNCHARTED: Legacy of Thieves Collection
Additionally confirming that the game does experiences similar behavior on my machine.
System Information
- CPU: AMD Ryzen 9 5950x
- GPU: Radeon RX 6600XT
- Driver: Mesa 22.2.1-1
- Kernel: 6.0.2-arch1-1
- Proton Version: Proton 7.0-4
Additionally verified no updates were available, and tried experimental branch of proton. Right now, the only common denominator I am seeing is the kernel.
Same symptoms as described above.
- AMD Ryzen 7 3800x
- Radeon RX 6900 XT
- Mesa 22.2.1-1
- Linux 6.0.2-zen1-1-zen
- Proton Experimental - bleeding-edge
Same thing
- GTX 3080
- Intel i7 6600k
- Linux 6.0.2-arch1-1
- Proton experimental bleeding edge
- NVIDIA-DKMS 520.56.06
Replying to https://github.com/ValveSoftware/Proton/issues/6246#issuecomment-1284359369
I might be wrong, but I think the log is saying it cant find your gpu?
Got it to boot! PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% (Only works for NV cards!)
Got it to boot! PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%
No such luck on my AMD system. :crying_cat_face:
I attempted the variables shared by @Bitwolfies but had no luck on my AMD machine.
Try PROTON_HIDE_NVIDIA_GPU=1 %command% The issue (in theory) is that the game cant see our gpus's since I was on NV I could force it to expose my NV GPU. If 1 doesn't work amd might need another workaround.
No luck thus far! I do agree with the conclusion that it can't see the GPU for whatever reason. But I am not sure if a similar workaround to PROTON_HIDE_NVIDIA_GPU immediately exists for AMD.
If the issue is related to the game needing raytracing / dxr and failing without it, then I would expect that you also need to tell mesa/RADV to enable the incomplete driver implementation of that when using an AMD card.
If the issue is related to the game needing raytracing / dxr and failing without it, then I would expect that you also need to tell mesa/RADV to enable the incomplete driver implementation of that when using an AMD card.
Its not, it works fine without the DXR config, I truly think it just cant see the GPU. I can fix it for my NV card by telling it not to hide it, but I think AMD users are out of luck.
No luck launching the game with RADV_PERFTEST=rt %command% standalone or combined with the previous environment variables.
Similarly had no luck with that variable too. I sourced it globally, and directly within the game's launch parameters.
Yeah, i'll go out on a limb and say something is not allowing the game to see the GPU's, that's the one setting only NV users have access to, and the only one so far that's fixed it.
If you report AMD GPUs as Nvidia it complains about out of date drivers. I'm not sure how to work around that
[u4.exe]
dxgi.customVendorId = 10de
From dxvk.conf
The game works for me but mouse input feels terrible.
It feels like there's some kind of variable acceleration/deceleration applied to the camera. No such issue on Windows.
(Gnome Xorg)
EDIT: mouse input seems fine when I lock it to 60 FPS. It's only problematic at higher frame rates (120+).
The game works for me but mouse input feels terrible.
It feels like there's some kind of variable acceleration/deceleration applied to the camera. No such issue on Windows.
Are you on X or Wayland? The mouse has felt kinda bad for me on X but I’ve not had a chance to test it on wayland.
If you report AMD GPUs as Nvidia it complains about out of date drivers. I'm not sure how to work around that
[u4.exe] dxgi.customVendorId = 10deFrom dxvk.conf
maybe use dxgi.customDeviceId steam deck gpu?
I try it with: PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%
The game starts, but once the videos of the studios have passed the game crashes, it does not reach the game menu.
I think there is something else wrong in addition to it not detecting the graphics card.
Same issues:
CPU: AMD Ryzen 9 5900X
GPU: AMD Radeon RX 6800
Kernel: 5.19.16-200.fc36.x86_64
Mesa: 22.1.7-1
Proton Experimental 7.0-20221012
Also worth mentioning that I am running Steam in a flatpak.
If you report AMD GPUs as Nvidia it complains about out of date drivers. I'm not sure how to work around that
[u4.exe] dxgi.customVendorId = 10deFrom dxvk.conf
maybe use dxgi.customDeviceId steam deck gpu?
I tried this with the same result: no launch.
dxgi.customDeviceId = 163f
dxgi.customVendorId = 1002
Setting amd_ags_x64.dll to builtin in the prefix allowed me to launch the game on AMD.
Setting
amd_ags_x64.dllto builtin in the prefix allowed me to launch the game on AMD.
can you explain exactly what you did?
sure add this to your launch options WINEDLLOVERRIDES="amd_ags_x64.dll=b"
I can confirm that @gort818's suggestion works for me on Proton 7.0-4! Thank you so much!
also can confirm this works!
The DLL override makes the game work. From a quick look it seems that enabling FSR 2 in the game shows no effect on the picture nor the performance - can someone confirm this? (Windows Benchmarks show a 20 FPS gain going from Native to FSR Quality)
I am noticing performance gains from the various FSR settings, but at one point when fiddling with the settings I noticed a very sudden and prolonged degradation in performance. It behaved as though it was ignoring my FSR setting and rendering at full scale, so perhaps something similar occurred on your end? If so, a simple restart did bring things back up to a stable 60 for me on FSR quality.
I also didn't see much in terms of performance change but i was also getting like 95-110fps in 4K ultra settings, so hard to say.
The DLL override makes the game work. From a quick look it seems that enabling FSR 2 in the game shows no effect on the picture nor the performance - can someone confirm this? (Windows Benchmarks show a 20 FPS gain going from Native to FSR Quality)
Same sorta experience with DLSS, I don't use it personally, but I did test it for this game. It works for sure, but the gains are maybe 10 fps?
The game doesn't continue after the Iron Galaxy logo.
I am noticing performance gains from the various FSR settings, but at one point when fiddling with the settings I noticed a very sudden and prolonged degradation in performance. It behaved as though it was ignoring my FSR setting and rendering at full scale, so perhaps something similar occurred on your end? If so, a simple restart did bring things back up to a stable 60 for me on FSR quality
@woltersdylan You probably ran out of of VRAM.
From a quick look it seems that enabling FSR 2 in the game shows no effect on the picture nor the performance - can someone confirm this? (Windows Benchmarks show a 20 FPS gain going from Native to FSR Quality)
@Mershi Make sure the game is actually GPU limited. DLSS or FSR don't help if the game is CPU limited.
@gort818 thanks, works for me too, although with Proton 7.0-4, not with Proton Experimental.
I'm getting around 115 FPS all Utlra, no FSR at 1440p on my Ryzen 9 5900X, RX 6800XT, Fedora with kernel 6.0.2
Setting
amd_ags_x64.dllto builtin in the prefix allowed me to launch the game on AMD.
Thanks man, this really helps to launch the game for AMD GPU's ( WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command% )....under Proton 7.0-4, wonder if only RX6000 series GPU's are affected or even older ones.
@mershi Make sure the game is actually GPU limited. DLSS or FSR don't help if the game is CPU limited.
The opening sequence on the market is very CPU intensive (60%+ on an 3700x) which lead to my findings. Later levels did not show the same behaviour so far. Performance is fairly good now.
EDIT: The game seems to show minor issues when played from a hard drive. There have been quite a few texture pop-ins and animations starting late or janking in cinematics (with T poses in between).
I have the issue of i can see the logos, but after that just black screen, left it for atleast 30 minutes, no change, running htop i can see its doing somthing but not drawing it to the screen
Proton Log steam-1659420.log
this is under NVIDIA, latest drivers, 1060GTX 6GB
I have the issue of i can see the logos, but after that just black screen, left it for atleast 30 minutes, no change, running htop i can see its doing somthing but not drawing it to the screen
Proton Log steam-1659420.log
this is under NVIDIA, latest drivers, 1060GTX 6GB
The same thing happens to me, one of the times I tested, I do not know how or why I passed that point and I could see that even having the GTX 1080 the default game tries to activate the FSR, I disabled it, but it did not listen to me. I think the problem of freezing after the logos is because it tries to rescale the images.
It may be meaningless, but there were a number of posts i saw (on Steam Discussions and Reddit) about the game not working for 1000 series Nvidia users, even on Windows. It could be possible that this is an extension of that?
It may be meaningless, but there were a number of posts i saw (on Steam Discussions and Reddit) about the game not working for 1000 series Nvidia users, even on Windows. It could be possible that this is an extension of that?
Well, it may be, since I think all of us who have the problem of freezing are from the 1000 series
Yes, I'm with 1080Ti but the game is working on Mint. The problem with the black screen is on Arch only, very strange.
On Steam Deck I can get the game to launch if I select Proton 7.0-4 (no launch options necessary), but the game immediately crashes on launch if I select Proton Experimental. Unfortunately, setting WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command% doesn't make a difference.
Edit: I'm on the latest version of the Preview branch if that matters!
sure add this to your launch options
WINEDLLOVERRIDES="amd_ags_x64.dll=b"
Worked a charm! Thanks!
Does anyone have a fix to get AMD cards working on windows 10? The game launches but it seems to be using software rendering since it runs at like 2fps and barely uses my gpu if at all. This has been an issue for every game I've tried while trying to do some tests.
EDIT: NVM, fixed it!
Hello @Gambagor, you've come across an issue tracker for a project called Proton. Proton is a compatibility layer for running Windows based games on Linux. Since you're using Windows to start with, Proton is not used and all feedback on this issue tracker is unrelated to your system.
@siramok Thank you for reporting! It looks like this regression has already been fixed in bleeding-edge. Please let me know if it continues to fail after the next experimental release!
Hello
does anyone knows, how it launch on steamdeck?
try different repacks
My game doesn't continue after the he Iron Galaxy logo either.
OS: Manjaro Linux XFCE
Processor: i7-4770K
GPU: Nvidia GTX 1080 Ti
The log file contains just as many 0114:01bc:fixme:mmdevapi:SAO_SetVolume as the log of @mfoxdogg who has the same "game doesn't continue after logo" problem.
Edit: now that I think about it, I think I should also mention that I'm using PipeWire.
I'm also getting 0114:01bc:fixme:mmdevapi:SAO_SetVolume and cant get past logos on Arch. There's no problem on Mint though.
No matter what i did (and i did everything from above), is not launching on Steam Deck. At best is giving a PlayStation error.
I was finally able to get uncharted to run on experimental by limiting the cores to 16 or less:
WINE_CPU_TOPOLOGY="16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15" %command%
may be helpful to others
@GloriousEggroll Do you still need that on bleeding-edge? If so, what hardware is this on?
I'm also not able to get past the logos - I just have a black screen too. Again, my log is full of "fixme:mmdevapi:SAO_SetVolume" errors. I'm using Pipewire on Fedora 36 with a GTX 1070.
@GloriousEggroll Do you still need that on bleeding-edge? If so, what hardware is this on?
yes, experimental bleeding edge, 7950x, 6900 xt, mesa-git
Still not working on steam deck :(
Still not working on steam deck :(
I had no trouble running this on my steam deck!
https://steamcommunity.com/sharedfiles/filedetails/?id=2879559376
https://steamcommunity.com/sharedfiles/filedetails/?id=2879559416
https://steamcommunity.com/sharedfiles/filedetails/?id=2879559435
sway nvidia user here with an i7 6700 and a 1080
amd_ags_x64.dll=b was needed for me to launch the game
Anyone tried this? https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton7-38
I tried running the game with the latest proton-ge build, it starts up perfectly fine with no parameters, but after displaying the logos the game keeps freezing.
Solved 1 of 2 problems.
With the new Proton-GE I get the following error when I try to launch Uncharted:
How do I solve this?
Still not working on steam deck :(
@Lenksi Honestly, I would try either verifying the integrity of files or fully deleting/reinstalling. I know it is a huge game :/ Proton Experimental should work just fine on the deck ...
@GloriousEggroll Do you still need that on bleeding-edge? If so, what hardware is this on?
yes, experimental bleeding edge, 7950x, 6900 xt, mesa-git
Thank you for the details! It sounds like this failure is specific to CPUs with over 8 cores.
@GloriousEggroll Also - could you describe the failure that happened without this launch command?
Two issues I have:
- No rumble/haptic when wired. (adaptive trigger and PS button prompts). On Wireless, rumble (no adaptive and xbox prompts).
- No DLSS menu options on the menu. Can only set with settings file. Using
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%with and withoutVKD3D_CONFIG=dxr11
Tested with Proton-7.04, Proton-Experimental, and GE-Proton7-38
NVIDIA RTX-2070 v510.47.03
With the new Proton-GE I get the following error when I try to launch Uncharted:
How do I solve this?
You could try running the winecfg via protontricks and check if the Windows version is set to Windows 10
@mercifulboss
I'm on ubuntu 20.04 with a nvidia 1070 card. I also got this black-screen-after-logo problem. Tried all launch options mentioned in this thread with Proton7.04 / Proton Experimental / GE-Proton, none of them worked for me :(
I had exactly the same issue than @jianpan described. GTX 1060 Mobile, many Proton variants tested. Black screen after logo/intro, nothing else. Multiple Proton input env var combinations attempted with no success.
Therefore, refunded the game.
I had black screen after logos, but got it fixed by: PROTON_LOG=1 WINE_CPU_TOPOLOGY="16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15" DXVK_ASYNC=1 WINEDLLOVERRIDES="amd_ags_x64.dll=b" VKD3D_CONFIG=dxr11 %command%
with Proton GE 7-37, after first succesfull startup nothing was needed.
I got crash without going to desktop after 5-15 seconds of cutscene/gameplay, on lowest possible details.
Specs:
AMD Ryzen 9 5900x
Nvidia GTX 980
Mesa-22.2.2-1
Linux 6.0.7-zen1-1-zen
Proton GE 7-39
Additionally there is: kernel NVRM: Xid (PCI:0000:2b:00): 69, pid=6023, name=u4.exe, Class Error: ChId 001c, Class 0000b197, Offset 00002388, Data 10621b01, ErrorCode 00000004 in system journal.
I don't know if I'm the right place (old thread), but Uncharted Legacy of Thieves constantly freezes after 10-15 mins of play (memory leak?). The system is still responding and I can exit the game. It tried Proton 9.0-4, Proton Experimental and GE-Proton 10.17, to no avail.
I'm running SteamOS 3.8 on an Ultra Core 7 265F with RX 9060 XT.
Any help would be appreciated,
Thanks!
@Mohandevir the game was fine on my end after over an hour on uncharted 4, can you confirm which game you were playing?
On steam the help menu > system information, will get you information about your system that'd be a good idea to share.
Additionally, add this to the game's launch parameter PROTON_LOG=1 %command% and run the game with proton 10 or experimental until it freezes again and upload steam-1659420.log which you will find in your home folder, note that the log will get overwritten every time you launch the game.
@simifor There you go:
Ordinateur :
Fabriqué par : ASUSTeK COMPUTER INC.
Modèle : ROG STRIX B860-I GAMING WIFI
Type : ordinateur de bureau
Aucun écran tactile détecté
Processeur :
CPU fabriqué par : GenuineIntel
Marque du processeur : Intel(R) Core(TM) Ultra 7 265F
Famille du processeur : 0x6
Modèle du processeur : 0xc6
Révision du processeur : 0x2
Type de processeur : 0x0
Fréquence : 5400 Mhz
20 processeurs logiques
20 processeurs physiques
HyperThreading : non pris en charge
FCMOV : pris en charge
SSE2 : pris en charge
SSE3 : pris en charge
SSSE3 : pris en charge
SSE4a : non pris en charge
SSE41 : pris en charge
SSE42 : pris en charge
AES : pris en charge
AVX : pris en charge
AVX2 : pris en charge
AVX512F : non pris en charge
AVX512PF : non pris en charge
AVX512ER : non pris en charge
AVX512CD : non pris en charge
AVX512VNNI : non pris en charge
SHA : pris en charge
CMPXCHG16B : pris en charge
LAHF/SAHF : pris en charge
PrefetchW : non pris en charge
BMI1 : pris en charge
BMI2 : pris en charge
F16C : pris en charge
FMA : pris en charge
Version du système d'exploitation :
"SteamOS Holo" (64 bits)
Nom du noyau : Linux
Version du noyau : 6.16.7-valve1-1-neptune-616-g27c7a95f5ca5
Serveur X distribué par : The X.Org Foundation
Version du serveur X : 12101018
Gestionnaire de fenêtres X : KWin
Version d'exécution Steam : steam-runtime_1.0.20250723.149234
Informations du client :
Version : 1759461205
Navigateur — accélération matérielle : activé
Navigateur — Canvas : activé
Navigateur — Canvas out-of-process rasterization : activé
Navigateur — Direct Rendering Display Compositor : désactivé
Navigateur — Compositing : activé
Navigateur — Multiple Raster Threads : activé
Navigateur — OpenGL : activé
Navigateur — Rasterization : activé
Navigateur — Raw Draw : désactivé
Navigateur — Skia Graphite : désactivé
Navigateur — Video Decode : activé
Navigateur — Video Encode : désactivé
Navigateur — Vulkan : désactivé
Navigateur — WebGL : activé
Navigateur — WebGL2 : activé
Navigateur — WebGPU : désactivé
Navigateur — WebNN : désactivé
Carte graphique :
Pilote : AMD AMD Radeon Graphics (radeonsi, gfx1200, LLVM 20.1.8, DRM 3.64, 6.16.7-valve1-1-neptune-616-g27c7a95f5ca5)
Version du pilote : 4.6 (Compatibility Profile) Mesa 25.2.0 (git-dce58d5bd5)
Profondeur de couleur du bureau : 24 bits par pixel
Taux de rafraichissement du moniteur : 60 Hz
ID fabricant : 0x1002
ID périphérique : 0x7590
Révision non détectée
Nombre de moniteurs : 1
Nombre de cartes vidéos logiques : 1
Résolution de l'écran principal : 1920 x 1080
Résolution du bureau : 1920 x 1080
Taille de l'écran principal : 31.50" x 17.72" (36.10" diag), 80.0cm x 45.0cm (91.7cm diag)
Mémoire vidéo principale : 8192 Mo
Carte son :
Périphérique audio : ATI R6xx HDMI
Mémoire :
RAM : 63694 Mo
Matériel de VR :
Casque VR : aucun détecté
Aucune configuration VR avec capteur détectée
Nombre maximum de capteurs par session : 0
Divers :
Langue de l'interface : Français
LANGUE : en_US.UTF-8
Espace disque total disponible : 939791 Mo
Plus grand bloc disponible sur le disque dur : 111536 Mo
Espace disque :
Nombre de SSD : 2
Taille du ou des SSD : 2000G,1000G
Nombre de disques durs : 0
Nombre de médias amovibles : 0
I added the PROTON_LOG=1 %command% in the launch options, but nothing to show for in my home folder. I'll try again. Something to do with Gamscope?
I don't know if it's as intended, but I can't add the log file without compressing it first. Here it is:
@Mohandevir github has a file size limit, so if the log size grows too big (and that pretty much depends on the game itself) it's normal to zip it to bring its size down. I couldn't see any smoking gun here so I tried running steam through gamescope and then uncharted 4 within that, but so far no luck getting it to freeze
If you think gamescope might be a factor, then you should run the game in desktop mode and see if it stops freezing, that way things can be narrowed down further. I tried with gamescope 3.16.17 (12494be), if you find gamescope makes a difference on your end that'd mean there was some change between the gamescope version you are on, and mine.
Proton versions
proton experimentalx10 2025-10proton 10.17x1 2025-10proton 9.0-4x1 2025-10proton7.04x1 2022-10ge-proton7-38x3 2022-10proton 7.04x1 2022-10proton 7.0-4x5 2022-10
Launch options
PROTON_LOG=1x3 2025-10WINEDLLOVERRIDES="amd_ags_x64.dll=b"x5 2022-11VKD3D_CONFIG=dxr11x3 2022-11WINE_CPU_TOPOLOGY="16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15"x2 2022-11DXVK_ASYNC=1x1 2022-11PROTON_ENABLE_NVAPI=1x4 2022-10PROTON_HIDE_NVIDIA_GPU=0x4 2022-10VKD3D_CONFIG=dxr11`x1 2022-10RADV_PERFTEST=rtx1 2022-10PROTON_HIDE_NVIDIA_GPUx1 2022-10PROTON_HIDE_NVIDIA_GPU=1x1 2022-10
Launch lines
PROTON_LOG=1 WINE_CPU_TOPOLOGY="16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15" DXVK_ASYNC=1 WINEDLLOVERRIDES="amd_ags_x64.dll=b" VKD3D_CONFIG=dxr11 %command%x1 2022-11PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%x2 2022-10WINE_CPU_TOPOLOGY="16:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15" %command%x1 2022-10WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command%x2 2022-10PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%x2 2022-10RADV_PERFTEST=rt %command%x1 2022-10PROTON_HIDE_NVIDIA_GPU=1 %command%x1 2022-10
DLLs
amd_ags_x64.dllx8 2022-11
Compatibility Report
System Information
I confirm:
Symptoms
I hit the play button on Steam, for a few seconds the button appears as playing and after a few seconds the play button turns green again. And even waiting a while the game does not start.