dotAGE
No sound on Ubuntu 22.04
Running the game on a Thinkpad P1 with (up to date) Ubuntu 22.04, and I very rarely have sound. I usually have to restart my laptop, and switch the audio output off and back on after the initial loading screen in order to start getting audio. I also usually have to attempt this several times. I do not have this problem with other games.

If any other additional system info or output logs would be helpful let me know! Love the game.
Originally posted by Catman:
Originally posted by Edible Banana:
FYI, IIUC this is fixed in the latest version of Unity (I think one of the things fixed in the 0.0.8 update of Shapez 2 which had the same problem: https://shapez2.wiki.gg/wiki/Changelog ), and the issue linked earlier in this thread is marked as fixed by Unity.
Probably just need to update the game to use the latest version of Unity to finally fix this bug :)

Good! I actually just released the patch 1.4 yesterday which updates the Unity version, among other things, to 2023.2.34f1, and the bug seems to be fixed in 2023.2.20f1 (previously we were on 2023.2.14). Could anybody confirm whether this is fixed?
< >
Showing 1-15 of 21 comments
OctoberCain 6 Dec, 2023 @ 4:33pm 
I am having the same issue on Ubuntu 22.04.
Similar issue on Ubuntu 22.04.3 LTS. Just got the game, and it had no sound at all, even after rebooting the computer. Then, I tried "switching the audio device" to a non-functional output, and then back again, after the game was started based on @ExtremeACrepairman 's workaround, and that got sound working.
Catman  [developer] 16 Jan @ 5:01am 
Thank you for the reports. I am not using anything weird for sound, it is the stock audio engine of Unity, so I wonder what may be happening.

Could you try the Experimental branch? I updated the engine there and it may solve your issue!
Atlas 22 Jan @ 5:27pm 
Originally posted by Catman:
Could you try the Experimental branch? I updated the engine there and it may solve your issue!
I'm having the same issue but with EndeavourOS Linux, kernel version 6.7.0-zen3-1-zen. Tried the experimental branch, but had no success in playing with audio. Nonetheless, with proton, the audio plays just fine, so I can still play.
Catman  [developer] 22 Jan @ 8:44pm 
If any of you could send me the Player.log file found among save files I can check whether there is some hint at what is happening. See the sticky post
Maybe you should take a look at this Unity issue[issuetracker.unity3d.com] and the related thread on the FMOD's forum[qa.fmod.com]. From what I understand, Unity is using an old FMOD version in their engine that doesn't select the right output device. Using something like pavucontrol (PulseAudio Volume Control) to switch game output to the right device or disabling other output devices works.
Last edited by BloodScourge; 23 Jan @ 1:54pm
The Unity issue appears to be what is happening. The game seems to be defaulting to the wrong audio output. Changing that to the correct one gets sound working for it.

The output it defaults to always seems to be the first sink listed when using:
pactl list sinks
Atlas 23 Jan @ 5:26pm 
Originally posted by Catman:
If any of you could send me the Player.log file found among save files I can check whether there is some hint at what is happening.

Hey, sorry for the delay, here are the game0.age and profile0.age files. I had no Player.log files among those.

Filebin [filebin.net]
Last edited by Atlas; 23 Jan @ 5:26pm
Catman  [developer] 24 Jan @ 5:34am 
Originally posted by BloodScourge:
Maybe you should take a look at this Unity issue[issuetracker.unity3d.com] and the related thread on the FMOD's forum[qa.fmod.com]. From what I understand, Unity is using an old FMOD version in their engine that doesn't select the right output device. Using something like pavucontrol (PulseAudio Volume Control) to switch game output to the right device or disabling other output devices works.

Thanks! This seems to be exactly the issue. Unfortunately it seems that it is an engine issue and a workaround should be used until a patch comes, as there is no way in Unity to select another sound device with the default audio engine. I'll be monitoring the issue on the tracker
Bip 9 Feb @ 9:28pm 
Does this affect the demo on Windows 10? I don't have any sound, either, playing the demo, and I can't seem to figure out a workaround. I've tried switching audio outputs while the game is running and it didn't help.

