search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.16k stars 1.06k forks source link

UNCHARTED: Legacy of Thieves Collection (1659420) #6246

Open EnLaLuna91 opened 1 year ago

EnLaLuna91 commented 1 year ago

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.

woltersdylan commented 1 year ago

Additionally confirming that the game does experiences similar behavior on my machine.

System Information

Additionally verified no updates were available, and tried experimental branch of proton. Right now, the only common denominator I am seeing is the kernel.

Proton Log Gist

dennis1248 commented 1 year ago

Same symptoms as described above.

Proton log Gist

Bitwolfies commented 1 year ago

Same thing

Bitwolfies commented 1 year ago

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?

Bitwolfies commented 1 year ago

Got it to boot! PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% (Only works for NV cards!)

dennis1248 commented 1 year ago

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:

woltersdylan commented 1 year ago

I attempted the variables shared by @Bitwolfies but had no luck on my AMD machine.

Bitwolfies commented 1 year ago

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.

woltersdylan commented 1 year ago

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.

kisak-valve commented 1 year ago

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.

Bitwolfies commented 1 year ago

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.

dennis1248 commented 1 year ago

No luck launching the game with RADV_PERFTEST=rt %command% standalone or combined with the previous environment variables.

woltersdylan commented 1 year ago

Similarly had no luck with that variable too. I sourced it globally, and directly within the game's launch parameters.

Bitwolfies commented 1 year ago

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.

Trevonn commented 1 year ago

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

K0bin commented 1 year ago

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+).

Bitwolfies commented 1 year ago

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.

Deneby67 commented 1 year ago

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

maybe use dxgi.customDeviceId steam deck gpu?

EnLaLuna91 commented 1 year ago

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.

telometto commented 1 year ago

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

Full gist

Also worth mentioning that I am running Steam in a flatpak.

tajeraich commented 1 year ago

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

maybe use dxgi.customDeviceId steam deck gpu?

I tried this with the same result: no launch. dxgi.customDeviceId = 163f dxgi.customVendorId = 1002

gort818 commented 1 year ago

Setting amd_ags_x64.dll to builtin in the prefix allowed me to launch the game on AMD.

nebadon2025 commented 1 year ago

Setting amd_ags_x64.dll to builtin in the prefix allowed me to launch the game on AMD.

can you explain exactly what you did?

gort818 commented 1 year ago

sure add this to your launch options WINEDLLOVERRIDES="amd_ags_x64.dll=b"

woltersdylan commented 1 year ago

I can confirm that @gort818's suggestion works for me on Proton 7.0-4! Thank you so much!

nebadon2025 commented 1 year ago

also can confirm this works!

Mershl commented 1 year ago

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)

woltersdylan commented 1 year ago

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.

nebadon2025 commented 1 year ago

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.

Bitwolfies commented 1 year ago

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?

mozo78 commented 1 year ago

The game doesn't continue after the Iron Galaxy logo.

K0bin commented 1 year ago

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.

agurenko commented 1 year ago

@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

durijuri commented 1 year ago

Setting amd_ags_x64.dll to 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.

Mershl commented 1 year ago

@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).

mfoxdogg commented 1 year ago

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

EnLaLuna91 commented 1 year ago

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.

woltersdylan commented 1 year ago

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?

EnLaLuna91 commented 1 year ago

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

mozo78 commented 1 year ago

Yes, I'm with 1080Ti but the game is working on Mint. The problem with the black screen is on Arch only, very strange.

siramok commented 1 year ago

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!

telometto commented 1 year ago

sure add this to your launch options WINEDLLOVERRIDES="amd_ags_x64.dll=b"

Worked a charm! Thanks!

ghost commented 1 year ago

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!

kisak-valve commented 1 year ago

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.

alasky17 commented 1 year ago

@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!

console-master commented 1 year ago

Hello does anyone knows, how it launch on steamdeck?

try different repacks

E3FxGaming commented 1 year ago

My game doesn't continue after the he Iron Galaxy logo either. OS: Manjaro Linux XFCE Processor: i7-4770K GPU: Nvidia GTX 1080 Ti

steam-1659420.log

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.

mozo78 commented 1 year ago

I'm also getting 0114:01bc:fixme:mmdevapi:SAO_SetVolume and cant get past logos on Arch. There's no problem on Mint though.

Lenksi commented 1 year ago

No matter what i did (and i did everything from above), is not launching on Steam Deck. At best is giving a PlayStation error.

GloriousEggroll commented 1 year ago

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