Quake Champions (611500)

[JR1994]

I am requesting that Quake Champions be added to the white list. I have verified that it works via Steam Play. My Steam system info is here.

[cjfcollins]

I get horizontal axis lock while moving my mouse at low speeds in Quake Champions with Proton.

Upgrading to the latest version of DXVK also almost doubled my performance.

[kwahoo2]

Crashes for me at the menu loading (after warning screen)

https://gist.github.com/kwahoo2/e3c89a9b3798764991df3fc65bda4c2c

[Leopard1907]

Did you played it actually? Afaik that game needs Stream Output which DXVK doesn't have.

[aqxa1]

@Leopard1907
IIRC reports were suggesting that it only uses the feature at higher settings, so that is why it may not be crashing for some. I can only get the game to work with DXVK on native Windows, and it didn't crash for me in that environment at least.

[Leopard1907]

@thirdeyefunction

And if an app is not working properly on some settings due to a missing feature or similar , that should not be in the whitelist.

Because whitelist represents " tested , somewhat Steam Certified " apps , at least for now.

[aqxa1]

@Leopard1907
Agreed, just giving additional context.

[thunder1410]

I tried playing it but it crashed after sometimes with 2fps in the tutorial. Highest video settings on full HD.
Main menu works fine
OS: ubuntu 18.04.1
GPU: AMD RX 580
CPU: I5-4460
GPU driver: mesa 18.3.0
Game is installed on an NTFS hard drive. But other games don't have problems with it.

[JR1994]

I have gone through the tutorial and so far I was able to play. I get some stuttering, but I think that is because I am using Intel graphics. I have a second laptop with NVIDIA that I am going to test on shortly.

[Zeioth]

I have +200 hours played, the game runs great. But since DXVK is not fully implemented yet, you will experience some crashes related to stream output: For more info see this.

The crashes happen 100% of the time on these 3 specific moments:
After loading the map "Lockbox"
After loading the map "Vale of pnath"
When the character/champion named "Sorlag" uses his ability: Acid spit.

And about performance, I recorded some videos.

UPDATE: I've recorded a new video, this time, using Steam for Linux.

[czarnyckm]

The game works fine with ultimate settings with the exception to the Details Level in postprocessing it must be set to low otherwise i get crash after use a weapon.
I played tutorial and one multiplayer team death match.
Resolution:
2560x1440 at 60fps
ryzen 7 2700x
32GB ram
nvidia gtx 1070 Driver 396.51

[sigzegv]

using PROTON_NO_ESYNC=1 %command% seems to greetly reduce stuttering on quake champions.

[Zeioth]

using PROTON_NO_ESYNC=1 %command% seems to greetly reduce stuttering on quake champions.

I can't reproduce this.

Please make sure the shader cache is fully loaded. The game will stutter until you load every single map and model of the game into screen at least once. For this... You need to play the game for an hour or so maybe.

Need confirmation.

EDIT: Some videos without 1,2 and with 1, 2 esync .

[sigzegv]

I am not speaking about shader caching.
In tutorial's first room, with esync my mouse is not smooth and my framerate in unstable (and stutters from time to time) : 40 to 80 fps in that really simple room (I have not set any particular system conf for esync). And without esync, my mouse is really smooth, and my framerate is constant 90/110 fps.

I don't know why some people have no issues with esync, but I hope this can help anyone. (My system is archlinux, I have a gtx 1070, and in the game options Details and Post Processing are set to low to avoid crashed).

[thunder1410]

Ok, I tried playing it again with graphics on LOW and PROTON_NO_ESYNC=1 %command% in the launch option. First I did the tutorial which worked ok, it had some stutters because it needs to load the shaders. Then I queued for an online match where I just crashed to desktop in the loading screen, tried to rejoin but didn't work. Maybe something with the map?
I restarted and tried again which worked, played a full instagib deathmatch game with only some stutters at the start. (I won so it worked great)
system information: https://gist.github.com/thunder1410/76897c9bd211c74b30968baa4037ce96

[Zeioth]

@thunder1410 see this
@sigzegv the more cores your CPU have, the better performance you can expect from esync. I use Ryzen 1700, which has 16 threads, and when I play QuakeChampions I have a CPU usage of 75% or so in all threads.

[NoXPhasma]

I can't get the game to even get to the main menu, I always get this error and then it exit: https://i.imgur.com/snmuArf.jpg

