protonscr

Breathedge

appid 738520 1 threads, 1 open 17 comments last activity 2023-03-03
Latest maintainer comment · kisak-valve · 2023-03-03 · #3850
Hello @vhda, the workaround you mentioned is legally problematic and has been removed.
Threads

Breathedge proton open 2 matching

#3850 · 17 comments · opened 2020-05-09 · last comment 2023-03-03 by Patola
comment by taisph · 2021-04-11 · view · github
... Proton 5.13-6 nvidia 460.67 Ubuntu 20.04.2 LTS Linux 5.4.0-70-generic
comment by taisph · 2021-04-11 · view · github
... Proton 6.3-2 nvidia 460.67 Ubuntu 20.04.2 LTS Linux 5.4.0-70-generic
Recent activity
  • Patola · 2023-03-03 · Breathedge
    For the record, I also tried the "legally problematic" workaround and it did not work.
  • kisak-valvemaintainer · 2023-03-03 · Breathedge
    Hello @vhda, the workaround you mentioned is legally problematic and has been removed.
  • Zorrototo · 2023-03-03 · Breathedge
    OK if I start a new game, even on fresh prefix I also can reproduce the hang. If I start a new game and tick the skip intro box, it loads properly to the game without having the 'torture' intro.
  • Patola · 2023-03-03 · Breathedge
    The rest of the game seems to work well for me, the only part where I detected the hang was in that particular moment at the starting cinematics. What is your hardware and distro?
  • Zorrototo · 2023-03-03 · Breathedge
    I don't know I can play well I just tested and loaded different saves too.
  • Patola · 2023-03-03 · Breathedge
    Prior to testing I deleted the prefix and set it to standard 7.0-6 proton with no startup options as I said. I've only added `PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%` in a later attempt exactly to offset the fsync-...
  • Zorrototo · 2023-03-03 · Breathedge
    Does it crash if you (all of them): - delete the prefix (or rename it, to keep the old files just in case, the savegame for example) - use standard 7.0 Proton not experimental or beta - use standard kernel instead of TKG...
  • Patola · 2023-03-02 · Breathedge
    When the hang occurs, one process stays at 100% CPU the whole time in the call (caught by strace): `futex(0x7fc9d3e267a4, FUTEX_WAIT_PRIVATE, 12, NULL` Using `PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1` doesn't change anything

Proton versions over time

Launch lines, newest first

PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%

Launch options