Latest maintainer comment ·
kisak-valve · 2020-11-02 ·
#182Looks like a general issue happened: [code] Also being tracked at #4269.
Threads
#182 · 22 comments ·
opened 2018-08-22 · last comment 2020-11-02 by kisak-valve
#211 · 10 comments ·
opened 2018-08-23 · last comment 2020-04-20 by qunka
#490 · 3 comments ·
opened 2018-08-25 · last comment 2018-08-25 by kisak-valve
Recent activity
- Looks like a general issue happened: [code] Also being tracked at #4269.
- Unfortunately the game crashes at startup with Proton 5.13 (and it doesn't run the installation scripts). I already have Steam Runtime Soldier installed and tried running the game with a clean prefix. [steam-282800.log](...
- Hello @DraconYale, `err:steamclient:create_win_interface Don't recognize interface name: SteamUtils010` looks like a line of interest in your log. Please retest with Proton 5.13.
- I had that problem for a short while after they updated the network code. What worked for me was running the game with steam-runtime which downloaded something called SteamLinuxRuntime_soldier. After that it works with b...
- Game can't connect to Steam even if some months ago it was working perfectly. I tried setting `PROTON_NO_ESYNC=1` but it didn't work. [steam-282800.log](https://github.com/ValveSoftware/Proton/files/5474534/steam-282800....
- Most likely yes, that could workaround the base requirement of Proton. Also using an futex-multi-wait (fsync) enabled kernel would avoid the use of esync.
- (I assume setting launch options to `PROTON_NO_ESYNC=1 %command%` would also work?)
- > Hello @qunka, please add your experience to #182. Also, please attach logs as a file or use a [gist](https://gist.github.com). Done and done. Time to reopen, perhaps?