https://gist.github.com/NoXPhasma/17aaaab0d5841d6a92dac4d184a9592f

[aqxa1]

Yeah, I get the same error as @NoXPhasma. If you run the game with wine-3.15, the error changes to "Error: timeout". Possibly the change is due to winhttp now using windows sockets resulting in slightly different behaviour.

[kisak-valve]

Quake Champions (611500)/Doom DEMO (479030) not working with linux mint 19

Issue transferred from #1127.
@logan001 posted on 2018-09-01T11:57:15:

Quake Champions crash in different places. Last time i didn't get past the health warning.
But sometimes i get in the arena and even move a bit. Im guessing thats because someone kills me and game crash. Why i guess that? well the game loads the map horible therefor the game freeze a lot with each room/character it has to load. I have no clue why this happens in all games under wine.

Doom (Demo) i can only see it for a brief moment in process list but nothing the screen. Of course except 1st setup window with DX and whatelse.
I've tried a few more games to test proton. mostly the free to play ones since i dont have many games that works only on windows and dx10/dx11
None of the games i've tried worked. the one that i remember are ashses of singularity/path of exile
i've tried a few more but i dont rememeber. i just picked them up from store.

Any suggestions?

Edit: i've installed Tomb Raider Anniversary (old game) and its working. im guessing dx11/dx10 are not working

[doitsujin]

@Leopard1907 you're right, and this game requires Stream Output even on lower settings. It should however work with pretty much no issues once that is implemented.

[logan001]

@doitsujin sorry i'm confuse with your answer: the game should work but should not work cause its missing stream output? :)
Does somneon knows a game that is free with dx11 and its working with proton so that i can give it a try?
im pretty much sure at this moment that proton is a quite useless for me on dx10/dx11 games. Don't know what's wrong with it.

[kisak-valve]

Hello @logan001, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[logan001]

@kisak-valve here it is https://gist.github.com/logan001/bfff8843809ad5a7ca118e64c385c2c8
i've tried both version of proton currently available. same results with both
Edit: i have no clue how to add that link lol

[alvarlagerlof]

This one keeps on crashing randomly for me. So annoying. Any suggestions on how to fix?

I play at 4k on a GTX 1080. I get 60fps with occasional dips to 45.

[Zeioth]

• Play on low specs.
• Avoid the maps Lockbox and Vale of pnath.
• Avoid sorlag F skill.

It won't crash as long as you do that.

[Leopard1907]

That game should not be in the whitelist and all hot-blooded Linux users should stop creating idiotic whitelist request.

Obviously , most of them are just booting the game , check menus etc. and call it a day.

@kisak-valve @Plagman Please ignore many whitelist requests like this. They're far from truth.

[Zeioth]

It can be white listed as soon as DXVK Stream Output is implemented, or the game implements native vulkan support (which is planned, but here's no date announced). Whatever it somes first.

[Leopard1907]

Yet , there is no Stream Output anywhere and still that guy somehow requested that game to be whitelisted.

How is that normal to you?

[Zeioth]

Don't take me wrong, I agree with you.

[virnik0]

With latest beta bleeding edge fixed even the stutter. The game is fluid again. Thank you! From my perspective, problem solved.

[virnik0]

NICE! Downloaded new bleeding edge build, and it nows pre-gen shaders! Thanks a milion!

[suabicii]

After new update when I try to run the game I see black screen... then nothing is going on – regardless of the Proton version ('normal' Proton, Experimental, GE etc.)

If it's important my OS is Pop_OS! 22.04 and kernel 5.17.5-76051705-generic

Maybe you can read something from log
steam-611500.log

[gofman]

I had a very brief look and that looks like a dxvk issue. Game loads fine to main menu with PROTON_USE_WINED3D=1.

The crash is an attempt to call NULL pointer. Maybe (e. g.) some d3d call failed to return an interface and the game is trying to use an unitialized one (just guessing).

Also, this:

err: D3D11: CreateGeometryShaderWithStreamOutput: Rasterized stream not supported
but not sure if that is related.

[d3rhans]

@suabicii @gofman issue is already fixed in the test version of the game, the patch will likely come into the live version mid July

[gofman]

@d3rhans Thanks for the update! Could you please tell me what is the technical problem if possible (possibly email me to pgofman@codeweavers.com), as since it works on Windows and with PROTON_USE_WINED3D there is possibly a room for Proton bug we might want to fix.

UPDATE and knowing at once what is failing may save many hours debugging

[d3rhans]

I wouldn't know what the actual problem is, but I can ask the devs of the game if they can provide any information. To my understanding it is related to an update of the game's anti-cheat though.

Btw. I also cannot start the game with PROTON_USE_WINED3D=1 in the launch option (tried several proton versions) and I also get the err: D3D11: CreateGeometryShaderWithStreamOutput: Rasterized stream not supported message in the log for the test version (steam app id is 743650 if you want to try that one) which seems to work perfectly fine, so I don't think this is what cause the crash.

[gofman]

Oh yeah, I am sorry, my quick check was totally misleading. The critical bit how It actually worked for me was not PROTON_USE_WINED3D but my local build with a load of WIP patches :) I found which of WIP patches fix it but that part is not quite ready and, more important, requires custom kernel patches to really work, so if it is fixed in the next update already doesn't worth trying to bring that in somehow.

