Anno 1602: History Edition

protonopen appid 2820130Game compatibility - Unofficial

ValveSoftware/Proton#7679 · opened 2024-04-28 by haffmans · updated 2026-08-31 · 4 comments · github · game page · search this game

Hhaffmans 2024-04-28 github

Compatibility Report

Name of the game with compatibility issues: Anno 1602: History Edition
Steam AppID of the game: 2820130

System Information

GPU: Radeon RX 6700 XT
Video driver version: Mesa 24.0.5-arch1.1
Kernel version: 6.8.7-arch1-1
Link to full system information report as Gist: here
Proton version: Various Proton-GE 8+ (all show same symptom), currently UMU Launcher Proton (GE) 9.0-beta16; using Heroic Launcher

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

Game starts up with a completely pink window first, instead of showing the epilepsy warning
The Settings show large pink areas where the (modernized) UI should show up. The close (X) button on the right top corner still responds but with the invisible UI it is unusable.
The Multiplayer screen also shows a completely pink window instead of the UI

Proton debug log: steam-heroic-0.log

Reproduction

Appears to be the same for multiple users, also using the Steam version, as per ProtonDB reports. Appears every time the game is launched.

Update: adding winetrick d3dcompiler_47 solves the problem for me

MMartinX3 2025-08-31 github

The game probably doesn't work anymore.
I installed d3dcompiler_47 and the Ubi Connect launcher via Protontricks.
But it just crashes after the startup logo.
The little startup logo has also wrong colors.

steam-2820130.log

Ssimifor 2025-08-31 github

@MartinX3 Wipe the game's prefix and swap out of third party builds of proton. I installed the game on deck and desktop, and it seems to be working fine without any extra steps. If problems persist, attach a new log.

MMartinX3 2025-09-14 github

@simifor the new log:
steam-2820130.log

Kkacperpaczos 2026-08-31 github

Ubisoft Connect GameStarter never initializes — game process waits forever with no window; works on GE-Proton10-34

System: Fedora (kernel 7.1.10-200.fc44), KDE Plasma on Wayland, Intel Core Ultra 7 258V (Intel Graphics, Lunar Lake), 32 GB RAM. Ubisoft Connect 173.0.13316 (built Aug 6 2026), installed by the game's Steam install script into the game's prefix.

Symptoms: Launching the game starts Anno1602.exe -uplay_steam_mode, which starts Ubisoft Connect. UC opens and logs in via Steam ticket, but the game itself is never launched: no game window, no sound. The wrapper process stays alive indefinitely at ~3% CPU and UC's Library shows "This game is currently running".

Log evidence (from .../pfx/drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/logs/), on every launch since installation:

launcher_log.txt: PlayGame.cpp (1571) Gamestarter must be initialized before game can be launched. followed by PlaySession.cpp (364) Play session (1) successfully started for game 7023. — then nothing further.
game_starter_log.txt is 0 bytes since installation.
service_log.txt: PolledPipeSocket.cpp (311) Executing asynchronous IO operation failed, code: 109 / PolledPipeSocket.cpp (360) Fail to complete async IO, closing 109 every session.

This looks like the same GameStarter mechanism failure analyzed in #9535 (transferred into https://github.com/ValveSoftware/Proton/issues/6507#issuecomment-3977165254): UbisoftGameLauncher.exe is spawned with -gamelauncher_wait_handle 1140 -upc_uplay_id 7023 ... and never progresses past the handle wait, so the game_start_ipc_pipe_ pipe is never created and no StartGrantedRsp reaches the game.

Tested, same prefix in all cases:

Proton 9.0-4 — broken
Proton Experimental (buildid 24943653) — broken
Proton Hotfix (buildid 24999779, updated 2026-08-31) — broken
GE-Proton10-34 — works. On its very first launch GameStarter initialized (HKCU\Software\Ubisoft\Uplay\GameStarter\7023 got created) and the game starts with window and sound.

Additional observation: the UC installer only created HKLM\Software\Wow6432Node\Ubisoft\Launcher; the native 64-bit registry view was missing entirely and service_log.txt logged RegistryUtils.cpp (284) Uplay is not installed. We manually mirrored Launcher\InstallDir and Launcher\Installs\7023\InstallDir into the native view before the GE-Proton test; this alone did not fix Valve Proton (unverified whether it contributed to the GE-Proton result).

PROTON_LOG=1 logs available for both the failing (Valve Proton) and the working (GE-Proton10-34) runs — happy to attach.