Edit: I managed to get the sound to work! I can only seem to get this to work with my wireless headphones, though. What seems to do it is to turn off sound in the audio mixer while in the game, then quit the game, then turned the sound back on and off a few times outside of the game and left it on. Then I started the game. I can't seem to reliably reproduce this, though. It could be chance for all I know. Perhaps this issue with Unity is also affecting Windows 10 installs.

Once I get it to work, I can exit and restart the game and the sound still works.
Last edited by Bip; 9 Feb @ 9:57pm
Originally posted by Catman:
Originally posted by BloodScourge:
Maybe you should take a look at this Unity issue[issuetracker.unity3d.com] and the related thread on the FMOD's forum[qa.fmod.com]. From what I understand, Unity is using an old FMOD version in their engine that doesn't select the right output device. Using something like pavucontrol (PulseAudio Volume Control) to switch game output to the right device or disabling other output devices works.

Thanks! This seems to be exactly the issue. Unfortunately it seems that it is an engine issue and a workaround should be used until a patch comes, as there is no way in Unity to select another sound device with the default audio engine. I'll be monitoring the issue on the tracker

Definitely a bummer, this was happening to me with Valheim too. But, until this is fixed here is something that worked for me in both DotAge and Valheim:

https://unix.stackexchange.com/a/67398/340600
Catman  [developer] 18 Feb @ 6:51am 
Originally posted by ExtremeACrepairman:
Originally posted by Catman:

Thanks! This seems to be exactly the issue. Unfortunately it seems that it is an engine issue and a workaround should be used until a patch comes, as there is no way in Unity to select another sound device with the default audio engine. I'll be monitoring the issue on the tracker

Definitely a bummer, this was happening to me with Valheim too. But, until this is fixed here is something that worked for me in both DotAge and Valheim:

https://unix.stackexchange.com/a/67398/340600

Thanks, I'll be sticking this for now!
I wrote a short bash script that implements the workaround in the marked post. Here's the content, which I have saved as change_dotAge_sink:

#!/bin/bash default_sink=$(pactl get-default-sink) sink_changed=false sleep 1 while (( $SECONDS < 5 )) && [[ $sink_changed = false ]]; do sink_input=$( pactl list sink-inputs | perl -ne \ 'if (/^Sink Input #(\d+)/) { $sink = $1 } elsif (/dotAge/.exe/ && defined $sink) { print "$sink\n"; undef $sink }' ) pactl move-sink-input $sink_input $default_sink && sink_changed=true done

You can save this somewhere in your $PATH (for example, ~/bin) and add it to your launch options:
%command% & sleep1; change_dotAge_sink; fg
or if you don't want to pollute your $PATH, move the file to ~/.steam/debian-installation/steamapps/common/dotAge and instead change your launch options to
%command% & sleep1; ./change_dotAge_sink; fg

Edit: Fixed conditional in the while loop
Last edited by Tokerante; 22 Aug @ 1:07am
FYI, IIUC this is fixed in the latest version of Unity (I think one of the things fixed in the 0.0.8 update of Shapez 2 which had the same problem: https://shapez2.wiki.gg/wiki/Changelog ), and the issue linked earlier in this thread is marked as fixed by Unity.
Probably just need to update the game to use the latest version of Unity to finally fix this bug :)
A developer of this app has indicated that this post answers the original topic.
Catman  [developer] 2 Oct @ 11:49pm 
Originally posted by Edible Banana:
FYI, IIUC this is fixed in the latest version of Unity (I think one of the things fixed in the 0.0.8 update of Shapez 2 which had the same problem: https://shapez2.wiki.gg/wiki/Changelog ), and the issue linked earlier in this thread is marked as fixed by Unity.
Probably just need to update the game to use the latest version of Unity to finally fix this bug :)

Good! I actually just released the patch 1.4 yesterday which updates the Unity version, among other things, to 2023.2.34f1, and the bug seems to be fixed in 2023.2.20f1 (previously we were on 2023.2.14). Could anybody confirm whether this is fixed?
< >
Showing 1-15 of 21 comments
Per page: 1530 50