[d3rhans]

FYI: The update that fixes proton compatibility for Quake Champions went live today. Game works fine again on proton experimental and latest GE-Proton (and runs on the Steam Deck as well, in case anyone cares). I did some testing earlier today and everything runs smoothly.

[andreymal]

Proton Experimental (both non-beta and bleeding-edge) has a lot of small freezes even in the main menu
Proton 7.0-3 works fine without freezes

[kisak-valve]

Hello @andreymal, please add PROTON_LOG=1 %command% to the game's launch options, see if the same behavior happens with the extra overhead of the logging, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[d3rhans]

I just did a quick test with Proton Experimental (bleeding edge) and Proton 7.0-3. Performance is about the same. There are some small stutters on both when the game is first started or a map is played for the first time, due to shader compilation, but that goes away after a bit (and is nothing new but seems to have gotten quite a bit better compared to maybe 2 years ago).

QC is one of those games that benefits greatly from dxvk-async, hence I usually use GE-Proton for it, doesn't cause any issues with the game or its AC and makes the stutters go away.

[clintar]

GE changes the mouse for me for some reason. I'd like to know why.

[Sid127]

@clintar Proton GE has a patch to sync your raw input sensitivity to Windows ones. it’s in wine-staging and Proton doesn’t have it

[clintar]

Great... once that goes in i won't be able to play at all

[clintar]

And also, Experimental gave me the same stutters. 7.0-3 is smooth. Well, fps is smooth. I can't stand the movement/animations now after not being able to play this game for a while, but I guess that's the way it's always been?

[clintar]

@kisak-valve
System Info:
https://gist.github.com/clintar/ea98a971f5e93f3d7369a67895711e01
Log with Proton Experimental:
steam-611500.tar.gz
Log with 7.0-3
steam-611500_1.tar.gz

[Sid127]

Great... once that goes in i won't be able to play at all

That patch from wine staging is not likely to make it into Valve's Proton

[Cloudperry]

Quake Champions has started having some really nasty periodic stutter that wasn't there before. On my system the frame times spike up to about 40 ms every 3 seconds every single time. I remember it working perfectly with Proton GE 7-45 and other Proton releases where Dxvk gpl was freshly added.

I just tested many Proton versions with and without Esync/Fsync and it is happening on every version tested (Proton 7.0-6, Proton GE 7-46, Proton experimental bleeding edge and Proton GE 8-3). So I'm pretty sure that the stutter bug was introduced by a game update, because the game used to work perfectly on the Proton versions mentioned. It would be pretty hard to test different versions of the game since its online only. From what I can remember the stutter bug was introduced in an update that removed Nvidia Reflex or after that. There are no patch notes for updates after last year, but Steamdb shows that the last update was 3 months ago. So that could be the faulty update.

Edit: It seems that recently many people are having stuttering even on Windows, but I haven't seen anyone describing this periodic stutter when playing the game on Windows.

Edit 2: Just tested Quake Champions PTS (test version) and it isn't fixed there.

Edit 3: Adding the most relevant system information here.
OS: Arch Linux
CPU: Ryzen 5700X
GPU: AMD RX 6950XT with mesa-git 23.2.0_devel.171810.92a7cba4f26-1 from Cachyos repos
DE: KDE Wayland 5.27.5
Launch options: gamemoderun %command% and MANGOHUD=1 gamemoderun %command% while testing

[Sid127]

Replying to #225 (comment)

