protonscr

XCOM: Enemy Unknown

protonopen appid 200510Game compatibility - Unofficial
ValveSoftware/Proton#4061 · opened 2020-07-12 by John-Gee · updated 2025-04-25 · 20 comments · github · game page · search this game
1 matching comments, n / p to jump
JJohn-Gee 2020-07-12 github

Compatibility Report

  • Name of the game with compatibility issues: XCOM Enemy Within (or Within I guess)
  • Steam AppID of the game: 200510

System Information

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 does not launch.
I see nothing interesting in the log, but when I run the game in Steam in Wine, before anything I had to accept the EULA which did not happen with Proton, maybe there's something there.

I've tried the last 3 versions, but I saw no difference.
Other games run with Proton so it's not Proton not running on my system.

Reproduction

Install and run the game with Proton.

Thanks!

JJohn-Gee 2020-07-12 github
Kkisak-valve maintainer 2020-07-12 github

Hello @John-Gee, looks like the Windows variant of this game uses CEG (#753).

JJohn-Gee 2020-07-12 github

Oh that would explain it I guess.

Hopefully Steam's Proton will be able to support it like standard Wine.

Thank you for the quick reply!

Ggardotd426 2020-08-27 github

Hopefully Steam's Proton will be able to support it like standard Wine.

That's not the issue.

The issue is the Steam Windows client vs Steam Linux client.

The Steam Windows client has CEG support. The Linux one doesn't.

There's nothing that can be done in Proton to make this work. There's no missing functionality in Proton. If you wanted to use Proton to run Windows Steam outside of the Native Steam Client, it would work the same way as Wine.

The issue is with the Steam clients themselves, not Wine vs. Proton.

Ffriedc 2021-12-06 github

So far XCOM: Enemy Unknown works great for me with the Steam Beta Client and Proton Experimental.

There is one small glitch that I noticed. After starting a new campaign and completing a tutorial mission, I was asked to choose the starting continent. After navigating to continents that I hadn't unlocked, the game wouldn't let me change the selection. I had to use steam to force close it. I started the game again and reloaded my last save. This time I chose a valid starting continent and after that everything went fine. No further glitches yet.

System Information

Ffriedc 2022-04-06 github

It seems that 7.0 and 7.0-2 RC do not recognize input from my Xbox 360 controller while Proton Experimental does.

Ppcfirebeats 2022-08-02 github

Using Proton Experimental, today's versions, the game runs with much better performance than the native (and outdated) version, but is instable and crashes many times, being unplayable.

Usually crashes on loading a game or at the start, sometimes I needed to hard reboot the PC because it becomes totally unresponsive.

System information
    Fabricante: ASUSTeK COMPUTER INC.
    Modelo: P8B75-M LX
    Tipo: Computador de secretária
    Sem input táctil

Informação do processador:
    Fornecedor da CPU:  GenuineIntel
    Marca da CPU:          Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
    Família da CPU:  0x6
    Modelo da CPU:  0x3a
    Versão da CPU:  0x9
    Tipo da CPU:  0x0
    Velocidade: 3600 Mhz
    4 processadores lógicos
    4 processadores físicos
    HyperThreading:  Não suportado
    FCMOV:  Suportado
    SSE2:  Suportado
    SSE3:  Suportado
    SSSE3:  Suportado
    SSE4a:  Não suportado
    SSE41:  Suportado
    SSE42:  Suportado
    AES: Suportado
    AVX: Suportado
    AVX2: Não suportado
    AVX512F: Não suportado
    AVX512PF: Não suportado
    AVX512ER: Não suportado
    AVX512CD: Não suportado
    AVX512VNNI: Não suportado
    SHA: Não suportado
    CMPXCHG16B: Suportado
    LAHF/SAHF: Suportado
    PrefetchW: Não suportado

Versão do Sistema Operativo:
    Pop!_OS 22.04 LTS (64 bits)
    Nome do Kernel: Linux
    Versão do Kernel: 5.18.10-76051810-generic
    Fornecedor de X Server:  The X.Org Foundation
    Versão de X Server: 12101003
    Gestor de X Window:  GNOME Shell
    Versão Runtime do Steam: steam-runtime_0.20220601.1

Placa gráfica:
    Driver: AMD AMD Radeon RX 470 Graphics (polaris10, LLVM 13.0.1, DRM 3.46, 5.18.10-76051810-generic)
    Versão do driver: 4.6 (Compatibility Profile) Mesa 22.0.5
    Versão do OpenGL: 4.6
    Profundidade de cor do ambiente de trabalho: 24 bits/pixel
    Taxa de Atualização do Monitor: 164 Hz
    ID do fornecedor: 0x1002
    Código do dispositivo: 0x67df
    Revisão não detetada
    Número de monitores:  1
    Número de placas gráficas lógicas: 1
    Resolução do monitor principal: 2560 x 1440
    Resolução do ambiente de trabalho: 2560 x 1440
    Tamanho do monitor principal: 27.44" x 15.43" (31.46" diag)
 69.7cm x 39.2cm (79.9cm diag)
    VRAM principal: 4096 MB

Placa de som:
    Dispositivo de áudio: VIA VT1708S

Memória:
    RAM: 7885 MB

Hardware de R.V.:
    Headset de R.V.: Nenhum encontrado

Diversos:
    Idioma da interface:  Português (Portugal)
    Idioma: pt_PT.UTF-8
    Espaço total disponível no disco: 441021 MB
    Maior bloco livre no disco: 28098 MB

Espaço no disco:
    Número de SSDs: 0
    Número de HDDs: 0

The runtime information tool is preparing a report, please wait...
Kkisak-valve maintainer 2023-07-15 github

XCOM: Enemy Unknown Linux native client not launching and crashes

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/9858.
@chknatwork posted on 2023-07-15T13:18:57:

Your system information

  • Steam client version (build number or date): 1689034492
  • Distribution (e.g. Ubuntu): Manjaro 23.0.0 UltimaThule
  • Opted into Steam client beta?: [Yes/No] No
  • Have you checked for system updates?: [Yes/No] Yes
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
  • GPU: Nvidia 1650 MaxQ

Please describe your issue in as much detail as possible:

XCOM: Enemy Unknown not launching - showing 00c8:err:xrandr:xrandr14_get_adapters Failed to get adapters amongst other errors in terminal

Steps for reproducing this issue:

  1. Click Play to launch XCOM:EU
  2. Doesn't launch and goes back to steam client

*i=other native games seem to work like Neverwinter Nights by Beamdog and Divinity Original Sin Enhanced Edition using Proton
steam-logs.tar.gz

Mmartinsuchan 2024-01-18 github

Just tested this game on my Steam Deck OLED with latest updates and it's not launching, stuck on the Steam Deck loading screen and then crashes.

BBearsPunch 2024-03-18 github

steam-200510.log
First start was ok. Now, each start - lag if I move mouse, and crash if load battle situation.

Ssimifor 2024-03-18 github

@BearsPunch Just to make sure, the game crashes whenever you load a map? Something like the attached screenshot or something more specific?
XCOM: Enemy Unknown 2024_03_18:15:41:50

BBearsPunch 2024-03-18 github

@BearsPunch Just to make sure, the game crashes whenever you load a map? Something like the attached screenshot or something more specific? XCOM: Enemy Unknown 2024_03_18:15:41:50

just when load the map. Correct. But as I said, the main issue started just after second launch and fps drops to 5-10 if I just move mouse. Remove shader cache, reinstall game didn't help.

Ssimifor 2024-03-18 github

@BearsPunch Yeah, I launched the game a few times and didn't encounter the fps drop or the crash. Have you checked if rebooting makes a difference for you?

BBearsPunch 2024-03-19 github

@BearsPunch Yeah, I launched the game a few times and didn't encounter the fps drop or the crash. Have you checked if rebooting makes a difference for you?

Of course I did 🙂 do you have nvidia or amd gpu?

Ssimifor 2024-03-19 github

@BearsPunch amd gpu, but it's very odd that you'd have a persistent degradation past the first launch regardless of card. Did you update your system between launches?

BBearsPunch 2024-03-19 github

@BearsPunch amd gpu, but it's very odd that you'd have a persistent degradation past the first launch regardless of card. Did you update your system between launches?

no and only this game has issues.

TTheOverpassArsonist 2024-06-06 github

For me it does launch, but more recent versions of proton suffer from crashing bugs when loading saves. It's not consistent, but on the latest version of proton I repeatedly got into complete dead locks where ALL of my saves just would not load, and I had to pull back an old save from a btrfs snapshot. It most frequently crashes when loading saves that were made mid-round, but it can crash at the base as well. Switching to an earlier proton version however, 7.0.6, makes loading saves perfectly reliable. (you can see some similar mentions in it's protondb page https://www.protondb.com/app/200510)

It does seem to be some issue that's based on the saves themselves however as no matter how many times I relaunch the game and try to load some saves it will never work, whereas other saves will load several times in a row perfectly fine.

Kkisak-valve maintainer 2024-06-06 github

Hello @TheOverpassArsonist, I'm guessing that the misbehaving saves got discarded. The next time you can reliably reproduce that snafu, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, 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. A copy of the save file would also be useful for a Proton dev to ponder.

RradgeRayden 2024-12-28 github

I just grabbed such a log:
steam-200510.log

Save file (enemy within):
save3.zip

Steam Runtime Diagnostics

TTh3M4ch1n3 2025-04-25 github

If you're looking for more data, I've got the save from the GoG version on Proton-GE 9-27 thats also experiencing issues. And I've got the dump from heroic.

Proton versions

Launch options

Upstream links