Rocket League (252950)

[Oliver-1xok]

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: GTX 970
• Driver/LLVM version: nvidia 440.59
• Kernel version: 5.3.0-28-generic BattleEye Fails startup on Linux using latest Proton #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
• Link to full system information report as Gist:
  https://gist.github.com/Oliver-1xok/1faf131563237060edc339a413646150
• Proton version: 5.0-1

LOGS

Here are the Proton logs from my system:
steam-252950.log

Here is an output of the PS command for the corresponding processes which are created in the system:
ps.log

Symptoms

When I start the experimental DX11 client from Rocket League the game does not work.

You can start this client with the launch option "-dx11". A window appears with the title: "Rocket League (64-bit, DX11, Cooked)".

The window does not disappear and is not updated after a while. No window with the game appears.
The 32-bit DX9 client of the game runs on my system without major problems and the game starts after a short time. The experimental DX11 client no longer does this.

Reproduction

1. Follow these steps:
   https://steamcommunity.com/app/252950/discussions/0/1738889518180525789/
2. For additional Proton Log use the following launch options: "PROTON_LOG=1 %command% -dx11"
3. Click on Start

[kisak-valve]

Hello @Oliver-1xok, just to check, was PROTON_LOG=1 %command% -dx11 what you tried to use in the game's launch options to generate a log? Environment variables have to come before the command that's being run.

[Oliver-1xok]

Hello @Oliver-1xok, just to check, was PROTON_LOG=1 %command% -dx11 what you tried to use in the game's launch options to generate a log?

Of course not. :/

Thank you for the hint! Sorry, my mistake. The proton logs are generated without problems. I added them to the report and also recreated the output of the PS command.

(I also updated Steam Info again, because my Steam Client has been updated in the meantime.)

[doitsujin]

D3D11 GPU hangs should be fixed as of doitsujin/dxvk@4aa6800.

Do note that the renderer seems to be quite buggy so there might be further issues.

[WernerAUT]

can confirm with doitsujin/dxvk@4aa6800
Rocket League runs without issues under D3D11, i played some rounds without any issues.

[Oliver-1xok]

can confirm with doitsujin/dxvk@4aa6800
Rocket League runs without issues under D3D11, i played some rounds without any issues.

Just for clarity: You tested it with a self-compiled version of DXVK that contains doitsujin/dxvk@4aa6800 ?
And you also tested it with an Nvidia card?

