XCOM: Chimera Squad (882100)

[Taijian]

Compatibility Report

• Name of the game with compatibility issues: XCOM: Chimera Squad
• Steam AppID of the game: 882100

System Information

• GPU: RX 470
• Driver/LLVM version: Mesa 20.0.5
• Kernel version: 5.6.7
• Link to full system information: https://gist.github.com/Taijian/93a1d772901ac4551c16cd72d75bb26f
• Proton version: 5.0-6 and 4.11-13

I confirm:

• [X] that I haven't found an existing compatibility report for this game.
• [X] that I have checked whether there are updates for my system available.

Symptoms

The game starts fine. Then, by default the launch screen will open as a 'borderless window'. In this mode, the mouse cursor is not rendered and non functional. The options menu can be selected with the keyboard and the presentation changed to 'fullscreen'. In 'fullscreen' the mouse cursor does render, but is non-functional, i.e. button presses do not register. This makes the game borderline unusable. Launching the game in an X-session does not suffer from this issue.

steam-882100.log

Reproduction

Start the game in a wayland session.

[NikolayKuzmin]

I confirm the mouse issue. It is possible to start a game using gamepad. Mouse actually works, but clicks registered with huge offset.

[f-abel]

Distro:Ubuntu 18.04.5 LTS (64 bits) Kernel:4.15.0-115-generic RAM:24 GB GPU Driver:NVIDIA 450.66 GPU:NVIDIA GeForce GTX 1070 CPU:Intel Core i7-8700K @ 3.70GH

no wayland and can't click on the launch screen, however legacy and 25th anniversary lanchers clicks ok. Any can help is welcome

[starvsion]

Distro: Fedora 33 Kernel:5.8.14-300.fc33.x86_64 RAM:32GB GPU Driver:AMD R9 390 (Driver: amdgpu) CPU:AMD Ryzen 9 3900X @ 3.70Ghz Proton version: 5.0-9

I can confirm the same problem with mouse cursor, tried with GDK_BACKEND=x11, still no luck. But works with a controller. Also, tried old fix from XCOM 2 with bind mouse to Window, still don't work....

[hajnal-endot]

Distro: Arch stable Kernel: 5.9.13-zen1-1-zen GPU and Driver: AMD R9 390 on amdgpu (default mesa stuff, vulkan-radeon) CPU: Ryzen 7 1700, stock Proton version: 5.13-4

This game is playable on the existing Proton 4.11-13 stuff, but it has CTDs. I'm interested to see if you can find what the feature regression is. I'll attach logs for what happens in 5.13-4 and the experimental branch, then finally whatever happens to cause the CTD in 4.11-13 (that will be a very long log, it takes a fair while, but i will do it in order to help the noble cause of xcom)

5.13-4: https://gist.github.com/hajnal-endot/1210ba47b53dcd25b34dd1cefd5e66ea Result: Launcher doesn't render properly, I get a tiny Chimera Squad button in the Wine system tray (???) for some inexplicable reason (why is that tray even there), game cannot be launched

Experimental: https://gist.github.com/hajnal-endot/9dde1f6316f0008327983a39855b6b64 Result: Instant CTD, launcher doesn't even appear

4.11-13: could not replicate issue, log not included Result: plays fine and quite smooth for a good while, will randomly CTD

[kisak-valve]

Hello @hajnal-endot, looking at the 5.13-4 log, gstreamer seems to be having a hard time. Possibly some video(s) are trying to play which were completely skipped before.

[hajnal-endot]

Hello @hajnal-endot, looking at the 5.13-4 log, gstreamer seems to be having a hard time. Possibly some video(s) are trying to play which were completely skipped before.

Any idea what approach I should take with it? Also, to clarify, I don't remember it using videos in the launcher, but then you could be right in that they're trying to play now and it isn't going too well.

[soerengrunewald]

Distro: Fedora 33 Kernel: 5.10.7-200.fc33.x86_64 GPU and Driver: Vega56 amdgpu/radv (mesa: 20.3.3) CPU: Ryzen 5 1600X, stock Proton version: 5.13-5 / experimental

The game starts, a splash-screen appears and then a black windows as launcher https://user-images.githubusercontent.com/2650470/104737512-a0142700-5744-11eb-8b0b-2c6f09d5cc83.mp4

steam-882100.log

Following an advice on ProtonDB, I tried Proton 5.0.10. And there it works, except that the mouse clicks are not recognized ingame. The launcher works.

[soerengrunewald]

Updated to Fedora 34 with newer Xwayland, solves the issue for me.

[afettouhi]

Just tried XCOM: Chimera Squad with the new Proton 6.3-1 release and the launcher crashes right from the start. The game works fine with Proton 5.0-10. So I don't understand why the relase notes say that XCOM: Chimera Squad works now?

[kisak-valve]

Hello @afettouhi, 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 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.

[afettouhi]

https://gist.github.com/afettouhi/21af3a5b9ec193f10c93f50b8dd6a58e

[sysms]

After the latest update from today, the game itself won't launch anymore (tried Proton 5.0-10 and Proton 6.3-1).

It tries to update some 2K Launcher, but then fails with

wine: Call from 000000007BC2F498 to unimplemented function KERNEL32.dll.GetMaximumProcessorGroupCount, aborting

Here is a log from Proton 6.3-1:

steam-882100.log

My sysinfo: https://gist.github.com/sysms/eea674251f5dc62490fc394a1c88b580

[afettouhi]

Can confirm that the game doesn't launch anymore other than trying to update the 2K launcher.

[screwylightbulb]

Also having the same issue. The same launcher has been added to Mafia: Definitive Edition which also fails.

Credit to a protondb user for this simple way to bypass the launcher in XCOM: Chimera Squad using this in Launch Options:

bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/Binaries\/Win64\/xcom.exe}"' -- %command%

[afettouhi]

Can confirm that the bash workaround works fine with XCOM: Chimera Squad even on Proton 6.3 for me. So I can now run the game with the latest Proton.

[FearlessQuality]

It appears workaround is no longer needed when using experimental and 6.3-4 RC

[ipr]

With current Proton Experimental game works, mouse input works and so on. Mesa 21.3.5, kernel 5.16.4, gnome-shell 41.2. This is without mentioned bash workaround. The launcher has updated itself so that is one possible reason?

Edit: people with issues in the past could re-test and check if there are still affected?

[zerkerX]

When I first installed the game, it took a fair bit of fiddling between Proton versions and even restarting my Linux session to eventually get the 2K launcher to appear at all. I managed to succesfully run and play for several sessions, but when I received an update to the game it seemingly broke the 2K launcher again and it silently refuses to run. It is very fragile.

At least the workaround solves it :shrug:

[pcfirebeats]

Hi,

When I launch XCOM:Chimera Squad it opens the 2K launcher, but when I try to go to mod manager it opens a new window, and it keeps just running the loading signal but nothing happens. Everything else seems normal.

Ubuntu 24.04, gfx AMD 6700, MESA drivers.