Hello @sulaiman1073, I'm not seeing an issue in the log, but as a blind guess, you could try adding PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% to the game's launch options.
Tried that, couldn't notice any changes.
Quake Live (282440)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3413.
@wfstuff posted on 2020-01-05T21:02:36:
Play button in the Steam client is sufficient.@sulaiman1073, based on the whitelist request, can you check if the game runs better with Proton 4.2 on your system?
Tried it on 4.2 earlier, same issues there. Couldn't tell if it was any better or worse. You don't get the missing textures bug all the time, depends on your luck. What I do is load a map, then quit it if I get the bug, then load the same map or another map again, quit it if I get the bug again, ...etc. After doing this 20 times, the 21th map might be fine. Sometimes you'd get lucky and the first map will be fine. Sometimes you'd get lucky and will only have to load/quit twice or thrice.
I never got this bug when playing with proton. However, I got a similar bug (missing textures, but not rocket smoke) in Quake 3 a long time ago in Windows. If I remember correctly it had something to do with bad .pk3 files. Perhaps you could try a fresh install and remove all custom mods/maps/models etc.
The game window doesn't show up on Debian Testing, NVIDIA driver 440.44, proton 5.0-1 and 4.11-12 Running apt upgrade and rebooting resolved the issue.
Quake Live (282440) mouse lags and inverse-accel (negative accel) 5.0+
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3685.
@username2222232 posted on 2020-03-25T04:14:05:
Same issue described as in the following ticket https://github.com/ValveSoftware/Proton/issues/3529#issuecomment-587539290 for Doom 2016 but for Quake Live.
Mouse sensitivity is registering different than on the Proton 4.0 branch.
[Edit: The default sensitivity and the feeling of it is overall 2x slower than the 4.0 branch and how the sensitivity should be. In addition to the inverse accel which I will mention below, the actual sens. is a lot slower in the game (2x).]
If you move the mouse quickly even with all acceleration parameters off and using raw input it will go a shorter distance than if you slowly move the mouse the same distance. Moving the mouse on the mat slowly results in a similar sensitivity like on the 4.0 branch and also makes it go twice as far in the game (in terms of 360's).
It's like some kind of reverse (negative accel) effect is going on in the game. Slow movements make the mouse travel further in the game and super fast one's are abrupt and short (for same distance).
I know this is a Proton bug b/c if I revert to the 4.0 branch the Quake Live sensitivity is not impacted by speed of my mouse movement as well it also matches a different game (which uses the same code = Quake III Arena, which I am playing natively on Linux outside of Steam).
Use either Ubuntu 19.10 or the Daily branch of 20.04. Move the mouse slowly in Proton 5.0 for a set distance. Then move the mouse very fast over this same distance. Even with all OS acceleration turned off and the mouse will be two very different 360 degree turns in the game. Fast will give you ~ 2.5x less of a 360. Slowly moving the mouse will give you 2.5x more 360. Distance should be ==
When trying to load a map retrieved form a Steam Workshop subscription, Game crash with the following error
ERROR: FS_FileForHandle: can't get FILE on zip file
Full Quake Live console log: quakelivelog.txt
In this case i tried to load the map 6plus. You can see in the console log that the game actually load the map files
Z:\mnt\datamix\SteamLibrary\steamapps\workshop\content\282440\547252823\\6plus.pk3 (0x3d3f1bca - 14 files)
Z:\mnt\datamix\SteamLibrary\steamapps\workshop\content\282440\547252823/
Quake Live is based on Quake 3 Arena (1999) which the source code has been published by Id Software. If that can be of any use, you can find the code who throw that error here
https://github.com/id-Software/Quake-III-Arena/blob/dbe4ddb10315479fc00086f08e25d968b4b43c49/code/qcommon/files.c#L404
Quake 3 Filesystem is also explained at the top of this file.
Everything run fine on Microsoft Windows.
Game runs perfectly fine except sometimes crashing in the server browser. The game never crashes during gameplay. Framerate is on par with Windows, there's no perceptible input or rendering delay.
Only complaint I've got that Alt-Tab doesn't work. The game takes over the entire desktop and switching to any other program while it's on is impossible. It's quite annoying when I want to change the music I'm listening to. I'm running KDE Plasma 5.19.5, on freshly upgraded Debian Testing (the issue has been there for far longer than the update).
I get a "Bad Server Address" error whenever i try to join trough server browser. Happens since I switched from Proton 6.3 to Proton 7.0.
steam-282440.log
Hello @kuba8588, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please clarify what is the newest version of Proton you know is not affected.
I have the same problem using Proton 7.0, and the frame rate has also dropped considerably (in single player). Works perfectly forcing Proton 6.3-8.
steam-282440.log
@francesconicoletta @kuba8588 Thank you for reporting the regression!
@francesconicoletta Could you give some instructions about how to get into single player mode where you are seeing the bad fps, and give some approximate good vs bad fps numbers? I only see a multi-player match gameplay option.
Same stuff happens to me as to @kuba8588 : I get a "Bad Server Address" error whenever i try to join trough server browser. Happens since I switched from Proton 6.3 to Proton 7.0.
@smiklosovic This should already be fixed in experimental, which you can force on a per-game basis. It should also be fixed with the next stable proton release if you want to wait for that :)
@francesconicoletta @kuba8588 Thank you for reporting the regression!
@francesconicoletta Could you give some instructions about how to get into single player mode where you are seeing the bad fps, and give some approximate good vs bad fps numbers? I only see a multi-player match gameplay option.
You could try putting map q3dm6 in the console to load Campgrounds on a private server, or open the Start Match menu and set it to singleplayer from the server settings there.
hello, just like to add that mouse raw input does not work
Quake Live in Linux with Proton has been crashing in 'Match Browser'
on all my different Linux boxes for the last few years. Nothing new about it, I'm used to it :-)
Loading servers in 'Match Browser' is approx 10 times slower in Linux with Proton when compared to Windows 10/11.
Unhandled exception: page fault on execute access to 0x00000000 in 32-bit code (0x00000000).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:00000000 ESP:019cfc3c EBP:019cfc68 EFLAGS:00210246( R- -- I Z- -P- )
EAX:000005cf EBX:00000000 ECX:00000001 EDX:00000000
ESI:7e757d00 EDI:00000000
Stack dump:
0x019cfc3c: 7e6f331f 7e0be5a0 08a000a3 00000000
0x019cfc4c: 7e6fb133 00000000 00050068 e72fa000
0x019cfc5c: 00000000 7e75aca0 01b56e30 019cfc88
0x019cfc6c: 7e6fb140 00050068 f3dfdf78 019cfcb8
0x019cfc7c: 00000000 7e757d00 00001449 019cfcb8
0x019cfc8c: 7a89fd24 00000000 00000003 00000000
Backtrace:
=>0 0x00000000 (0x019cfc68)
1 0x7e6fb140 (0x019cfc88)
2 0x7a89fd24 (0x019cfcb8)
3 0x0046b870 in quakelive_steam (+0x6b870) (0x019cfcd8)
4 0x00437b15 in quakelive_steam (+0x37b15) (0x019cfcec)
5 0x0043c525 in quakelive_steam (+0x3c525) (0x019cfcfc)
6 0x0043cb51 in quakelive_steam (+0x3cb51) (0x019cfd08)
7 0x004be44a in quakelive_steam (+0xbe44a) (0x019cfd24)
8 0x004cc9b3 in quakelive_steam (+0xcc9b3) (0x019cfd50)
9 0x004eda67 in quakelive_steam (+0xeda67) (0x019cfe9c)
10 0x005263d4 ??0_Mutex@std@@QAE@W4_Uninitialized@1@@Z+0x4f1() in quakelive_steam (0x019cff30)
11 0x7b62ddb0 ActivateActCtx+0x23420() in kernel32 (0x019cff48)
12 0x7bc5d3a7 A_SHAFinal+0x3cd87() in ntdll (0x019cff5c)
13 0x7bc5db50 A_SHAFinal+0x3d530() in ntdll (0x019cffec)
0x00000000: -- no code accessible --
Modules:
Module Address Debug info Name (61 modules)
PE 00140000-0014d000 Deferred userenv
PE 00150000-00196000 Deferred oleacc
PE 00400000-017c7000 Export quakelive_steam
PE 01f40000-02073000 Deferred ole32
PE 02080000-029b9000 Deferred shell32
PE 07a70000-07bad000 Deferred steam
PE 07bd0000-07bfe000 Deferred winepulse
PE 0c400000-0cb73000 Deferred uix86
PE 10000000-116a5000 Deferred awesomium
PE 38000000-3922e000 Deferred steamclient
PE 3b400000-3b431000 Deferred steam_api
PE 4ad00000-4b67f000 Deferred icudt
PE 61500000-6152f000 Deferred iphlpapi
PE 61740000-61784000 Deferred advapi32
PE 61940000-619cd000 Deferred wininet
PE 62fc0000-6304e000 Deferred rpcrt4
PE 631c0000-631e2000 Deferred secur32
PE 63480000-6348d000 Deferred version
PE 637c0000-63869000 Deferred urlmon
PE 63bc0000-63bda000 Deferred shcore
PE 64a40000-64a94000 Deferred shlwapi
PE 64ec0000-64fee000 Deferred oleaut32
PE 65f40000-65f4d000 Deferred kerberos
PE 66240000-66258000 Deferred bcrypt
PE 666c0000-666cf000 Deferred hid
PE 66b00000-66b3e000 Deferred win32u
PE 67840000-6784a000 Deferred psapi
PE 67d40000-67d6c000 Deferred mmdevapi
PE 68080000-680a0000 Deferred jsproxy
PE 682c0000-6831e000 Deferred dsound
PE 68500000-6855a000 Deferred combase
PE 68700000-68730000 Deferred uxtheme
PE 69540000-6958f000 Deferred dinput8
PE 69600000-69649000 Deferred winhttp
PE 6a040000-6a062000 Deferred msacm32
PE 6a280000-6a32e000 Deferred msvcrt
PE 6a400000-6a4c8000 Deferred winmm
PE 6aa40000-6aa48000 Deferred usp10
PE 6b880000-6b892000 Deferred xinput9_1_0
PE 6b9c0000-6b9cb000 Deferred dhcpcsvc
PE 6bc00000-6bc2c000 Deferred sechost
PE 6bcc0000-6bd41000 Deferred setupapi
PE 6c9c0000-6ca45000 Deferred gdi32
PE 6cc40000-6cd9f000 Deferred comctl32
PE 6d780000-6d7a9000 Deferred ws2_32
PE 6e4c0000-6e4d6000 Deferred dnsapi
PE 6e8c0000-6e994000 Deferred crypt32
PE 6ed00000-6ef41000 Deferred user32
PE 6f480000-6f48c000 Deferred nsi
PE 70940000-70960000 Deferred mpr
PE 70b40000-70c1c000 Deferred ucrtbase
PE 70e80000-70e8a000 Deferred msimg32
PE 71200000-7121c000 Deferred imm32
PE 78050000-780b9000 Deferred msvcp100
PE 78aa0000-78b5f000 Deferred msvcr100
PE 7a840000-7a844000 Deferred opengl32
PE 7b000000-7b0eb000 Deferred kernelbase
PE 7b600000-7b81a000 Export kernel32
PE 7bc00000-7bca8000 Export ntdll
PE 7e6c0000-7e6c4000 Deferred winex11
PE f7570000-f7573000 Deferred lsteamclient
Threads:
process tid prio (all id:s are in hex)
00000020 steam.exe
00000024 0
000000c4 0
0000013c 0
00000030 services.exe
00000034 0
00000038 0
00000044 0
00000064 0
00000070 0
00000094 0
000000ac 0
000000f8 0
0000003c winedevice.exe
00000040 0
0000004c 0
00000050 0
00000054 0
00000058 0
000000b8 0
0000005c winedevice.exe
00000060 0
00000068 0
0000006c 0
00000074 0
00000078 0
0000007c 0
00000080 0
00000088 0
0000008c plugplay.exe
00000090 0
00000098 0
0000009c 0
000000a0 0
000000a4 svchost.exe
000000a8 0
000000b0 0
000000b4 0
000000bc conhost.exe
000000c0 0
000000c8 explorer.exe
000000cc 0
000000d8 0
000000dc 0
000000e4 rpcss.exe
000000e8 0
00000100 0
00000104 0
00000108 0
0000010c 0
00000110 0
00000118 tabtip.exe
0000011c 0
0000012c 0
00000130 0
00000134 (D) Z:\media\data\SteamLibrary\steamapps\common\Quake Live\quakelive_steam.exe
00000138 0 <==
00000140 0
00000144 0
00000148 15
0000014c 15
00000150 15
00000154 0
00000158 0
0000015c 0
00000160 0
00000164 0
00000168 0
0000016c 0
00000170 0
00000174 0
00000178 0
0000017c 0
000001a4 0
00000180 awesomium_process.exe
00000184 0
00000188 0
0000018c 0
00000190 0
00000194 0
00000198 0
System information:
Wine build: wine-7.0
Platform: i386 (WOW64)
Version: Windows 10
Host system: Linux
Host version: 5.19.11-desktop-2omv4050
I can't seem to click anything in the menus, or at least not easily. As I mouse-over things they highlight for a brief moment and then un-highlight, I have to wiggle my mouse back and forth across things and click rapidly to click on anything. I'll try to get a log when I get a moment.
Attempted experimental and various GE versions - on Nvidia (3070).
Edit; Nothing to do with Proton! Use the below in console (tilde) to fix, it's a gamepad thing.
\in_joystick 0
\in_restart
Games crashes midgame. Happened three times, always in on about 2hs sessions. Got the log on the third time
CPU Brand: AMD Ryzen 5 1600 Six-Core Processor
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.6.1-arch1-1
X Server Vendor: The X.Org Foundation
X Server Release: 12101009
X Window Manager: bspwm
Steam Runtime Version: steam-runtime_0.20231024.64411
Video Card:
Driver: AMD AMD Radeon RX 6700 XT (navi22, LLVM 16.0.6, DRM 3.54, 6.6.1-arch1-1)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.2.1-arch1.2
OpenGL Version: 4.6
Proton 6.4-GE-1. Tried several, but had the problem that couldn't press anything in the menu. Apparently that had to do with configuring the game's input.
https://gist.github.com/mefff/3f0cd44f2440b15e27c5f4c22f2474aa
In the meantime I'll try a newer an official proton with the fix of the input. It's weird because I played this a lot about a year ago, don't remember on which proton, probably experimental of that time and never had any issue. Now this I also notice less stability on the fps.
The game generally works and I don't get crashes or anything now, but regardless of proton version I drop down to 60-80fps if there's ~10 players in the game regardless of video settings, which is really bad performance for such an old game and I can't find any solution to this. I'm running on a 5900x, 32GB ram and a RTX 3070. Anyone have any suggestions?
Not sure how I fixed my crashes, but it didn't happen anymore.
About the fps, I had the same issue and today found that with com_idlesleep 0 ingame fixes it. Didn't test it a lot, and in fact while trying in an offline server got spikes, but then in online serves with ~15 people had no issues and fps locked at 250
It seems like it is a thing with windows users too, not only wine
About the fps, I had the same issue and today found that with
com_idlesleep 0ingame fixes it. Didn't test it a lot, and in fact while trying in an offline server got spikes, but then in online serves with ~15 people had no issues and fps locked at 250It seems like it is a thing with windows users too, not only wine
Yeah others recommended this but doesn't seem to fix the issue for me. In games with ~4-5 players total I get 200-250fps, when there's ~8-10 players or more it'll drop down to 60-80 depending on how many are on screen, making it pretty unplayable. Seems to be specific to playing it via proton as on Windows this doesn't happen.
Quake Live performance issues
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8698.
@topochico6969 posted on 2025-05-14T22:42:25:
Name of the game with compatibility issues: Quake Live
Steam AppID of the game: 282440
System Information
GPU: NVIDIA GeForce RTX 4060 Ti
Video driver version: NVIDIA 570.133.07
Kernel version: 6.8.0-59-generic
Link to full system information report as [Gist](https://gist.github.com/topochico6969/61d2842969680ee8c208087747156db3)
Proton version: GE-Proton8-30
I confirm:
that I haven't found an existing compatibility report for this game.
that I have checked whether there are updates for my system available.
Symptoms
Game experiences unstable frame timing and inconsistent FPS when using the regular Cinnamon session on Linux Mint.
FPS becomes more stable at 250 only when using Cinnamon (Software Rendering) session — likely due to compositor interference.
Still very noticeable frame timing issues and stutters.
When post-processing is disabled, the game displays a white screen instead of rendering properly.
Enabling post-processing avoids the white screen, but causes visual glitches such as flickering or artifacts.
These issues do not occur on Windows and are specific to running the game through Proton on Linux Mint.
Reproduction Steps
On Linux Mint (Cinnamon), install and run Quake Live using GE-Proton8-30.
Set com_maxfps 250 — observe unstable frame timing.
Log out and log into Cinnamon (Software Rendering) mode.
Relaunch the game — FPS is now stable.
Go to video settings → disable post-processing → screen goes completely white.
Re-enable post-processing → screen returns, but graphical glitches persist.
Proton Log:
steam-282440.log
ge-proton8-30x1 2025-05proton 6.4x1 2023-11proton 7.0x4 2022-10proton 6.3x2 2022-03proton 6.3-8x1 2022-02proton 4.0x1 2020-03proton 5.0x1 2020-03proton 5.0-1x1 2020-02proton 4.2x1 2020-01PROTON_LOG=1x1 2022-02PROTON_FORCE_LARGE_ADDRESS_AWARE=1x1 2020-01
Compatibility Report
System Information
I confirm:
steam-282440.log
Symptoms
The problem: https://i.imgur.com/9HVIdkL.jpg
The black and white texture on these pillars is also the texture of the rocket trail and smoke. The screen also flashes with this texture when you take damage.