Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Steam isn't running a shell and may not inherit things like your PATH variable.
I would need to see the scripts to evaluate.
Or you could try this. it might work:
bash -c '/home/username/bin/create_virtual_speakers.sh && %command% && /home/username/bin/delete_virtual_speakers.sh'
There could be Ubuntu specific issues as well, which is what Zyro is getting at. I'm not an Ubuntu user, but as I understand it Canonical has created a snap version of Steam that gets installed if you install Steam using Ubuntu's store or package manager.
If you using the snap version, you might try using the deb package from valve instead. You may find you don't even need these scripts.
Specifically, describe what you tried to do in game, what you know works outside of PEAK, and what your fix does that works only for PEAK.
And for the love of God, stop mentioning your love story with ChatGPT. Especially if you don't have a problem with what it creates, or if you don't show the scripts at all, it's pointless to mention.
Script to create looks like this
#!/bin/bash
pactl load-module module-null-sink sink_name=VirtualSink sink_properties=device.description=VirtualSink
And to delete
#!/bin/bash
module_id=$(pactl list short modules | grep module-null-sink | grep VirtualSink | awk '{print $1}')
if [ -n "$module_id" ]; then
pactl unload-module "$module_id"
fi
The 1st potential problem is that you are using the snap version which is sandboxed. Steam in this configuration may not have permissions to access your bin directory.
The 2nd potential problem is that when you add this to the launch options, it may not be aware of your $PATH variable, therefore, it may not know what/where pactl is.
Just an FYI, Valve engineer Timothée “TTimo” Besset explicitly stated that Valve is not involved in the Snap packaging and doesn’t support it. I can't link to it because he said it on Mastodon.
It seems the game has specific problems, but be aware that Snap could keep your games from accessing some system resources as well.