(I haven't had time to test it yet.)

[WernerAUT]

correct, but i didn't compile it myself :) Philip has his buildbot :)
https://git.froggi.es/doitsujin/dxvk/pipelines?scope=finished&page=1
I overwrote the 32bit and 64bit dll's in proton 5.0-2 (released some minutes ago) inside steam.
Yes i use Nvidia it is a GTX 1070.
Played again around 30 minutes without issues

[Oliver-1xok]

correct, but i didn't compile it myself :) Philip has his buildbot :)

Ah, it's easier, of course. Thanks for the advice!

[Oliver-1xok]

can confirm with doitsujin/dxvk@4aa6800
Rocket League runs without issues under D3D11, i played some rounds without any issues.

Can also confirm. I tested again with proton 5.0-2. With the release version of DXVK the game did not start. Then I used this build:

https://git.froggi.es/doitsujin/dxvk/pipelines/1068

I copied the libraries from "build/dxvk-release/x64" to "steamapps/common/Proton 5.0/dist/lib64/wine/dxvk".

Rocket League runs normally afterwards. It doesn't run as smooth as the D9 version due to the missing VSync in this experimental version. But this is another problem.

So I think Philip has fixed this problem.

[doitsujin]

Rocket League runs normally afterwards. It doesn't run as smooth as the D9 version due to the missing VSync in this experimental version

You can force vsync via dxvk.conf options, specifically dxgi.syncInterval = 1.

[WernerAUT]

hm in proton were should this dxvk.conf file go? i created one in my steam folder, and in Steam at the run options i added DXVK_CONFIG_FILE=/home/mine/Games/Steam/dxvk.config but it seems to get ignored

[doitsujin]

The environment variable should work fine, best double-check whether both the path and content of the file are correct.

[CSahajdacny]

What is the default location for the dxvk.conf file?

[Oliver-1xok]

What is the default location for the dxvk.conf file?

There is no default. Set the following launch option

DXVK_CONFIG_FILE=/your/dir/here/dxvk.conf %command%

Of course you have to replace /your/dir/here/ with the directory where your dxvk.conf is located.

You can download a commented dxvk.conf to your current directory with this command:
wget https://raw.githubusercontent.com/doitsujin/dxvk/master/dxvk.conf

You then simply adapt this conf to your needs. It works fine. Just tested it.

[Oliver-1xok]

You can force vsync via dxvk.conf options, specifically dxgi.syncInterval = 1.

I did not know the VSync option yet. Great option. The game becomes very smooth again. Works better than the VSync implementation by the Nvidia driver, which almost always results in micro stutterers.

The only thing I notice with dxgi.syncInterval = 1 are regular yellow spikes for single frames in the frame time graph during gameplay. The max frame time doubles from 17 ms to most 34 ms. However, I do not notice any disturbing stuttering. I don't really notice anything. I just see it in the graph.

Without VSync my GTX 970 reaches 120 to 180 fps in the DX11 client of Rocket League. 120 fps constant in any case. (With all graphic settings at maximum.)

This just for feedback.

[Anupalabdhi]

Though the DX9 version seems to start up and work. Rocket League DX11 version has stopped working again. The logs are identical to the ones posted originally in the issue (at least to my untrained eye).

steam-252950.log

The log is generated with latest mesa-aco from Valveaur repo, but even with regular mesa 20.x the dx11 version of the game was not working

[chevalmuscle]

Works for me with the -dx11 flag

GPU: GTX 1050 Ti
Driver/LLVM version: nvidia 435.21
Kernel version: 5.3.0-42
Proton version: 5.0-5

Don't forget to force the use of steam play because Psyonix is no longer supporting the game on linux

[Anupalabdhi]

After further testing, It seems that the Rocket League DX11 version does indeed start, but it does so after stalling at the startup logo for a good while (full 2 minutes as per my stopwatch). In the meanwhile the menu music is playing in the background even though the game is still showing the Psyonix start up logo. After two minutes when it finally reaches the menu, the "Press any button" starts blinking rapidly as if catching up to the amount of blinks it missed due to the delay. After a while it too settles down into the normal rhythm.

Something strange is going on, I must admit.

For completion's sake, I am attaching another log, after entering the game and closing it.

steam-252950.log

EDIT: For some reason (probably an update at my end), the game is now starting up properly.

[JoranDox]

AMD user here, I'm getting stutters after a few games, growing worse and worse.
Restarting rocket league doesn't seem to have any effect, but restarting my pc does. This to me feels like some form of memory leak or something like that? Haven't tested if e.g. restarting steam works too, I'll try working out what the exact "refresh" trigger is in the following days (takes a few games (or X time?) for the stutters to get noticably bad).

I haven't experienced this issue with Monster Hunter World, the only other game I've really played on my new machine, so I'm guessing it has something to do with rocket league, but not very sure.

I'm not running anything else apart from discord as this is a fresh install of ubuntu 20.04
Proton: tried with both 5.0-6 and 5.6-GE-2
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 5700

other system details here: https://gist.github.com/JoranDox/ccc321a93a5f7105f698a9eaccd29e59
protonlog: steam-252950.log

[bgrnwd]

Seeing a similar issue here as well.

CPU: AMD Ryzen 5 3600X
GPU: NVIDIA GeForce RTX 2070 Super
Proton Version: 5.0.9
Kernel: 5.6.19-2-MANJARO
Drivers: nvidia 440.100

I'm able to get Rocket League to launch to a black screen and then it quits.

Here's my `user_settings.py` and I am running Rocket League with `-dx11` as a launch option

#To enable these settings, name this file "user_settings.py".

#Settings here will take effect for all games run in this Proton version.

user_settings = {
    #Logs are saved to $HOME/steam-<STEAM_GAME_ID>.log, overwriting any previous log with that name.

    #Wine debug logging
    "WINEDEBUG": "+timestamp,+pid,+tid,+seh,+debugstr,+loaddll,+mscoree",

    #DXVK debug logging
    "DXVK_LOG_LEVEL": "info",

    #vkd3d debug logging
    "VKD3D_DEBUG": "warn",

    #wine-mono debug logging (Wine's .NET replacement)
    "WINE_MONO_TRACE": "E:System.NotImplementedException",
    #"MONO_LOG_LEVEL": "info",
    "PROTON_LOG": "1",
    #Enable DXVK's HUD
#    "DXVK_HUD": "devinfo,fps",

    #Use OpenGL-based wined3d for d3d11, d3d10, and d3d9 instead of Vulkan-based DXVK
    "PROTON_USE_WINED3D": "1",

    #Disable d3d11 entirely
#    "PROTON_NO_D3D11": "1",

    #Disable eventfd-based in-process synchronization primitives
#    "PROTON_NO_ESYNC": "1",

    #Disable futex-based in-process synchronization primitives
#    "PROTON_NO_FSYNC": "1",
}

The only error I see in my steam-252950.log is this:

245.965:00c8:00cc:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution

Edit

Was able to get rid of the ntlm_auth issue but still the same result where I get to a black screen and then the game crashes

[kisak-valve]

Rocket League not launching

Issue transferred from #4257.
@Owez posted on 2020-10-12T16:48:25:

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: RX580
• Driver/LLVM version: Mesa 20.0.8 (LLVM 10.0.0) (taken from vulkaninfo)
• Kernel version: 5.4.0-48-generic
• Link to full system information report as Gist: Info
• Proton version: Proton 5.0-9

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-252950.log

Symptoms

I have tried to launch the game but it doesn't show anything and fails after ~5 seconds of a "cancel x" or "stop x" button. I have tried reinstalling steam and wiping all .steam/ along with reinstalling the game from my ext-4 partitioned external drive to root ssd (even though that shouldn't be a problem). Can't seem to get it to work apart, using the PROTON_USE_WINED3D=1 or leaving it out of the launch options.