Discussed with them on the Quake discord as well, turns out to be the infamous wine high polling rate bug https://bugs.winehq.org/show_bug.cgi?id=46976

[clintar]

If it's the wile polling rate bug, why didn't it happen before? I stopped playing Quake champions 3 months earlier and tried it again last week and noticed this happening. It's just like my previous messages about Proton Experimental having the stutters when 7.0-3 didn't have any, and andreymal had the same issue. I sent logs for the different versions, but I don't know if it would show anything in those.

[Cloudperry]

Yeah, for me its clearly not the polling rate bug. I don't even have it in any other Windows games and I play a lot of them. If it was the polling rate bug it would happen only on mouse movement right? For me it happens whether I move the mouse or not. And it happens almost exactly every 3 seconds. I'm adding some system information to my earlier comment.

[mefff]

I had a similar issue, and was because it was set to raw input on the mouse settings. I'm not sure what the wine polling rate issue is, but I think that that mouse setting it's turn on on the defaults, so if you reinstalled the game maybe that setting did reset.

Just for confirmation, I'm now using the direct input setting with 1600 dpi on proton experimental, nothing on the launch settings, without any issue.

[Cloudperry]

Nope its not a DirectX input vs raw input issue either. Here are screenshots showing the stutters happening on DirectX input:

[Cloudperry]

Ohh wow I missed something that should have been very obvious. Recently I started installing some games on a Sshfs mount. For most games it works well, because I have very fast drives in the nas PC. Also I have a direct network connection with 2.5 GB/s ethernet between my main PC and the nas.

The stutter was completely fixed by installing the game locally. So either Quake Champions constantly does some really dumb blocking IO or there is some problem caused by Sshfs. Maybe I should check if NFS handles things like this any better, or just stop installing games on a nas.

[mefff]

I'm missing the cursor, I mean, the cursor is there and I can still navigate the menus but I don't see it.

I happens since some months ago I believe, one or two, no sure exactly when, I assumed it was some kind of thing with my window manager bspwm, it lately been doing weird things with steam too. But it turns out it also happens in swaywm.

When I consistently make it happen is when there is a loading screen, for example when you finish a match, and focus another workspace (so the game window looses focus). When I come back the cursor is gone. It also happens if it looses focus while starting, which is a pain in the ass since it takes ages on my crappy ssd.

I hope this long ass log can be useful: https://gist.github.com/mefff/e003c17cd736bd205392944cb5d89635

I just opened the game and immediately changed workspace, so indeed when the game finished loading my cursor is gone.

My system:

• arch linux - kernel 6.4.10-zen2-1-zen
• proton experimental
• swaywm

[Sid127]

A few users have been reporting crashes on the Quake discord, and we've identified that it's because of direct input. If you use raw input in the in-game settings they stop

[HolimaX]

For me, the darn game is not even launching. It keeps at status Running, but nothing is displayed on the screen. Using Fedora 38.

Graphics:
Device-1: Intel DG2 [Arc A770] driver: i915 v: kernel arch: Gen-12.7 pcie:
speed: 2.5 GT/s lanes: 1 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1,
DP-2, DP-3, DP-4, HDMI-A-3 bus-ID: 03:00.0 chip-ID: 8086:56a0
class-ID: 0300
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.9
compositor: gnome-shell v: 44.8 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: BenQ G2420HDBL serial: RAB03454SL000
res: 1920x1080 dpi: 92 size: 477x268mm (18.78x10.55") diag: 604mm (23.8")
modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-2 model: Philips FTV serial: 16843009 res: 1920x1080
dpi: 76 size: 640x360mm (25.2x14.17") diag: 734mm (28.9") modes:
max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris wayland: drv: iris x11:
drv: iris inactive: gbm
API: OpenGL v: 4.6 vendor: intel mesa v: 23.1.9 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel Arc A770 Graphics (DG2)
device-ID: 8086:56a0 display-ID: :0.0
API: Vulkan v: 1.3.243 layers: 1 surfaces: xcb,xlib,wayland device: 0
type: discrete-gpu driver: mesa intel device-ID: 8086:56a0 device: 1
type: cpu driver: mesa llvmpipe device-ID: 10005:0000

[clintar]

Looks like proton experimental crashes this at least for me on RX 6750 XT. Have to select 9.0-1 to get it to work again.

[kisak-valve]

Hello @clintar, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.