Steam for Linux

Steam for Linux

MisterPeModder 23 AGO 2021 a las 16:37
[SOLVED] Most Proton games either stuck at "Preparing to launch" or "Adding process x for game ID x"
I'm running arch on a Nvidia-optimus enabled laptop, all native games I have tried works flawlessly, but most Proton games refused to launch, the only exceptions being Cuphead
and Human Fall Flat.

Games will randomly either be stuck on the "Preparing to launch x" or appear to run, but without any window (or sound) displaying.

Heres a log of me trying to launch Noita:
https://pastebin.com/DBRNKhSK

I tried:
  • All of available proton versions (even GloriousEggroll)
  • Launching with intel graphics
  • Using a EXT4 partition instead of my BTRFS one
  • Using various launch options such as PROTON_USE_WINED3D=1

Some specs:
  • OS: Arch Linux (5.10.60-1-lts kernel)
  • CPU: Intel i7-9750H (12) @ 4.500GHz
  • GPU: Intel CoffeeLake-H GT2 [UHD Graphics 630]
  • GPU: NVIDIA GeForce GTX 1660 Ti Mobile
  • NVIDIA drivers: nvidia-lts 1:470.63.01-2 nvidia-utils 470.63.01-1
  • Bumblebee: 3.2.1-21

Any help with fixing this issue would be greatly appreciated!
Última edición por MisterPeModder; 28 AGO 2021 a las 2:16
Publicado originalmente por class101 [OLED deck]:
Thank you, that's a lot of datas to dig into :D:

I will look again after my play session but there are indications that your iGPU is being used and no indication that your nvidia card is used.

Did you made a simple test like, disabling the iGPU in the bios settings and look if there is changes in the proton log ?

I know for sure that using a iGPU with recent Proton versions could fail as these GPUs do not implement the latest vulkan specifications, it is often a requirement to run the newest proton version properly
< >
Mostrando 1-15 de 24 comentarios
tfk 23 AGO 2021 a las 16:52 
This error seems the culprit:
Invalid resolutions constraints: 0x0

I see many threads when searching for this error which relate to video not being able to play. Another mentioned the use of a wide screen monitor. Although, that was an old game.
MisterPeModder 23 AGO 2021 a las 17:09 
From what I understand this line is a video file error, but it does not occur every time
MisterPeModder 23 AGO 2021 a las 17:15 
The proton log appears to be empty:
====================== Proton: 1623873472 proton-5.13-6b SteamGameId: 881100 Command: ['/home/yguaye/Games/steamapps/common/Noita/noita.exe'] Options: {'forcelgadd', 'wined3d'} depot: 0.20210723.18 pressure-vessel: 0.20210722.0 scripts: v0.20210722.0-0-gb142f90 soldier: 0.20210719.0 soldier 0.20210719.0 ======================
MisterPeModder 23 AGO 2021 a las 17:59 
Interesting, the "invalid resolusions" errors only occurs when I open the property menu of games
Marlock 23 AGO 2021 a las 18:29 
whaaaaaaaaaat?! :winter2019surprisedyul:

as in... if you go to the properties menu in the steam libray before launching them?!
MisterPeModder 23 AGO 2021 a las 19:32 
yup
Marlock 23 AGO 2021 a las 19:45 
that's beyond bizarre :winter2019neutralyul:

maybe the menu has been implemented as a floating window and isn't destroyed properly, ends up as parent to the launched process and doesn't carry a proper screen reference for it to inherit... or whatever quirk like that...

idk... it's very buggy behaviour, and definitely steam's fault in some way!

did you try alt-tabbing back and forth before launching? does that shake the issue away?

does it affect any game you launch afterwards? or just the one whose properties were opened/edited?
MisterPeModder 23 AGO 2021 a las 19:48 
It doesn't affect the game launch at all, I tried relaunching steam after changing proton version, but no luck
looks like an issue some peoples seem to have solved by disabling startup movies of games like that. Maybe a problem with the code responsible of automatically detecting the desktop resolution.
MisterPeModder 24 AGO 2021 a las 11:25 
I had some progress (?), the game launches (still with no window) and produces a proton log:
steam log[pastebin.com]
proton log[pastebin.com]
class101 [OLED deck] 24 AGO 2021 a las 17:46 
Your log reveals you are using

- An outdated version of Proton, v5.13-6b, you should always use the latest release or the latest Proton experimental
- This crash seems connected to a wrong use of PROTON_USE_WINED3D. You should never use at all this option. It will downgrade all the rendering engines in Proton, like using a simple Wine installation and so on, even if it works, you will have bad performances because all the components being developped by Valve will be disabled (DXVK, VKD3D, etc...). It is best to not use launch parameters unless you really know for what they are intended to be used for, protondb has a lot of misinformations about this, peoples are posting parameters they don't even know what they realy do.

You should focus on getting the game to run without using this launch option at all in all your games

If I were you, I'd start fresh by dropping the proton prefix in steamapps/compatdata/881100/ to reset it from scratch and make sure you use the latest proton release 6.x or experimental and no special launch options.
Última edición por class101 [OLED deck]; 24 AGO 2021 a las 18:14
MisterPeModder 25 AGO 2021 a las 11:37 
Proton v5-12-6b just happened to be the last version I tested, after removing the arguments, set the proton version to experimental, then removing the steamapps/compatdata/881100/ folder, The game gets stuck at "Installing breakpad exception handler for appid(steam)/version(1626824053)" when I launch it.
class101 [OLED deck] 25 AGO 2021 a las 12:31 
This is the relevant error here to fix, add this as launch parameter, this will create a steam-881100.log file in your home folder

PROTON_LOG=1 %command%

Another thing to check is the operating system logs

journalctl -xb -p 3
MisterPeModder 25 AGO 2021 a las 17:50 
No logs are produced when I try to launch the game this way, not even a file.
As the kernel log, the only relevant lines are:
Aug 25 19:57:03 kernel nvidia-gpu 0000:01:00.3: i2c timeout error e0000000 Aug 25 19:57:03 kernel: ucsi_ccg 0-0008: i2c_transfer failed -110 Aug 25 19:57:03 kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110

Apparently, those errors are related to my GPU's usb port, but since I can't even get the game to launch using the Intel iGPU, this is probably not the cause
< >
Mostrando 1-15 de 24 comentarios
Por página: 1530 50

Publicado el: 23 AGO 2021 a las 16:37
Mensajes: 24