HGL
Heroic Games Launcher•2mo ago
wise-white

Heroic starts a second time when game is launched from Steam

When launching a game installed through Heroic from Steam, it starts a second instance of Heroic and takes a ~1 minute to launch the game, if at all. 
Memory: 16.69 GB (used: 5.7 GB)
GPUs:
  GPU 0:
    Name: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480
    IDs: D=67df V=1002 SD=04a8 SV=1043
    Driver: amdgpu
OS: NixOS 25.11 (Xantusia) (linux)
The current system is not a Steam Deck
We are not running inside a Flatpak container
Software Versions:
  Heroic: 2.18.1 "Waterfall Beard" Jorul
  Legendary: 0.20.37 Exit 17 (Heroic)
  gogdl: 1.1.2
  comet: comet 0.3.1
  Nile: 1.1.2 Will A. Zeppeli
Memory: 16.69 GB (used: 5.7 GB)
GPUs:
  GPU 0:
    Name: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480
    IDs: D=67df V=1002 SD=04a8 SV=1043
    Driver: amdgpu
OS: NixOS 25.11 (Xantusia) (linux)
The current system is not a Steam Deck
We are not running inside a Flatpak container
Software Versions:
  Heroic: 2.18.1 "Waterfall Beard" Jorul
  Legendary: 0.20.37 Exit 17 (Heroic)
  gogdl: 1.1.2
  comet: comet 0.3.1
  Nile: 1.1.2 Will A. Zeppeli
Running the command Steam executes from the terminal works properly. Each time I run heroic, it starts up a new instance Logs from client 1: https://0x0.st/8FsZ.log Logs from client 2: https://0x0.st/8FsN.log Any help is much appreciated
Solution:
https://github.com/NixOS/nixpkgs/issues/432037
GitHub
heroic: opens new instance instead of closing · Issue #432037 · N...
Nixpkgs version Unstable (25.11) Describe the bug Heroic will start a new instance every time the executable is run instead of closing with the following message: Heroic is already running, quittin...
Jump to solution
5 Replies
CommandMC
CommandMC•2mo ago
Please send in your game log (/home/ny/.local/state/Heroic/logs/games/1207659023_gog/launch.log) Note that the NixOS package is unofficial & has known issues. For a more consistent experience, you might want to use the Flatpak
wise-white
wise-whiteOP•2mo ago
Thanks for helping, here ya go: https://rusty.ccnlc.eu/overexcitably-semiprecious-nicol.log Although I don't think it is game related, as running heroic multiple times in a terminal would start a new instance per terminal. It feels like Heroic instances can't see one another, Running the flatpak works perfectly
Solution
wise-white
wise-white•2mo ago
https://github.com/NixOS/nixpkgs/issues/432037
GitHub
heroic: opens new instance instead of closing · Issue #432037 · N...
Nixpkgs version Unstable (25.11) Describe the bug Heroic will start a new instance every time the executable is run instead of closing with the following message: Heroic is already running, quittin...
CommandMC
CommandMC•2mo ago
Hm yeah I'm not sure why that's happening. The general log you've uploaded above is the same file by the way (the 2nd instance moves the current log to heroic.log.old and writes heroic.log, then both instances continue to use heroic.log). As far as I can tell the game log looks normal, not sure where the slowdown could come from (you should probably install d3dcompiler_43 and/or _47 with Winetricks, but that's a game-specific issue)
wise-white
wise-whiteOP•2mo ago
the nix package seems to wrap heroic in an FHS environment which uses bubblewrap, so i guess somewhere the IPC gets lost Thanks for the help

Did you find this page helpful?