search

ValveSoftware / Proton

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

Subnautica (264710) #79

Open cjwijtmans opened 6 years ago

cjwijtmans commented 6 years ago

when you start subnautica it stalls at startup. when you kill wineserver the game continues to start up.

jonbitzen commented 4 years ago

I think there is a regression on Proton 5.0-1. When you start the game the water ocean background in the splash screen isnt visible. If you try to enter a saved game the screen is black, you get sound for a short bit, then it freezes.

kisak-valve commented 4 years ago

Hello @jonbitzen, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box. Also, what is the most recent version of Proton that isn't affected by the regression?

jonbitzen commented 4 years ago

@kisak-valve

I just tested Proton version 4.11-12, and that one works. I have the water background, and I am able to get all the way into a game, and play it after loading.

Attached is the log you requested, running with Proton 5.0-1

steam-264710.log

doitsujin commented 4 years ago

@jonbitzen can you try putting a file dxvk.conf next to the game's executable with the following contents:

dxvk.enableOpenVR = False

I had someone test the game on Proton 5.0 and apparently it still works for them, so not sure what's going on here.

jonbitzen commented 4 years ago

That fixed it.

kisak-valve commented 4 years ago

The workaround has been integrated at https://github.com/ValveSoftware/dxvk/commit/fbca62df8e09ef6962f300a78e01056e020a3081 into Proton 5.0-2.

rbjorklin commented 4 years ago

Has there been a regression here? The game launches and runs fine under 4.11-13 for me and completely refuses to start under 5.0-5. Trying to run it with PROTON_LOG=1 %command% produces a log with 4.11-13 but nothing with 5.0-5.

system-info.txt compat_log.txt

This only shows up with 5.0-5:

[2020-04-08 17:25:24] GetCompatibilityToolCommandLineInternal: '/home/rbjorklin/.local/share/Steam/steamapps/common/Proton 5.0'/proton getcompatpath
[2020-04-08 17:25:24] Foreign install path for AppID 264710:
[2020-04-08 17:25:24] Foreign install path for common redist for AppID 264710:
kisak-valve commented 4 years ago

Hello @rbjorklin, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

rbjorklin commented 4 years ago

Hi @kisak-valve,

As stated in my initial comment that doesn’t produce a log file with 5.0-5 so I’m guessing the issue occurs before that is being executed?

kisak-valve commented 4 years ago

Looking at your system information again, I suspect that your system ran out of disk space while unpacking Proton 5.0. Maybe try freeing up some disk space, then delete dist in <steamapps folder>/common/Proton 5.0/ and re-run the game with it configured to run with Proton 5.0?

nentibusarchitectura commented 4 years ago

I can't run subnautica at all on any version of proton on my computer.

System info gist:

https://gist.github.com/nentibusarchitectura/325b0016eac6b31babf302421a200d1f

Attached log from running attempt with proton 5.0-6:

https://github.com/ValveSoftware/Proton/files/4496742/subnautica-proton506-steam-264710.log

kisak-valve commented 4 years ago

Hello @nentibusarchitectura, looking at the diagnostic info in your system information, it looks like there's some very old vulkan icd files in /etc/vulkan/icd.d/. Can you identify where they came from and check if moving/removing them has an effect?

nentibusarchitectura commented 4 years ago

/etc/vulkan/icd.d/

Hi Kisak,

Thanks for looking at this, I've checked where the files came from, as you can see my system thinks the files came from your PPA's packages, however I have had other repositories in the past (oibaff) , and won't be surprised if those files are from older packages...

root@kirby-z:/etc/vulkan/icd.d# dpkg -S *
mesa-vulkan-drivers:i386: /usr/share/vulkan/icd.d/intel_icd.i686.json
libgl1-mesa-dri:i386: /etc/vulkan/icd.d/intel_icd.i686.json
dpkg-query: no path found matching pattern *intel_icd.json_BAK*
libgl1-mesa-dri:amd64: /etc/vulkan/icd.d/intel_icd.x86_64.json
mesa-vulkan-drivers:amd64: /usr/share/vulkan/icd.d/intel_icd.x86_64.json
libgl1-mesa-dri:i386: /etc/vulkan/icd.d/radeon_icd.i686.json
mesa-vulkan-drivers:i386: /usr/share/vulkan/icd.d/radeon_icd.i686.json
libgl1-mesa-dri:i386, libgl1-mesa-dri:amd64: /etc/vulkan/icd.d/radeon_icd.json
libgl1-mesa-dri:amd64: /etc/vulkan/icd.d/radeon_icd.x86_64.json
mesa-vulkan-drivers:amd64: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json

I'm going to delete them and reinstall the packages that contains them...

nentibusarchitectura commented 4 years ago

Hi Kisak

Looking at the files on the mesa-vulkan-drivers package I can see that in your package the icd.d files live on /usr/share/vulkan/icd.d/ and not /etc/vulkan/icd.d so definitively the old files came from some other PPA and somehow were left over when I replaced the mesa drivers with your repository.

I've removed the old files and just in case forced a reinstall of both: "mesa-vulkan-drivers" and "libgl1-mesa-dri"

apt install --reinstall mesa-vulkan-drivers libgl1-mesa-dri

nentibusarchitectura commented 4 years ago

Hi Kisak,

It fixed the problem! not only it fixed the issues with Subnautica, my issues with Risk of Rain 2 are gone too!

Many, many thanks!

PCVirus25 commented 4 years ago

