Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No sound at all in The Elder Scrolls Arena (GOG) when launched through Heroic #4409

Open
4Vertikal4 opened this issue Mar 12, 2025 · 1 comment
Labels
bug:unconfirmed Someone works on identifying the issue

Comments

@4Vertikal4
Copy link

4Vertikal4 commented Mar 12, 2025

Describe the bug

When running The Elder Scrolls Arena (GOG version) through Heroic Games Launcher, the game launches and runs correctly, but there is absolutely no sound - no music, no sound effects, nothing. The game is completely silent. Additionally I also tried the set up even though FluidSynth/QSynth, but it didn't work either.

Add logs

https://0x0.st/8S3w.log

Steps to reproduce

  1. Install The Elder Scrolls Arena (GOG version) using Heroic Games Launcher
  2. Launch The Elder Scrolls Arena from Heroic
  3. Game starts and runs, but has no audio output whatsoever

Expected behavior

The game should have complete audio functionality, including music and sound effects, as it does when played natively on Windows or when configured properly through standalone DOSBox.

Screenshots

No response

Heroic Version

Latest Stable

System Information

OS: Fedora 41 Workstation
CPU: 12th Gen Intel i5-12400F
GPU: NVIDIA RTX 3060 Ti
RAM: 16GB
Heroic installation method: Flatpak (system-wide)
Wine version: Wine-GE-Proton8-26

Additional information

I've tried extensive troubleshooting:

I FluidSynth/QSynth setup attempts:

  1. Installed QSynth/FluidSynth: sudo dnf install qsynth fluidsynth
  2. Downloaded soundfonts: FluidR3Mono_GM.sf3 to ~/.local/share/soundfonts/
  3. Tried launching QSynth with various parameters: qsynth -a alsa -m alsa_seq
  4. Verified FluidSynth was running using: aconnect -o | grep qsynth

II DOSBox configuration:

  1. Located DOSBox config files: find ~/Games/Heroic/Arena -name "dosbox*.conf"
  2. Found and reviewed /home/vertikal/Games/Heroic/Arena/dosbox_arena.conf and dosbox_arena_single.conf
  3. Attempted to modify audio settings in these configuration files
  4. Integration script attempts:
  5. Created custom launch script at ~/.local/bin/play-arena.sh
  6. Made it executable: chmod +x ~/.local/bin/play-arena.sh
  7. Script launched QSynth before starting the game through Heroic

III Flatpak permissions:

  1. Added device access: flatpak override --user com.heroicgameslauncher.hgl --device=all
  2. Attempted to access Wine configuration: WINEPREFIX="/home/vertikal/Games/Heroic/Prefixes/default/The Elder Scrolls Arena" flatpak run com.heroicgameslauncher.hgl winecfg

IV Other attempts:

  1. Checked system audio with other applications - works fine
  2. Verified Wine prefix location and structure
  3. Explored DOSBox MIDI and sound settings

Despite all these efforts, the game remains completely silent. I suspect there might be issues with how Heroic's Flatpak implementation handles DOSBox audio passthrough or Wine audio configuration for DOS games specifically.

@4Vertikal4 4Vertikal4 added the bug:unconfirmed Someone works on identifying the issue label Mar 12, 2025
@4Vertikal4
Copy link
Author

4Vertikal4 commented Mar 12, 2025

I did additional troubleshooting:

Reproduction Steps:

  1. Configured dosbox_arena.conf with [sblaster] sbtype=none and [midi] midiconnect="FLUID port".
  2. Attempted starting FluidSynth with:

fluidsynth -s -a alsa -m alsa_seq "$HOME/.local/share/soundfonts/FluidR3Mono_GM.sf3" &

Result: Process is immediately paused/terminated (message "Zatrzymano"/Stopped).

  1. Tried connecting MIDI ports:
    aconnect failed (Operation not permitted) due to permissions/Flatpak isolation.

Current Symptoms:

  1. FluidSynth fails to run persistently (stops after starting).
  2. MIDI connection command errors due to permission restrictions (even with sudo).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:unconfirmed Someone works on identifying the issue
Projects
None yet
Development

No branches or pull requests

1 participant