ValveSoftware
The Last of Us Part 1 (1888930)
Compatibility Report
- Name of the game with compatibility issues: The Last of Us Part 1
- Steam AppID of the game: 1888930
System Information
- GPU: Nvidia 3090
- Driver/LLVM version: Nvidia 530.41.03
- Kernel version: 6.2.8.arch1-1
- Link to full system information report as Gist: https://gist.github.com/urbenlegend/3f09d7a80a7c5ea2ac31053f9e120c12
- Proton version: Hotfix (also tested on Experimental)
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
Game crashes on start if PROTON_ENABLE_NVAPI=1 %command% is specified in the launch options. Game successfully starts when it is omitted, but this means that DLSS can not be enabled.
Reproduction
- Add
PROTON_ENABLE_NVAPI=1 %command%to launch options. - Start game
- Game window briefly flashes before crash reporter pops up
Can confirm, 3080, either on hotfix or bleeding edge. Other typical things like PROTON_HIDE_NVIDIA_GPU=0 or VKD3D_CONFIG=dxr11 are fine.
Dunno if this is a proton bug or a game bug, but it only sees my card as having 6gb of vram, my card has 10gb.
There's something quite funny going from them boasting about day 1 deck compatibility to the unofficial label. Speaking of which I noticed the page doesn't actually make any mention of verification, what happened there?
Hello @urbenlegend, warn:debugstr:OutputDebugStringA "\n******************************************************************************\n*** ASSERTION: NVAPI_OK == status\n***\n*** Function: ndgi::Adapter::InitPerfInfo\n*** File: ndlib/render/ndgi/win/ndgi-adapter-table-win.cpp\n*** Line: 922\n*** Built: \n***********************"... looks like a possible line of interest in your log.
(Non-authoritative) It looks like this game uses DLSS 3.0? DLSS 3.0 is known to not work with Proton at this time.
@kisak-valve Is there no DLSS 2.0 fallback? AFAICT, other games (Spider-Man Miles Morales) have offered DLSS 3 (frame generation and all that) but they always had a mode that could still work on Nvidia 3xxx cards and below.
@Bitwolfies I am seeing something similar on my end except it's reporting 12GB of RAM when I have 24GB of RAM on my 3090.
Regarding NVAPI crash, I filed https://github.com/jp7677/dxvk-nvapi/issues/115 to track this on our side. Right now it expects NvAPI_GPU_GetGpuCoreCount to succeed which is implemented using NVML so it fails if wine-nvml is not installed in the prefix. And if it is installed, it then calls NvAPI_GPU_GetPstates20 which is not implemented at all.
(Non-authoritative) It looks like this game uses DLSS 3.0? DLSS 3.0 is known to not work with Proton at this time.
@kisak-valve I think we should be able to get DLSS 3.0 Super Resolution to work, it's only DLSS 3.0 Frame Generation that's currently not available on Linux.
The game opened with Proton Experimental, Proton 7.0-6 and HotFix, but not at the first try, but I think that I closed it on the "spinning coin" screen because it was taking too long. Seeing friend with similiar GPU running on Windows the performance was also awful already on the configuration menus and on the title screen. The integrade shaders builder is really taking its time to finish, I'll wait and see if it improves. None of the previous mentioned parameters made any difference , performance wise at first, but it seems that the Integrated Shaders Builder, with its very slow process, is improving. At least, now at 37%, the intro until the first zombie appears feels much better.
Mine: Core i7-10750H, RTX 2060 mobile 6GB, 16GB RAM, Fedora 38 Beta, Kernel 6.2.8-cbl (CachyOS LTO) Friend's: Ryzen 5 3600, RTX 2060 Super 8GB, 16GBRAM, Windows 11
Also I forgot this that happens everytime I click play to open the game (AMD drivers??):
Hmm, anyone else not seeing enemy outlines in the "listen" mode? Makes stealth in this game kinda hard. I am not sure if this is a Linux specific bug as I don't have a Windows install to test currently.
Hmm, anyone else not seeing enemy outlines in the "listen" mode? Makes stealth in this game kinda hard. I am not sure if this is a Linux specific bug as I don't have a Windows install to test currently.
I did not either
After waiting the Integrated Shader Compiler, the frame times and FPS got much better. Just not the VRAM and RAM consumption. On my case it improved from 10-21FPS on the title screen to 35-65FPS+ and improved a lot inside the game, but I am still at the lowest settings with almost my 6GB VRAM full.
Setting WINEDLLOVERRIDES="amd_ags_x64.dll=b" should show the correct amount of vram, and stop the pop up about out of date drivers for amdgpu users.
WINEDLLOVERRIDES="amd_ags_x64.dll=b"
Just stopped the message at the start, the amount still the same.
Setting
WINEDLLOVERRIDES="amd_ags_x64.dll=b"should show the correct amount of vram, and stop the pop up about out of date drivers for amdgpu users.
I can confirm this fixes both the driver update popup and the available VRAM for me, on the default Proton Hotfix, with an RX 6800 XT.
WINEDLLOVERRIDES="amd_ags_x64.dll=b" works to fix the vram and driver update for me as well, but it causes graphical glitches with the curtains in at the main menu.
I also have the same issue with the listening mode not showing outlines on moderate difficulty.
EDIT: Following this article it's possible that PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 could help Nvidia users.
WINEDLLOVERRIDES="amd_ags_x64.dll=b"works to fix the vram and driver update for me as well, but it causes graphical glitches with the curtains in at the main menu.I also have the same issue with the listening mode not showing outlines on moderate difficulty.
EDIT: Following this article it's possible that
PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0could help Nvidia users.
Tried that earlier, hide fixes nothing and nvapi causes a crash.
I just can't start the game. With or without WINEDLLOVERRIDES="amd_ags_x64.dll=b", not with proton hotfix, proton experimental, 7.0-6 or GE. Here is a gist of my steam system information.
Hello @grumpy-guy, your system is configured to use AMDVLK and AMDGPU-Pro. Can you test how the game behaves with mesa/RADV?
Hello @kisak-valve, What if I had an Nvidia? more specifically a GTX 1050 Ti, is there anything I can do? I have the same problem:
A GPU supporting D3D_FEATURE_LEVEL_12_0 or higher is required.
I am using the NVIDIA proprietary drivers
Playing for about 15-20 minutes usually results in the game freezing up with technicolored barf: 
Apologies for the phone pic, the issue doesn't get captured with screenshot tools for some reason.
Anyone else got awful load times? I have an NVME drive and loading the prologue takes upwards of 2 mins with all shaders compiled.
@Bitwolfies yes, even after shader compilation I still have to wait 1-2 minutes to get in-game from the main menu.
I just can't start the game. With or without
WINEDLLOVERRIDES="amd_ags_x64.dll=b", not with proton hotfix, proton experimental, 7.0-6 or GE. Here is a gist of my steam system information.
After today's update not just that happened as it said that the game was improperly closed. Which was not.
Latest Experimental bleeding edge should contain a fix for the game crashing when NVAPI is enabled. This should in turn allow DLSS to be used.
Interestingly, it appears that FPS drop to about 5 while DLSS is enabled and shaders are still being compiled in the menu. No idea why but hopefully it won't cause performance issues during actual gameplay.
Latest Experimental bleeding edge should contain a fix for the game crashing when NVAPI is enabled. This should in turn allow DLSS to be used.
Interestingly, it appears that FPS drop to about 5 while DLSS is enabled and shaders are still being compiled in the menu. No idea why but hopefully it won't cause performance issues during actual gameplay.
Tried it, still crashes. Unless it just has not been pushed out yet.
It's either that or Steam client didn't pick up the new version yet. In the meantime, you can take nvapi64.dll from the GitHub Actions artifacts here and replace Proton's library in Proton - Experimental/files/lib64/wine/nvapi/ with that one.
It's either that or Steam client didn't pick up the new version yet. In the meantime, you can take
nvapi64.dllfrom the GitHub Actions artifacts here and replace Proton's library inProton - Experimental/files/lib64/wine/nvapi/with that one.
Thats done it, experimental bleeding doesn't have it yet then.
Latest Experimental bleeding edge should contain a fix for the game crashing when NVAPI is enabled. This should in turn allow DLSS to be used.
Interestingly, it appears that FPS drop to about 5 while DLSS is enabled and shaders are still being compiled in the menu. No idea why but hopefully it won't cause performance issues during actual gameplay.
For me its the other way, I disabled DLSS In the menu and it tanked it to 5 fps.
Using the new nvapi dll linked by @Saancreed works for me! DLSS works properly, VRAM amount is correctly reported, and I swear it runs much more stable than before. Not sure what got fixed, but instead of crashing every 15-20 minutes with technicolor barf on the screen I can now play for hours. There was one crash after playing for 2 hours but then it worked for another 3 hours before I had to stop playing. Now, the only glaring issue for me besides the long load times is the lack of enemy outlines in the "listen" mode.
EDIT: Nope, spoke too soon. Crashed again with technicolor barf.
Replying to https://github.com/ValveSoftware/Proton/issues/6653#issuecomment-1488579027
@kisak-valve:
Omg, I feel embarrassed, typical layer 8 problem. You were right, now everything is working like a charm.