Hi Kisak

Looking at the files on the mesa-vulkan-drivers package I can see that in your package the icd.d files live on /usr/share/vulkan/icd.d/ and not /etc/vulkan/icd.d so definitively the old files came from some other PPA and somehow were left over when I replaced the mesa drivers with your repository.

I've removed the old files and just in case forced a reinstall of both: "mesa-vulkan-drivers" and "libgl1-mesa-dri"

apt install --reinstall mesa-vulkan-drivers libgl1-mesa-dri

This recipe did not work on my PC. Or I did something wrong. Can I write in steps what needs to be done?

RossComputerGuy commented 4 years ago

@PCVirus25 Did you run sudo with apt? Or are you running something other than Ubuntu, Debian, or Linux Mint?

nentibusarchitectura commented 4 years ago

Hi Kisak Looking at the files on the mesa-vulkan-drivers package I can see that in your package the icd.d files live on /usr/share/vulkan/icd.d/ and not /etc/vulkan/icd.d so definitively the old files came from some other PPA and somehow were left over when I replaced the mesa drivers with your repository. I've removed the old files and just in case forced a reinstall of both: "mesa-vulkan-drivers" and "libgl1-mesa-dri" apt install --reinstall mesa-vulkan-drivers libgl1-mesa-dri

This recipe did not work on my PC. Or I did something wrong. Can I write in steps what needs to be done?

@PCVirus25

What I posted is valid for Ubuntu 18.04.x using Kisak's Mesa PPA

Installing/removing packages with "apt" always requires elevated rights, so you need to prefix with sudo:

sudo apt install --reinstall mesa-vulkan-drivers libgl1-mesa-dri

Or just run sudo -i (or use su -) to completely switch to root account and gain elevated privileges.

PCVirus25 commented 4 years ago

Installing/removing packages with "apt" always requires elevated rights, so you need to prefix with sudo:

I know. I meant that the team worked, but the problem did not disappear.

PCVirus25 commented 4 years ago

@PCVirus25 Did you run sudo with apt? Or are you running something other than Ubuntu, Debian, or Linux Mint?

Yes, I used a "sudo" with "apt". (sorry for my English)

ghost commented 4 years ago

To add a datapoint : I was able to recently play Subnautica from end to end on my Debian without any workaround or significant issues. There are very minor annoyances (like opening containers while moving sometimes behaves improperly), but I'm not sure they're linux-specific, and it doesn't impair gameplay.

If it was just me, I'd simply fill a whitelist request here, but it seems that some people are still having issues... should I go ahead anyway ?

StarrKiss commented 4 years ago

This game is VERY low FPS for me on Manjaro- and in addition, there is MASSIVE pop in and V low res textures even very close to the object.

ThisNekoGuy commented 3 years ago

@kisak-valve

Compatibility Report

System Information

I confirm:

Proton log: steam-264710.log

Symptoms

Game works, but it swaps the left and right triggers on my Xbox controller. (Thinks RT is LT and LT is RT)

Reproduction

Game was started with:

gamemoderun %command%
ChildishGiant commented 2 years ago

For me the game was working literally yesterday and now it doesn't do anything on launch? steam-264710.log

kisak-valve commented 2 years ago

Hello @ChildishGiant, err:module:import_dll Library WindowsCodecs.dll (which is needed by L"Z:\\mnt\\hdd\\steam\\steamapps\\common\\Subnautica\\UnityPlayer.dll") not found looks like the line of interest in your log. Since the Proton Experimental build is experimental-7.0-20220331, it's not clear why that library would go missing in the last day if nothing else has changed.

Maybe try verifying the integrity of Proton's files?

ChildishGiant commented 2 years ago

Verifying didn't work but reinstalling did, RIP save because I forgot to back it up. The files it was complaining about were there but I guess the dll somehow got corrupted and the verification missed it?

skauertz commented 11 months ago

I'll just leave that here since it seems the most appropriate. The same issue occurs with Subnautica: Below Zero.

Compatibility Report

System Information

I confirm:

Symptoms

Game hangs on a black screen with in-game mouse cursor visible and reactive, but does not complete start-up (see Proton log.

When launching the game using PROTON_USE_WINED3D=1 %command% it starts, but there are visual glitches, the performance is bad and the Steam overlay does not work.

It worked fine a few months ago under Proton 8.0-3 with the same system setup.

To make it work, I had to install Proton-GE 8.3 from May 2023. Latest Proton-GE 8.21 has the same behaviour.

Reproduction

Use recommended Proton 8.0-4 to run the game without any launch options.

kisak-valve commented 11 months ago

Hello @skauertz, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

skauertz commented 11 months ago

Hello @skauertz, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

Done, added to my previous post.

kisak-valve commented 11 months ago

Thanks, your Proton log looks like a Steam overlay issue similar to https://github.com/ValveSoftware/steam-for-linux/issues/9586.

skauertz commented 11 months ago

That may be the case, I notice there are no overlay elements (FPS counter, broadcast info) when it hangs. But launching with the overlay disabled yields the same issue. Proton log with overlay disabled for reference.

Something else: Alt-tabbing out of the game while it hangs takes like 10 seconds, but once it does the game continues to the main screen. It is sufficient to open the app switcher by holding Alt-Tab, I don't even need to bring another app to the foreground. However, when I bring the game to the foreground again, video instantly freezes with audio continuing to run. Doesn't matter if Overlay is enabled or not.