[steam-1902150-WINEDEBUG=+openxr.log](https://github.com/ValveSoftware/Proton/files/9544042/steam-1902150-WINEDEBUG.%2Bopenxr.log) And ...

Ran the game with `WINEDEBUG=+mfplat %command%` in Proton Experimental to get only the mfplat messages. Log is ...

Well, used `WINEDEBUG=+openxr %command%` and got this log -- interesting line: `[OVRPlugin][ERROR] ovr_Initialize failed: Unable to load ...

... Sending the proton log, maybe also using with `WINEDEBUG=openxr %command%` might help?

Ran the game with WINEDEBUG=+vrclient, maybe it can offer useful information... The log ended up with 213 ...

> By adding +dxgi,+vulkan do you mean add it to PROTON_LOG or WINEDEBUG? Add those to WINEDEBUG, in ...

Maybe the problem can be discovered using the +relay in WINEDEBUG

... com/ValveSoftware/Proton/issues/3291#issuecomment-644193811 was spot on, the Winedebug flags were eating my performance away

So, my laptop repeat the exact same behaviour, and I found where the `winedebug -all` come from. So ...

> Hello [@arazilsongweaver](https://github.com/arazilsongweaver), please share a Proton log without WINEDEBUG set. `System WINEDEBUG: -all` makes ...

BTW, @kisak-valve do you really require `WINEDEBUG=+module` ? this produces either more noise than help `WINEDEBUG=+loaddll ...

@GoLD-ReaVeR `WINEDEBUG="+rawinput"` should do

... to fetch a log with the following launch options instead? WINEDEBUG="+timestamp,+pid,+tid,+seh,+debugstr,+module" %command%

... No crash also with > WINEDEBUG=+relay,+tid When we set such flags, do we also initialize memory to ...

@Fatmice WINEDEBUG=+timestamp,+pid,+tid,+debugstr,+server

I was only able to run/install it with wine using `WINEDEBUG=+heap`

... prefix ``` WINEPREFIX=/home/lukas/.steam/steam/steamapps/compatdata/271590/pfx WINEDEBUG=+heap wine Installers/Rockstar-Games-Launcher.exe ```

... Can you add `+win` to your `WINEDEBUG` variable (either through the `user_settings.py` in Proton GE's folder ...

... You can cut down on that by passing a custom `WINEDEBUG` variable in your launch options. By default ...

... Got two logs with that winedebug config, one skipped/no mouse and one played through/mouse ok (labeled ...

Can you get a log with `WINEDEBUG=+fnamf,+mfplat` ?

... I'm guessing it's because you have an extra %command% in there before the WINEDEBUG=.

@madewokherd - Tried 8.0-3 with command "PROTON_LOG=1 %command% WINEDEBUG=+fname,+mfplat %command%" Got: [this thing.log ...

It seems setting WINEDEBUG to *anything* other than the default of `-all` works, I set `WINEDEBUG=+timestamp` and ...

@JWolvers @Newbytee Does activating ntdll debug channel help? (WINEDEBUG=+ntdll %command%)

... So indeed a race condition. (And adding WINEDEBUG=+ntdll %command% has no effect)

... So indeed a race condition. (And adding WINEDEBUG=+ntdll %command% has no effect) It appears that this build ...

0x8004100e is WBEM_E_INVALID_NAMESPACE, a log with WINEDEBUG=+wbemprox might be useful.

Here you go as well, a log with "WINEDEBUG=+wbemprox": [steam-936790.log](https://github.com/ValveSoftware/Proton ...

Ok, this is with `WINEDEBUG=+wbemprox PROTON_LOG=1 %command%` I'm not really sure what the command you ...

@fxzxmicah Default with maybe `WINEDEBUG=+loaddll` should be enough i believe

DispatchMessage could go anywhere. WINEDEBUG=+msg,+win,+seh might provide more information.

@kisak-valve do you want me to set any additional `WINEDEBUG` flags?

@galister can you run with `WINEDEBUG=+vrclient`? it would give me a bit more info.

@roryyamm Can you run with `GST_DEBUG=5 WINEDEBUG=+mfplat` and upload the proton log file? And what h264 ...

... If you could set the following variables to your launch argument for log: `PROTON_LOG=1 WINEDEBUG=+module,+xaudio2 ...

... if you want to log, try `WINEDEBUG=+setupapi,+mmdevapi` (or maybe `WINEDEBUG=+setupapi,+mmdevapi,+reg` although those reg ...

... From the debug logs ('WINEDEBUG=+hid,+mmdevapi'), the game enumerates audio endpoints but doesn't appear to use ...