@kisak-valve Thanks for not closing this issue I made. I actually discovered today that the current version of proton borked a lot of my games that worked with 4.2.2. (it's just that this game in particular doesn't have an open issue) I wish I could revert. I guess I'll hope 4.2.4 fixes everything 4.2.3 broke.
Update: The new version 4.2.3 actually didn't break a bunch of my games those issues were fixed with a system reboot but the issue with this game remains. I tried tweaks but they didn't work and read on protondb that it's because my xbox 360 is plugged in which is a shame because it use to work regardless of that and I don't want to play this game with keyboard and mouse.
Do you hear audio during cinematics with Proton?
As described here: https://bugs.winehq.org/show_bug.cgi?id=41047, the A3Dapi.dll is necessary for the game to find a sound card but you can not hear audio cinematics. Erase A3Dapi.dll and you can hear audio cinematics but you will obtain no audio ingame. Is it a bug for our FAUDIO dev?
@legluondunet
I can't even get to the point where audio would be a concern because the game doesn't start anymore. (according to protondb it's because I have my xbox 360 controller plugged in but that use to not be a problem prior to the current proton version)
In the previous version where the game worked the audio worked fine as well.
I just launched it with my RX580 and it works very well. Proton 4.2-3 and today build of steam beta.
However, the multiplayer doesn't work, it complains about IPX not being available. I don't even know if that game can be played over the internet or if that's just a LAN thing.
@Flaburgan
It probably worked because you didn't have a controller plugged in. I tested it with 4.2.4 and it still doesn't work when the controller is plugged in.
With Proton 5.13-1, cinematics remain with no-sound in game.
@leillo1975
try this workaround:
copy dsound.dll file in game folder
<Workaround removed by moderator
then put dsound.dll as native, builtin in proton config.
Hello @legluondunet, the workaround you linked is legally problematic and has been removed.
@leillo1975
try this workaround:
copy dsound.dll file in game folder
<Workaround removed by moderator
then put dsound.dll as native, builtin in proton config.
The problem is that using this DLL I have sound on movies and not in game. I hope proton devs found a solution for this great game.
And of course, thanks for the tip
Hello @legluondunet, the workaround you linked is legally problematic and has been removed.
I understand perfectly @kisak-valve. But It's could help to know that this workaround works for me on different computers, for cinematics and ingame sounds.
Perrhap's you can let me precise that only a dsound.dll with md5 sum a97542f6c1b3c99e739e6d2a79c1e1a3 works.
I miss being able to use my xbox 360 controller for this game. sigh (referring to the brief time it worked when 4.2 was the latest version. In case you're wondering reverting the steam client to that branch doesn't cause it to work. )
Star Wars Episode 1 Racer broken audio in cutscenes (808910)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5820.
@jonkoops posted on 2022-05-05T21:13:38:
During any of the cutscenes, such as the game intro no sound is audible.
Start the game and view the introduction cutscene.
Hello @legluondunet, looks like you were looking for #1474 instead of this compatibility report.
Audio for the cutscenes still seems to be broken on deck as of the latest Experimental proton like the intro fmvs
steam-808910.log
Cutscenes still missing audio with Proton 10.0 beta-1, but no other issues.
Upon launching my GOG copy, the game automatically closes. Launching it with the game's -v launch option brings up a black, monitor resolution-sized window and a smaller resolution selection window, and the game crashes after I click the Accept button.
steam-10303635730072600576_default.log
steam-10303635730072600576_ -v.log
Launch the game with either no launch options or with -v.
Cutscenes audio still doesn't work with Proton 11.0-1, but I've found a workaround some people shared on Protondb.
dsound.dll (32bit) in the game's folder (versions 6.3.9600.16384 and 6.2.9200.16384 worked fine on my end) WINEDLLOVERRIDES="dsound=n,b" %command%Hi all, just wanted to let you know that I submitted a patch upstream in Wine to fix the sound issue in the cutscenes.
FYI the 'no audio in cutscenes' issue has been fixed by my PR, which has landed as part of Wine 11.9.
@jonkoops Thank you for contributing to Wine and for the heads up here! We've cherry-picked your commit and it is already in the Proton - Experimental bleeding-edge branch, and it will be in the next regular Proton - Experimental release :)
@alasky17 Thanks! I just tested on the latest Proton Experimental, and the cutscenes are indeed working as expected.
Now that the cutscene audio fix has landed in Proton Experimental, I believe the original issues tracked here are resolved. The game launches and plays fine with full audio.
@codeman101, is the game still failing to launch with an Xbox 360 controller plugged in? That was last reported in 2020, so it may well have been fixed since (I don't have controller to test with). @thasreal, is the GOG version crash still occurring on the latest Proton Experimental?
If all reported issues are resolved, could this be closed?
I can also confirm the intro fmvs are now finally playing audio on my deck too with experimental
@kisak-valve considering the above, perhaps this issue can be closed?
@kisak-valve considering the above, perhaps this issue can be closed?
@jonkoops typically these issues continue to stay open even if the game works flawlessly, just as a current status on how the game plays.
proton experimentalx2 2026-05proton 11.0-1x1 2026-04proton 10.0x1 2025-05proton 5.13-1x1 2020-11proton 4.2-3x1 2019-05WINEDLLOVERRIDES="dsound=n,b"x1 2026-04WINEDLLOVERRIDES="dsound=n,b" %command%x1 2026-04dsound.dllx4 2026-04a3dapi.dllx1 2019-05
Compatibility Report
System Information
I confirm:
steam-808910.log
Symptoms Doesn't start.
Reproduction
Install the game and try to launch it. The screen with go black but then it will go back and the game will be killed. This game use to work fine with a previous 4.x version of proton but the current 4.2.3 borked it.