Did you use `PROTON_LOG=1` or `PROTON_LOG=1 %command%`? If you used the first one, try the second ...

Can you add `PROTON_LOG=1` to your launch options and show us your `~/steam-271590.log` after your ...

I replaced my launch options with `PROTON_LOG=1` but it seems like there is no `~/steam-271590.log ...

@Juppstein Add PROTON_LOG to your launch command `PROTON_LOG=1 %command%` it should show up in your $HOME dir ...

> I have no particular launch options, just `PROTON_LOG=1 %command%`. @mattlennon3 PROTON_LOG=1 enables log, which may decrease ...

> > I have no particular launch options, just `PROTON_LOG=1 %command%`. > > @mattlennon3 PROTON_LOG=1 enables log, which may decrease ...

Just PROTON_LOG=+hid?

... when I set `PROTON_LOG=1 %command% PROTON_USE_D9VK=1 %command%`? When I set only `PROTON_LOG=1 %command%` then it ...

Use `PROTON_LOG=1 PROTON_USE_D9VK=1 %command%`

PROTON_LOG generated with radv.

... PROTON_LOG=1 %command% or just PROTON_LOG=1 I do not remember which onet I used the last time ...

... I'm using PROTON_LOG=1 %command% in the launch options and no log is created

... I've got Steam over Snap, and after setting up `PROTON_LOG=1 %command%`, I found the log files ...

BTW one way you can see it in Proton is to run with PROTON_LOG=+xaudio2. That will log ...

... Is it possible to get a log with PROTON_LOG=+module,+path,+file ? That may be big but should ...

... Also if you can run Cosmoteer on Proton and enable default logging with PROTON_LOG=1 %command% in launch ...

> [@HansKristian-Work](https://github.com/HansKristian-Work) is there any way to enable PYROVEIL without proton_log clogging up ...

> > [@HansKristian-Work](https://github.com/HansKristian-Work) is there any way to enable PYROVEIL without proton_log clogging up ...

Do you have a PROTON_LOG? It's probably the NV compiler bug now.

use `PROTON_LOG=1 %command% +in_terminal 1`

@VincentGuinaudeau I've put ``PROTON_LOG=1 %command%`` on launch options, but I have no fatal errors in the ...

@chanakaya then check the logs, try to launch it with `PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens ...

PROTON_LOG=1 %command% = https://pastebin.com/nsNGcQRU

PROTON_LOG=1 %command% = https://pastebin.com/PuB8wxsx

... In your case it should be `PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% SKIPINTRO`, or just simply `PROTON_LOG ...

... In your case it should be `PROTON_LOG=1 PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% SKIPINTRO`, or just simply `PROTON_LOG ...

> [`PROTON_LOG=1 %command%`](https://github.com/ValveSoftware/Proton#runtime-config-options) > Hello [@neverded](https://github.com/neverded), please ...

@cybik Post a log (`PROTON_LOG=1`) I suppose.

@vsod99 can you send me both a PROTON_LOG w/ WINEDEBUG=+bcrypt and the output `cat /proc/(halo PID ...

... Wasn't running with `PROTON_LOG=1` at the time so no log for that.

Did you set the launch option to `PROTON_LOG=1` or `PROTON_LOG=1 %command%`? If the former, try the ...

Works with `PROTON_LOG=1 %command%` so closing as working as intended I suppose. Still think its odd that ...

... Simply go to game properties -> launch options and enter `PROTON_LOG=1 %command%` that's it right?

Better to send this log `PROTON_LOG=1 %command%` no ?

@leillo1975 Actually, please put `WINEDEBUG=+dinput` instead of `PROTON_LOG`.

`PROTON_LOG=1` log: https://gist.github.com/gardotd426/fa6f5ee08a9b69b6131e9b469ae99692

Apparently adding `PROTON_LOG=1` option breaks the launcher. :thinking:

What does PROTON_LOG say if you grep for pyroveil?

... issues/8408#issuecomment-2657714906 If you haven't, you need to add `PROTON_LOG=1` to your steam command

... should be enabled first with the following command: `PROTON_LOG=1`. Then try to run the game. The output ...