Reproduction

Not sure how to reproduce, I can only find some errors regarding cryptic memory addresses and pid swaps once it crashes (which I assume is steam handling pid control, not the game). This started a week ago and it may be an issue with updated graphics drivers but a lot has been changed apart from a upgrade updating drivers near the time for my RX580. Running on linux mint 20, all stock with only steam and programming tools installed (e.g. vscode which shouldn't affect in any way).

[kisak-valve]

Hello @Owez, something's abnormal about your video drivers and : CommandLine Error: Option 'help-list' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options in the log supports that impression. In particular, the extended diagnostic information says that you have mesa 20.1.5 / llvm 10.0.1 when testing OpenGL, and mesa 20.0.8 / llvm 10.0.0 for Vulkan. This version mismatch is unusual and I wouldn't be surprised if it's the root of the issue you're seeing.

[Owez]

Appreciate the response @kisak-valve , will try to fix the mismatch: does seem like that's the issue in retrospect.

[oblitum]

After latest recent game update, steam update, and proton update (so I ignore which update is the cause), the game or steam client is crashing when starting, both game and steam closes. This is the log.

[kisak-valve]

Hello @nuno1212s, I'm not that familiar with AMD+nVidia systems like yours, but you might be seeing something similar to ValveSoftware/steam-runtime#312 and if that's the case, then it might be worthwhile to test temporarily disabling mesa/radv with something like sudo mv /usr/share/vulkan/icd.d/radeon_icd.x86_64.json /usr/share/vulkan/icd.d/radeon_icd.x86_64.json.disabled and see if that has an effect.

[nuno1212s]

Hello @nuno1212s, I'm not that familiar with AMD+nVidia systems like yours, but you might be seeing something similar to ValveSoftware/steam-runtime#312 and if that's the case, then it might be worthwhile to test temporarily disabling mesa/radv with something like sudo mv /usr/share/vulkan/icd.d/radeon_icd.x86_64.json /usr/share/vulkan/icd.d/radeon_icd.x86_64.json.disabled and see if that has an effect.

This fixed my issue. Does this config have effect on the whole system or just how proton runs games? If it's system wide, do you have any idea if it will get reverted if I change back to hybrid graphics?

[kisak-valve]

Yes, it's a system-wide change and renaming it back to radeon_icd.x86_64.json or getting any update to the mesa-vulkan-drivers package will re-enable mesa/radv.

[legendofmiracles]

I'm not sure how to debug this, but since recently the game doesn't react to controller input; Keyboard still works fine.
This is happening with proton-experimental

[kisak-valve]

BUG: no vibration in rocket league (dualsense controller)

Issue transferred from #5575.
@Etaash-mathamsetty posted on 2022-02-16T01:51:25:

I am using proton experimental using heroic games launcher, and there's no vibration when I am playing in rocket league.
(vibration is enabled and at max strength)

[Etaash-mathamsetty]

still broken with latest update, works when the game uses xbox buttons though (proton experimental)
when wired proton uses the Xbox controller scheme (vibration works!)
on Bluetooth proton uses the PlayStation controller scheme (vibration no work)
tried a different game and vibration dosen't work on bluetooth either
am using heroic games launcher if that makes a difference

[murlakatamenka]

After recent (a few weeks ago) voice chat update the game has the issue that you can't hear how other players talk unless you change audio device once per game:

• https://www.protondb.com/app/252950#PHT_KWuT65=

when they added the voice chat function, I sometimes lose the audio and have to switch input and output settings around to make it work again, temporarily. It can be finicky, and other times I have had no issues.

• https://www.protondb.com/app/252950#Es0bC0dEEb

In game Voice call -- Every new match that starts, all sound works except I cannot hear anyone in the voice call. At the start of each match, I have to change the voice call output device to either 'default' and 'The_Name_of_The_Device' (Only set it once for the match. If it is currently on default then change to the name and vice versa.)

• same for me

Guess it's Linux / Proton specific issue.

[Etaash-mathamsetty]

dualsense controller support is still broken, it's actually kinda sad that stock wine is better at gaming lmao (they patched it in wine 7.3)

[ryliejamesthomas]

Had a problem with the last couple of updates to Proton Experimental where nameplates weren't showing, or would be blank, or some would be the colour of the opposite team, which all make it very tricky to play.

With 7.0-3 it's working as expected.

[kisak-valve]

Hello @ryliejamesthomas, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[kisak-valve]

Rocket League (252950)

Issue transferred from #6001.
@tatsujb posted on 2022-07-16T09:55:27:

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: GTX 1080
• Driver/LLVM version: nvidia 510
• Kernel version: 5.15.0-41-generic
• Link to full system information report as Gist : https://gist.github.com/tatsujb/275e7e3817dac46c7b1bce26b1e94c15
• Proton version: Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
  (I'm creating a new thread since rocket league worked fine before, this is a new issue that suddenly surfaced. I tried reporting it to Psyonics, I also made a reddit thread but it's when another said the issue went away for him when he downgraded proton version that I realized this might be due to a proton update : https://www.reddit.com/r/RocketLeague/comments/vyulfb/comment/igcagvi/?context=3 )
• that I have checked whether there are updates for my system available.

steam-252950.log

Symptoms

player Nameplates don't appear since the 12th of July 2022

as you can see neither my teamates nor myself have a nameplate and that makes players hard to see.

---

@tatsujb commented on 2022-07-16T09:58:10:

and yeah with Proton version 7.0 the nameplates are back :

[ryliejamesthomas]

Hello @ryliejamesthomas, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Sorry about that. Here's my system info: https://gist.github.com/ryliejamesthomas/109d136add6de5cb99e9cc140d4c51d9

[kisak-valve]

Rocket League mouse wheel inconsistent scroll beahviour

Issue transferred from #6007.
@Hackeitos posted on 2022-07-17T11:25:35:

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: RTX 3060 Ti
• Driver/LLVM version: nvidia-dkms 515.57-1
• Kernel version: 5.18.10-zen1-1-zen
• Link to full system information report as Gist: Steam system report
• Proton version: Proton 7.0-3

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Mouse wheel scroll behaviour seems inconsistent. Sometimes it works correctly, but sometimes input gets registered twice and sometimes it doesn't at all.

Reproduction

• Open game
• Launch freeplay (or anything to get in-game)
• Bind any action to MWHEELUP or MWHEELDOWN (in my case I have "focus on ball", but other actions present the same problem)
• Move the mouse wheel accordingly to the keybind set a few times

steam-252950.log

[alasky17]

@tatsujb

Symptoms

player Nameplates don't appear since the 12th of July 2022 as you can see neither my teamates nor myself have a nameplate and that makes players hard to see.

I did some digging and this was a dxvk regression and should already be fixed in experimental-bleeding-edge (and thus in the next experimental update). Please let me know if the next experimental release does not fix this, ty :)

[Fxzzi]

Anyone else still unable to use Anti-Aliasing in game? Any workarounds found?

[Etaash-mathamsetty]

Anyone else still unable to use Anti-Aliasing in game? Any workarounds found?

I noticed this too, the anti-aliasing dosen't seem to do anything. I would probably make a issue on the dxvk github about it though.

[doitsujin]

Can you post a screenshot of what it looks like vs what it's supposed to look like on Windows?

[kisak-valve]

Game launches but doesn't display game window (252950)

Issue transferred from #6194.
@Ahptt posted on 2022-09-28T15:52:14:

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: RTX 3080 FE
• Driver/LLVM version: nvidia 515.76-1
• Kernel version: 5.19.10-arch1-1
• Link to full system information report: https://gist.github.com/Ahptt/7cbd8454bacae2aac7c53e0e73c6a84c
• Proton version: Experimental, 7.0-4, 5.0-10, Steam Linux Runtime

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.
  steam-252950.log
  I have followed this issue and tried the remedies, still did not fix. Unable to use proton (games not loading) #6076
  I also created a post in the Arch Forums, but have not had any luck either. https://bbs.archlinux.org/viewtopic.php?id=279058

I have seen this post which mentions downgrading from the glibc 2.36 > 2.35, but I'm not looking to downgrade my packages, as it has been months since I've updated, and I have other packages on my system such as obs-studio that requires the glibc 2.36 package. (Along with this, Rocket League is not an EAC game) #6051

Symptoms

Steam shows that the game is running, but no window is displayed with the game.

[Beanow]

Also seeing the #3521 (comment) voice chat issues.

Regular audio works fine though. (Using pipewire)

It seems some XAudio2 device is exiting very early on:

[0011.06] Exit: XAudio2 Device shut down.

Below kinds of errors seem to show up for each match.

[0494.67] EOSVoice: Received full credentials from the server.
[0494.67] EOSVoice: Joining room 46190D3611EE65218B3F669003816124-0
[0494.68] PsyNet: PsyNetServiceProvider_X_1 ExecuteService Complete, Service=VoiceChat/MatchToken 
[0495.47] EOSVoice: SetPlayerMuteStatus for player [redacted] in room 46190D3611EE65218B3F669003816124-0 to False
[0495.49] Error: EOSSDK-LogAudioMixer: XAudio2 Error: Result -> 0x800401F0: UNKNOWN (line: 436)
[0495.49] DevOnline: EOSSDK-LogEOSRTC: RTCRoom [46190D3611EE65218B3F669003816124-0 bf1...37b] QueryOutputDevices failed 2147483647
[0495.49] DevOnline: EOSSDK-LogEOSRTC: RTCRoom [46190D3611EE65218B3F669003816124-0 bf1...37b] The specific output device id '{0.0.0.00000000}.{FD47D9CC-4218-4135-9CE2-0C195C87405B}' has not been found. The default device index '-1' will be used instead of it
[0495.49] Error: EOSSDK-LogAudioMixer: XAudio2 Error: Result -> 0x800401F0: UNKNOWN (line: 850)
[0495.49] Error: EOSSDK-LogEOSRTC: RTCRoom [46190D3611EE65218B3F669003816124-0 bf1...37b] unable to get output device information by index[-1]. 0xa
[0495.49] DevOnline: EOSSDK-LogEOSRTC: LibRTCCore: LibRtc::FStatisticsService::GetConferenceStats. Collecting statistics is already in progress
...
[0499.43] Error: EOSSDK-LogEOSRTC: RTCRoom [46190D3611EE65218B3F669003816124-0 bf1...37b] MercuryOutputStream_Create unable to start with those channels and sample rate
[0499.43] Error: EOSSDK-LogEOSRTC: RTCRoom [46190D3611EE65218B3F669003816124-0 bf1...37b] StartRendering failed

XAudio2 Error: Result -> 0x800401F0 mapping to CO_E_NOTINITIALIZED, the device not being initialized would make sense if it exited early on.

Finally when actually quitting the game, log entries are prefixed "exit"

[0040.32] Exit: Preparing to exit.
[0040.41] Exit: Game engine shut down
[0040.45] Exit: Windows client shut down
[0040.46] Exit: AK Audio shut down.
[0045.25] Exit: Object subsystem successfully closed.
[0046.89] Exit: Exiting.
[0046.89] Log: Log file closed, 07/10/2023 18:11:27

So it would seem this super early XAudio2 exit is unexpected.

[Beanow]

Taking a closer look at the EOSSDK, it seems to use some version of the Google WebRTC implementation: https://webrtc.googlesource.com/ which I don't think mentions xaudio. However the SDK clearly does.
https://dev.epicgames.com/docs/game-services/voice#implementing-the-voice-interface-on-windows
Specifically xaudio2_9. Which matches up with the proton logs I got.

Some other debugging info... Game logs are in:
compatdata/252950/pfx/drive_c/users/steamuser/My Documents/My Games/Rocket League/TAGame/Logs/Launch.log

You can get those same logs in your proton log with: warn+seh in WINEDEBUG.
Some ole error confirms the XAudio2 CO_E_NOTINITIALIZED error.

1868.222:0140:err:ole:com_get_class_object apartment not initialised
1868.222:0140:warn:seh:OutputDebugStringA "[0210.01] Error: EOSSDK-LogAudioMixer: XAudio2 Error: Result -> 0x800401F0: UNKNOWN (line: 436)\r\n"
1868.222:0140:warn:seh:dispatch_exception "[0210.01] Error: EOSSDK-LogAudioMixer: XAudio2 Error: Result -> 0x800401F0: UNKNOWN (line: 436)\r\n"
1868.222:0140:warn:seh:OutputDebugStringA "[0210.01] DevOnline: EOSSDK-LogEOSRTC: RTCRoom [D260D4D211EE65C53CDC2C854F78CFAD-0 bf1...37b] QueryOutputDevices failed 2147483647\r\n"
1868.222:0140:warn:seh:dispatch_exception "[0210.01] DevOnline: EOSSDK-LogEOSRTC: RTCRoom [D260D4D211EE65C53CDC2C854F78CFAD-0 bf1...37b] QueryOutputDevices failed 2147483647\r\n"
1868.222:0140:warn:seh:OutputDebugStringA "[0210.01] DevOnline: EOSSDK-LogEOSRTC: RTCRoom [D260D4D211EE65C53CDC2C854F78CFAD-0 bf1...37b] The specific output device id '{0.0.0.00000000}.{FD47D9CC-4218-4135-9CE2-0C195C87405B}' has not been found. The default device index '-1' will be used instead of it\r\n"
1868.222:0140:warn:seh:dispatch_exception "[0210.01] DevOnline: EOSSDK-LogEOSRTC: RTCRoom [D260D4D211EE65C53CDC2C854F78CFAD-0 bf1...37b] The specific output device id '{0.0.0.00000000}.{FD47D9CC-4218-4135-9CE2-0C195C87405B}' has not been found. The default device index '-1' will be used instead of it\r\n"
1868.223:0140:err:ole:com_get_class_object apartment not initialised
1868.223:0140:warn:seh:OutputDebugStringA "[0210.01] Error: EOSSDK-LogAudioMixer: XAudio2 Error: Result -> 0x800401F0: UNKNOWN (line: 850)\r\n"
1868.223:0140:warn:seh:dispatch_exception "[0210.01] Error: EOSSDK-LogAudioMixer: XAudio2 Error: Result -> 0x800401F0: UNKNOWN (line: 850)\r\n"
1868.223:0140:warn:seh:OutputDebugStringA "[0210.01] Error: EOSSDK-LogEOSRTC: RTCRoom [D260D4D211EE65C53CDC2C854F78CFAD-0 bf1...37b] unable to get output device information by index[-1]. 0xa\r\n"
1868.223:0140:warn:seh:dispatch_exception "[0210.01] Error: EOSSDK-LogEOSRTC: RTCRoom [D260D4D211EE65C53CDC2C854F78CFAD-0 bf1...37b] unable to get output device information by index[-1]. 0xa\r\n"

When changing audio device during the match it indeed resolves the issue. Though I couldn't find any noteworthy logs by the game to confirm the switch. Just the absence of errors and some logs about SaveData. Which I assume has to do with persisting the settings change.

On successfully switching device, first mmdevapi gets hammered to enumerate devices, xaudio2 gives one warning: warn:xaudio2:xaudio2_initialize Processor affinity not implemented in FAudio and then a giant wall of xaudio2 traces for all the buffers processed.

Final log settings I ended up running were:
PROTON_LOG=1 WINEDEBUG="+timestamp,warn+seh,warn+mmdevapi,warn+pulse,+loaddll,warn+xaudio2,warn+ole" %command%

🤷 that's about where I run out of expertise, hope this helps anyone with more wine experience debug.

All I have right now is a suspicion that:

• The game's device selection code differs when joining the match vs changing settings in-game.
• And the device selection on join fails with this uninitialized com apartment.

Why this fails, I'm not sure. Perhaps the xaudio2 dll drops a reference to mmdev too soon. Perhaps the game is bugged. Perhaps trying to use your "SaveData" audio settings is non-deterministic and fails to grab that particular device or fallback. Maybe the XAudio2 that "exits" 11 seconds after starting the game is the handle it tries to use to init on join? 🤷

However fortunately it should be easy to reproduce. This XAudio2 Error: Result -> 0x800401F0 can be observed 100% of the time when joining any match, regardless of other players talking or even joining the voice channel.

[al12gamer]

As a note for those playing the Steam edition of Rocket League in 2024, I've only had a flawless time running it in Proton Experimental or the latest GE-Proton build. This is likely due to attempts by EGS to kick Linux users off online.

[kisak-valve]

Multiple Controllers Detected In Rocket League

Issue transferred from #7752.
@Dex0112 posted on 2024-05-20T18:24:00:

I've reproduced this with:
Proton Experimental
Proton 9.0-1
Proton 8.0-5

When my controller gets disconnect, for any amount of time, and reconnected in Rocket League it pops up "press options to join". There is not another controller connected so this shouldn't be appearing. I've tested this with Windows and the native linux build (It is outdated and no longer supported) and in both this issue doesn't occur. The only way to fix this issue is to entirely close the game and relaunch.

In this it is explained that this is typically caused by software that is used to handle controller input. I don't have any software like this on my system as I am on a brand new Arch Install.