protonscr

NaissancE

appid 265690 1 threads, 0 open 6 comments last activity 2019-06-12
Threads

NaissancE proton closed 2 matching

#1231 · 6 comments · opened 2018-09-04 · last comment 2019-06-12 by Simmonz
comment by glubsy · 2018-09-04 · view · github
... launch options) such as `PROTON_LOG=1 PROTON_DUMP_DEBUG_COMMANDS=1 DXVK_HUD=1 %command%` you can find proton specific log in ...
comment by glubsy · 2018-09-04 · view · github
... steam-265690.log) with `PROTON_LOG=1 PROTON_DUMP_DEBUG_COMMANDS=1 DXVK_HUD=1 %command%` `PROTON_USE_WINED3D11=1` doesn't change much it ...
Recent activity
  • Simmonz · 2019-06-12 · NaissancE
    I can confirm it launched and played for me in Proton 4.2-7 as well. It did freeze after changing the resolution and AA but after killing the process and relauching the game it was fine. I've since relaunched multiple ti...
  • DarkFenX · 2019-06-12 · NaissancE
    Starts in 4.2-7, i suppose issue can be closed.
  • DarkFenX · 2019-03-30 · NaissancE
    This is strange because it used to work under vanilla wine (steam launched from within wine). Also worth to mention that its still doesn't work with proton 4.2-1.
  • glubsy · 2018-09-04 · NaissancE
    Here's a [proton log](https://gist.github.com/glubsy/b63dd93a680ccbcbb643e245f8ea1a8c) (/home/user/steam-265690.log) with `PROTON_LOG=1 PROTON_DUMP_DEBUG_COMMANDS=1 DXVK_HUD=1 %command%` `PROTON_USE_WINED3D11=1` doesn't ...
  • Simmonz · 2018-09-04 · NaissancE
    https://gist.github.com/Simmonz/52713185a5e0abe7d3686717467cdff9 Couldn't find any crash logs even after adding the launch command you provided.
  • glubsy · 2018-09-04 · NaissancE
    You should post what Steam reports as system information: in the Steam client go to help menu -> System information -> right click copy all, paste into a [gist](https://gist.github.com/) or pastebin. Also try to include ...

Proton versions over time

Launch lines, newest first

PROTON_LOG=1 PROTON_DUMP_DEBUG_COMMANDS=1 DXVK_HUD=1 %command%

Launch options