protonscr

Arc Raiders voice chat requires AEV_QueryHardwareSupport

protonclosed
ValveSoftware/Proton#9202 · opened 2025-11-09 by Skrappjaw · updated 2025-11-09 · 1 comments · github
1 matching comments, n / p to jump
SSkrappjaw 2025-11-09 github

Compatibility Report

  • Name of the game with compatibility issues: Arc Raiders
  • Steam AppID of the game: 1808500

System Information

  • GPU: NVIDIA GeForce RTX 2060 (primary), Intel UHD Graphics 630 (integrated)
  • Video driver version: NVIDIA 580.105.8, Mesa 25.2.6 (Intel)
  • Kernel version: Linux 6.17.7-1-default SMP PREEMPT_DYNAMIC Sun Nov 2 16:18:06 UTC 2025 (5d304cd) x86_64
  • Proton version: GE-Proton10-25 (also tested with Proton Experimental - same issue)

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

Microphone/voice chat input does not work in Arc Raiders. Audio output (playback) works perfectly, but the game cannot capture audio input for voice chat.

Detailed Symptoms:

  • Game audio output works correctly
  • Game detects and enumerates audio input devices (including virtual sinks and hardware devices)
  • Game matches input devices by GUID successfully
  • Game performs format queries on input devices
  • Game never creates input/capture streams - no source-outputs are created in PulseAudio/PipeWire
  • Voice chat in-game shows no microphone activity
  • No errors are logged - the game silently fails to create input streams

Technical Details from Logs:

  1. Audio API Used: Game uses mmdevapi.dll (Windows Multimedia Device API) for audio operations
  2. Stub Function Calls: Multiple calls to mmdevapi:AEV_QueryHardwareSupport stub - this function is not implemented in Wine
  3. Device Detection: Game successfully detects input devices:
    • VOIP_MIC Audio/Duplex sink (virtual sink, s16le 2ch 48000Hz)
    • GCS-8 Multichannel (hardware device)
    • PulseAudio Input
  4. Format Queries: Game queries device formats (pulse_create_stream Obtaining format returns 00000000) but never creates input streams
  5. Output Streams: Multiple output streams are created successfully (pulse_write messages in logs)
  6. No Input Streams: Zero source-outputs created - pactl list source-outputs returns empty

Root Cause Analysis:

The issue appears to be caused by Wine's incomplete implementation of mmdevapi.dll. According to Wine API documentation, only 9 out of 24 functions in mmdevapi.dll are implemented, with 15 functions remaining as stubs. The AEV_QueryHardwareSupport function is one of these stubs.

When the game calls AEV_QueryHardwareSupport to query hardware capabilities for input devices, the stub function cannot provide proper information about input device support. This likely causes the game to skip creating input streams, even though:

  • Devices are detected
  • Devices are matched by GUID
  • Format queries occur
  • The default source is correctly set

Audio System:

  • Audio Server: PipeWire 1.5.81 (with PulseAudio compatibility layer)
  • Default Source: VOIP_MIC (virtual sink, s16le 2ch 48000Hz)
  • Default Sink: SYSTEM (virtual sink)
  • Tested with both virtual sinks and hardware devices - same behavior

Launch Options Used:

PROTON_LOG=1 WINEDEBUG=+pulse,+timestamp %command%

Log File:

Attached: steam-1808500.log (contains full Proton log with PulseAudio debugging enabled)

Additional Notes:

  • Issue occurs with both GE-Proton10-25 and Proton Experimental
  • Issue occurs with both virtual PipeWire sinks and hardware audio devices
  • Audio output works perfectly - only input/capture is affected
  • Game is playable otherwise, but voice chat functionality is completely non-functional
  • No workarounds found - appears to be a fundamental limitation in Wine's mmdevapi.dll implementation

steam-1808500.log

Kkisak-valve maintainer 2025-11-09 github

Hello @Skrappjaw, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/9164#issuecomment-3508701527.

Proton versions

Launch options

Upstream links

DLLs