Closed megabytesofrem closed 1 month ago
I'm not sure why this happens, but this is more likely to do with some system/Wine problem than SteamTinkerLaunch, as you can check the script and see it isn't touching audio sources. I'm not even sure how it would do this, it's likely a Wine issue.
Also, you're using a very out-of-date version of SteamTinkerLaunch. Only the latest commit on master is ever supported at any given time, the issue templates asks you to check out master before filing an issue. Not that I expect it to resolve it, but worth noting.
I'm not sure why this happens, but this is more likely to do with some system/Wine problem than SteamTinkerLaunch, as you can check the script and see it isn't touching audio sources. I'm not even sure how it would do this, it's likely a Wine issue.
Also, you're using a very out-of-date version of SteamTinkerLaunch. Only the latest commit on master is ever supported at any given time, the issue templates asks you to check out master before filing an issue. Not that I expect it to resolve it, but worth noting.
The issue was due to lib32-pipewire
not being present on the system. In reference to the out of date version, should I use ProtonUpQT to install it instead?
You can use ProtonUp-Qt or clone the repo and sudo make install
. Make sure to update regularly when you see new commits, regardless of what method you choose.
Be sure to uninstall with your package manager first, but make sure you still have the necessary dependencies installed as neither the Makefile nor ProtonUp-Qt handles dependencies for you.
There is also an AUR steamtinkerlaunch-git
package but I'm unsure of the status of that.
The issue was due to lib32-pipewire not being present on the system
Wine/Proton likely depends on this, makes sense. They have dependencies on quite a few 32bit packages.
EDIT: Interesting, I can't see PipeWire noted anywhere on the Wine dependencies. I wonder where this requirement comes from. I do have PipeWire on my system, but not lib32-pipewire! I wonder what requires this, and why you ran into this issue. Perhaps this dependency is specific to Valve's flavour of Wine. I'm running vanilla Arch and not endeavourOS although I'm not sure that would make such a difference here.
I have at least one display with audio out, but I haven't had issues with the wrong audio source being used. I just tested again, although I'm using ModOrganizer v2.4.4 and not v2.5.0.
Still, I don't think this is specific to SteamTinkerLaunch, but a Wine oddity. Good to note that lib32-pipewire fixed it for you, in case others run into the problem.
EDIT 2: Ah, Wine depends on various ALSA/libpulse packages, including 32bit variants. It's possible lib32-pipewire satisfies some kind of dependency here.
System Information
Issue Description
Launching Fallout New Vegas through ModOrganizer 2 results in the audio for the game being sent to the incorrect audio source (monitor audio) instead of headphone audio (despite headphone audio being set as default).
This does not happen when running the game normally, or clicking "Play" on SteamTinkerLaunch itself but rather when pressing the play arrow on ModOrganizer 2. This occurs even when the incorrect audio source is disabled in the KDE System Settings.
Logs