protonscr

Geometry Wars: Retro Evolved

protonopen appid 8400Game compatibility - Unofficial
ValveSoftware/Proton#39 · opened 2018-08-22 by pprotonrep · updated 2025-08-04 · 12 comments · github · game page · search this game
Ppprotonrep 2018-08-22 github

I tested Geometry Wars: Retro Evolved and it worked perfectly fine for me, including sounds, controller input and effects.

  • Ubuntu 18.04.1 LTS (64 bit 4.15.0-32-generic)
  • GeForce GTX 1070/PCIe/SSE2 (396.51)
  • Proton 3.7 (default configuration)

System information from steam

Llaxdragon 2018-08-22 github

For me, the game crashes when I try to set the resolution to 1920x1080 and hit apply. It runs fine at the default 640x480, but who would want do to that? ;)

edit: config: Ubuntu 18.04 / nvidia 396.51 / note: I use 3 monitors

Ppprotonrep 2018-08-22 github

Hehehe :smiley: That's too bad @laxdragon ! Do you mind sharing your system information? That may help the maintainers pin-point the issue.

FFrans-Willem 2018-08-24 github

Here's how to change the resolution:
https://steamcommunity.com/app/8400/discussions/0/846939071100359808/

Seems non-linux users seem to encounter it too.

Llaxdragon 2018-08-24 github

Thanks! Since this is a windows bug, then it is a non-issue for Proton.

Kkisak-valve maintainer 2025-08-02 github

Geometry Wars: Retro Evolved (8400) crash on start

Issue transferred from https://github.com/ValveSoftware/Proton/issues/8945.
@jpVm5jYYRE1VIKL posted on 2025-08-02T10:33:43:

Compatibility Report

  • Name of the game with compatibility issues: Geometry Wars: Retro Evolved
  • Steam AppID of the game: 8400

System Information

  • GPU: NVIDIA AD103 [GeForce RTX 4070 Ti SUPER]
  • Video driver version: driver: nvidia v: 575.64.05
  • Kernel version: Kernel: 6.15.8-arch1-1 arch: x86_64 bits: 64
  • Link to full system information report as Gist:
  • Proton version: Proton: 1746128130 hotfix-20250501

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.

steam-8400.log

Symptoms

Game not start alsmost immediately after start

Reproduction

install in steam and press start

Ssimifor 2025-08-02 github

@jpVm5jYYRE1VIKL I tried with a setup very close to yours and the game is working fine on my end.

I see that your game is installed into a different partition. Do you know the format of that partition?
If you don't know, you can run the following in your terminal df -T and bring the result here

JjpVm5jYYRE1VIKL 2025-08-04 github

@simifor thanks for your reply

Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p2 ext4 402053392 23522612 358034396 7% /
devtmpfs devtmpfs 32707568 0 32707568 0% /dev
tmpfs tmpfs 32809172 2073024 30736148 7% /dev/shm
efivarfs efivarfs 192 141 47 76% /sys/firmware/efi/efivars
tmpfs tmpfs 13123672 8652 13115020 1% /run
tmpfs tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service
tmpfs tmpfs 32809172 99192 32709980 1% /tmp
/dev/nvme0n1p1 vfat 2043984 534028 1509956 27% /efi
/dev/sda5 ext4 1800559984 1243641444 465378988 73% /mnt/sda5
/dev/nvme0n1p3 ext4 3022640400 54770552 2814253464 2% /home
/dev/nvme0n1p4 ext4 415600556 16830248 377585448 5% /var
tmpfs tmpfs 6561832 280 6561552 1% /run/user/1000

Ssimifor 2025-08-04 github

@jpVm5jYYRE1VIKL it might not change anything, but trying setting the game's launch parameter to this: PROTON_SET_GAME_DRIVE=1 %command%
Also, as a general rule of thumb you shouldn't use proton hotfix, it's preferable to stick to proton 9 or proton 10 (not that it should matter for this particular game).

JjpVm5jYYRE1VIKL 2025-08-04 github

@simifor Tried just now to use PROTON_SET_GAME_DRIVE still crash with same behaviour. Also attemted to do with proton 9-04 . Same result. Also tried to reinstall to original partition where home persist with same result. Look like that persist some kind of indirect unknown requirment of system lib.

Ssimifor 2025-08-04 github

@jpVm5jYYRE1VIKL can you share the output of pacman -Qs nvidia ?

JjpVm5jYYRE1VIKL 2025-08-04 github

@jpVm5jYYRE1VIKL can you share the output of pacman -Qs nvidia ?

local/cuda 12.9.1-1
    NVIDIA's GPU programming toolkit
local/egl-gbm 1.1.2.1-1
    The GBM EGL external platform library
local/egl-wayland 4:1.1.19-1
    EGLStream-based Wayland external platform
local/egl-x11 1.0.2-1
    NVIDIA XLib and XCB EGL Platform Library
local/lib32-nvidia-utils 575.64.05-1
    NVIDIA drivers utilities (32-bit)
local/libvdpau 1.5-3
    Nvidia VDPAU library
local/libxnvctrl 575.64.05-1
    NVIDIA NV-CONTROL X extension
local/linux-firmware-nvidia 20250708-1
    Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs
local/nvidia 575.64.05-2
    NVIDIA kernel modules
local/nvidia-hook 1.5.2-1
    pacman hook for nvidia
local/nvidia-inst 25.7.1-1
    Script to install/uninstall nvidia driver packages in EndeavourOS
local/nvidia-settings 575.64.05-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 575.64.05-1
    NVIDIA drivers utilities
local/opencl-nvidia 575.64.05-1
    OpenCL implemention for NVIDIA

Ssimifor 2025-08-04 github

@jpVm5jYYRE1VIKL I've tried the game on what's basically a mirror of your setup and the game works fine here. Same kernel, same driver version, same generation of gpu (4060). The only notable difference I could see was that you were using nvidia while I was using nvidia-dkms, but switching to match you still doesn't break the game.

Can you use this as your launch parameter and see if the game works with it? WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 %command%