Hello @d3rhans, some possible lines of interest from your log: fixme:bthpropscpl:BluetoothFindFirstRadio (000000000022F7E8 000000000022F7E0): stub! immediately followed by and access violation (c0000005) and wine: Unhandled page fault on read access to 0000000000000000 at address 0000000141F61AAE (thread 0118), starting debugger....
Hi, thanks for your prompt reply. I am following things in the Quake discord and as it seems their are at least some crashes on Windows 7 and 10 which may or may not be related to this. Those supposedly were fixed before I opened this issue - but seems like they aren't.
I'll see how this plays out and update this issue accordingly when new versions of PTS are released and when it goes live.
https://quake.bethesda.net/en/news/2WsLdFFKtoQRmjvrKUebWA
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000141f582fe).
Register dump:
rip:0000000141f582fe rsp:000000000022e630 rbp:000000000022e740 eflags:00010246 ( R- -- I Z- -P- )
rax:000000000000008b rbx:ffffffffffffffff rcx:000000000022ef78 rdx:0000000000000101
rsi:000000000022ef78 rdi:ffffffff80000002 r8:000000000022e6c0 r9:0000000000b6fe60 r10:0000000000000000
r11:000000000022e5a8 r12:0000000000000000 r13:0000000142d02b80 r14:0000000000cd0960 r15:0000000000000101
Stack dump:
0x000000000022e630: 0000000141f582c6 0000000141f70959
0x000000000022e640: ffffffffffffffff 000000000022ef78
0x000000000022e650: 0000020000000070 ffffffffffffff68
0x000000000022e660: 00000001423d8720 ba246beb10b7a200
0x000000000022e670: 000000007f0102b0 0000000000000001
0x000000000022e680: 0000000000cd09e0 0000000000000000
0x000000000022e690: 0000000000000001 0000000000000000
0x000000000022e6a0: 0000000000000000 00007fe7a8659cf8
0x000000000022e6b0: 00000000007c007c 000000000022e6f0
0x000000000022e6c0: 00007fe700000030 0000000000000000
0x000000000022e6d0: 000000000022e6b0 0000000000000040
0x000000000022e6e0: 0000000000000000 0000000000000000
Backtrace:
=>0 0x0000000141f582fe EntryPoint+0xfffa7e82() in quakechampions (0x000000000022e740)
1 0x0000000141f582c6 EntryPoint+0xfffa7e49() in quakechampions (0x000000000022e740)
2 0x0000000141f70959 EntryPoint+0xfffc04dc() in quakechampions (0x000000000022e740)
3 0x0000000141f23377 EntryPoint+0xfff72efa() in quakechampions (0x000000000022f030)
4 0x0000000141f230e9 EntryPoint+0xfff72c6c() in quakechampions (0x000000000022f910)
5 0x0000000141f1836f EntryPoint+0xfff67ef2() in quakechampions (0x0000000000000000)
6 0x0000000141f1610d EntryPoint+0xfff65c90() in quakechampions (0x0000000000000000)
7 0x0000000140160f74 EntryPoint+0xfe1b0af7() in quakechampions (0x00000003af6ee560)
8 0x00000003af68de3a EntryPoint+0x2fffa1f69() in ucrtbase (0x00000003af6ee560)
9 0x0000000141fb035d EntryPoint+0xfffffee0() in quakechampions (0x0000000000000000)
10 0x000000007b62c809 EntryPoint+0xffffffffffffffff() in kernel32 (0x0000000000000000)
11 0x000000007bc59803 EntryPoint+0xffffffffffffffff() in ntdll (0x0000000000000000)
0x0000000141f582fe EntryPoint+0xfffa7e82 in quakechampions: movq (%r10),%r10
Hello @Eonfge, your log looks similar to the opening post with fixme:bthpropscpl:BluetoothFindFirstRadio (000000000022F620 000000000022F618): stub! immediately followed by an access violation (c0000005).
:thinking: I did not play Quake Champions since April, so It might have broken since then, although there are reports of it working on ProtonDB as recent as three weeks.
The changes that caused the crash I initially reported for PTS went live this afternoon for the main game. The reason it isn't running with proton anymore are some built-in Anti-Cheat/Anti-Tamper measures that seem to be custom for this game.
@kisak-valve to my understanding the Bluetoth stuff can be ignored if I recall correctly, that message showed up in the logs previous to the update, not sure though. The access violation is where it fails though.
@Eonfge the reports on protondb were before today's update, so they are outdated. I'll post a new report there later.
I don't know what exactly they've implemented, but the game also refuses to run on Windows, if any program attempts to do anything with it's memory, tries to inject dlls or something like that (e.g. afterburner, rivatuner, programs that do macros for keyboards/gamepads etc.)
I am not sure if anything can be done about this from proton/wine side
@kisak-valve ok, makes sense. I'll get a new log and everything later this evening, update #225 accordingly and close this one, as PTS is just the test version of QC and down atm anyways.
On wayland (manjaro-sway), the game launches fine, but the buttons are not clickable, so there's no way to start a match.
EDIT: This seem to be an issue of sway itself when passing an screen position to the config file.
After removing the 'position' parameter of the output. Everything works well.
proton experimentalx1 2021-05PROTON_NO_ESYNCx1 2021-05PROTON_NO_FSYNCx1 2021-05PROTON_USE_WINED3Dx1 2021-05
Compatibility Report
System Information
I confirm:
steam-743650.log
Symptoms
Game crashes immediately, doesn't even show a black screen or anything else. Quake Champions PTS (Public Test Server) is the test/beta version of Quake Champions (Steam AppID: 611500) and will become the live version in ~4 weeks. Quake Champions works perfectly fine with any recent Proton version, so did previous versions of PTS.
I tried with different Proton versions, NVIDIA driver versions, Kernels, display managers (Gnome and i3) and multiple variants of launch options (none, PROTON_NO_ESYNC, PROTON_NO_FSYNC, PROTON_USE_WINED3D and combinations). The result is always the same.
I asked two other players that (at least sometimes) play the game on Linux and they confirmed the issue.
Reproduction