ARC Raiders (1808500)

[EmersonBiggons]

Compatibility Report

• Arc Raiders
• Steam AppID of the game: 1808500

System Information

• GPU: AMD RX 7800 XT
• CPU: AMD R7 5800x
• Video driver version: Mesa 25.2.5
• Kernel version: 6.17.5-200.nobara
• Gist
• Proton version: Proton Experimental Bleeding Edge (And Proton GE Latest)

I confirm:

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

Symptoms

The game crashes 100% of the time with and "out of video memory" error.

Full error Log:

LowLevelFatalError [File:.\Runtime/RenderCore/Private/RenderingThread.cpp] [Line: 952] 
Rendering thread exception:
LowLevelFatalError [File:.\Runtime/D3D12RHI/Private/D3D12Util.cpp] [Line: 1046] 
Out of video memory trying to allocate a rendering resource


0x00000001421c3c8c PioneerGame.exe!UnknownFunction []
0x00000001421724f8 PioneerGame.exe!UnknownFunction []
0x000000014215f5bf PioneerGame.exe!UnknownFunction []
0x00000001421a7b73 PioneerGame.exe!UnknownFunction []
0x00000001421b5184 PioneerGame.exe!UnknownFunction []
0x00000001421a2137 PioneerGame.exe!UnknownFunction []
0x00000001423bb74c PioneerGame.exe!UnknownFunction []
0x0000000142389828 PioneerGame.exe!UnknownFunction []
0x000000014237524e PioneerGame.exe!UnknownFunction []
0x000000014238b1f6 PioneerGame.exe!UnknownFunction []
0x0000000141e80630 PioneerGame.exe!UnknownFunction []
0x0000000141eb0851 PioneerGame.exe!UnknownFunction []
0x0000000140048864 PioneerGame.exe!UnknownFunction []
0x0000000140057ffd PioneerGame.exe!UnknownFunction []
0x00000001423603fb PioneerGame.exe!UnknownFunction []
0x0000000142372fd8 PioneerGame.exe!UnknownFunction []
0x000000014024ed45 PioneerGame.exe!UnknownFunction []
0x00000001402542b6 PioneerGame.exe!UnknownFunction []
0x00006fffffec0c59 kernel32.dll!UnknownFunction []
0x0000000140014d31 PioneerGame.exe!UnknownFunction []

Reproduction

Opening the game after fresh install. Regardless of what I do, it always has the same error.

[thiago-negri]

Original issue for Arc Raiders play test: https://github.com/ValveSoftware/Proton/issues/8636

[thiago-negri]

Constant crashes after a few minutes. Can't play. Void Linux. Tried Hotfix, Experimental, and Experimental Bleeding-Edge. Tried Steam overlay enabled/disabled.

# /etc/sysctl.conf
fs.file-max = 524288
vm.max_map_count = 1048576

$ ls /var/service/
NetworkManager  agetty-tty1  agetty-tty2  agetty-tty3  agetty-tty4  agetty-tty5  agetty-tty6  alsa  bluetoothd  dbus  elogind  libvirtd  nanoklogd  polkitd  socklog-unix  udevd  virtlockd  virtlogd

Running PipeWire at user level, Herbstluftwm (Xorg).

steam-log.tar.gz

Steam Runtime System Information

[lsahnicne]

https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3470699453 - reposting from play test issue thread as the issue persists on release version

Pop!_OS 22.04 LTS Proton Experimental & Hotfix

The game crashes on launch with the following error: Wine C++ Runtime Library Expression: "!status && "vkCreateComputePipelines""

steam-1808500.zip

https://gist.github.com/lsahnicne/dd7bc5d20a68d9aa918cca6483344287

[HansKristian-Work]

I cannot reproduce this on 25.1.5 driver or main, but I did find something a little suspect which might explain your crash. Filed:

https://gitlab.freedesktop.org/mesa/mesa/-/issues/14225

[astrayblackcat]

This is quite hard to provide a decent log for due to the random nature of it but I have attached one that is quite large due to the amount of attempts it took to get a crash. (2GB when uncompressed)

https://drive.google.com/file/d/1dj_wXhw_Ne8JS-tRmjgO2kFU7tIX8Ah4/view?usp=sharing Provided in Google Drive due to it being over the Github file size limit even when compressed.

Essentially, sometimes when loading into a match with the game window out of focus, it will randomly completely freeze and require the game to be restarted. I've noted several reports on ProtonDB with both Nvidia and AMD reporting the same, though I'm personally on Mesa 25.2.5 and an RX9070.

For clarity, this is with FSR4 running, but it also occurs without any launch options etc.

[gbip]

Replying to https://github.com/ValveSoftware/Proton/issues/9164#issuecomment-3474124131

I do have the same issue, crash when the game window is out of focus.

[simifor]

@astrayblackcat @gbip while I haven't repro'd on my end, I found tha thte game has two idle settings in the graphics settings, have you tried if turning them off prevents the issue from manifesting?

[astrayblackcat]

Replying to https://github.com/ValveSoftware/Proton/issues/9164#issuecomment-3478222291

I have tried, makes no difference unfortunately.

[MaysonYancey]

@astrayblackcat

I've encountered similar issues running ARC on arch linux, proton 10.0.2 and proton experimental.

The crashes typically occur right after we start the match, during the cut scene. There was one time that I fully loaded into the match, but before I was able to move the character it crashed (froze, no pop up error messages).

Has anyone else seen this issue or had any luck mitigating it?

[gbip]

@astrayblackcat @gbip while I haven't repro'd on my end, I found tha thte game has two idle settings in the graphics settings, have you tried if turning them off prevents the issue from manifesting?

I will try this, thanks.

[pollux78]

Just had a crash when redeeming some coins on the earnable store page 5, file is big so it is on mega.

RX 6700 10GB, Ryzen 7600, Cachyos, Mesa 25.2.6, Kernel 6.17.7, Proton Experimental

https://mega.nz/file/sBAEVJRb#EGJYcjWDtpPCJ4u8wuLQ7uRdozqHjqJxqV7weo3AytI

[rcv11x]

The game is great and I'm enjoying it. I've played for several hours, but it's true that there have been some problems.

When I played for the first 3 or 4 hours, everything was fine with the following flags: game-performance mangohud %command%

Then I was curious to try the game with the flags PROTON_ENABLE_WAYLAND=1 PROTON_USE_NTSYNC=1 + the previous ones, and what happens here is that the game works quite well, but if you are looking for a game and you are outside the game, it will never load the game, and if you are inside the game focus and it puts you in the game, the gameplay works fine, but the game cursor remains active on the screen.

This problem is caused by the variable PROTON_ENABLE_WAYLAND=1. so I removed these last two variables and the game worked fine as usual, but then it crashed for the first time. I don't know if it was a coincidence or completely random. I was in focus when I loaded the game, and once inside, I moved a few metres and the game crashed. Unfortunately, I don't have a screenshot to send, but if it happens again, I'll send it. I hope these issues get fixed, as I don't know if it's a vkd3d-proton issue or a Mesa issue.

The performance is quite good, but I think it's a little better on Windows. With everything set to Ultra, TSR 100% at 1440p with my rx 9070 xt, I got an average of 110-120fps, and on Linux a little less, around 100~, sometimes dropping to 90 and something.

mi setup specs: CachyOS, KDE plasma 6.5.1, kernel 6.17.6, ryzen 7 5800x3d, rx 9070 xt, mesa 25.2.6 and proton experimental / proton-cachyos-native

[simifor]

Proton logs compress well, so always try compressing them before uploading them, for convenience.

There are probably multiple factors leading to issues in this game, it's important to try and recall as many details as you can from the run where the issue occurred. As well as game settings, and device information.

The game has settings for idle energy settings that might cause some issues when out of focus in some setups.

For now, I can say that when using TSR the game can crash when switching graphics quality, at least on amd. This crash, when it happens, is instant and doesn't bring up the crash handler. It's possible that the game may also crash in other scenarios while using TSR so it's something worth taking into account.

Update:

Nvapi doesn't load successfully on amd, and during the run of the game the dll gets loaded and unloaded many times. This can be avoided by either disabling, or force enabling, nvapi through PROTON_DISABLE_NVAPI=1 %command% or PROTON_FORCE_NVAPI=1 %command% respectively in the game's launch parameter. Thus far, this seems to prevent the TSR crash that may happen when cycling through graphics preset.

[p5k369]

This issue is also still present: https://github.com/ValveSoftware/Proton/issues/8636#issuecomment-3420008982 After 30 minutes arc raiders crashes no matter where you are in the game, could be main menu, in game or in cutscene. One reason for that might be that some distros (like gentoo) have their vm.max_map_count at 65530. Changing that to 1048576 gives me a cttc (constant time till crash) of exactly 1 hour and 50 minutes. Changing it to 2147483642 does not increase that, instead I now only get a cttc of exactly 1 hour and 30 minutes.

Up until that crashing point the game runs like a charm. Great performance, feels very well optimized. It does not matter which proton version I'm on (including betas like bleeding edge), it's always the same. Also EXPO settings does not seem to matter, graphic settings also does not seem to matter. I switched to single monitor, no change. I'm on 580.95.05 with rtx 4070 ti super.

edit: Figured it out. Also the hard file descriptor limit has to be set. It is quite low on gentoo by default. So I added * hard nofile 524288 to /etc/security/limits.conf. No more crashes so far.

[pollux78]

Replying to https://github.com/ValveSoftware/Proton/issues/9164#issuecomment-3481332753

The wine wayland cursor problem has been resolved in plasma 6.5.2, it was a regression with plasma 6.5

https://bugs.kde.org/show_bug.cgi?id=511075 https://invent.kde.org/plasma/kwin/-/merge_requests/8326

[Blisto91]

A crash related to the presence of nvapi on non Nvidia systems have now been worked around in Proton Bleeding Edge

[simifor]

I've managed to crash once, a few seconds after joining a match. The game gave me an option to reconnect the match after starting the game again, which made it crash again. Unfortunately, when starting the game with extra debugging options it didn't crash, and in other matches I couldn't crash even when going to the same zone.

For those who have crashed starting a match, have you been able to rejoin the match? And did it crash again after doing so?

[pollux78]

Game appears with a newer driver window warning when launching on latest update on amd hardware atleast on 2 different computers running nobara and cachyos, one running experimental and one running experimental(bleeding edge)

[kisak-valve]

That dialog doesn't read like an outdated warning. Instead, it's saying the claimed driver version is newer than a known working point release.

[pollux78]

That dialog doesn't read like an outdated warning. Instead, it's saying the claimed driver version is newer than a known working point release.

yes sorry, i wasn't reading it properly for some reason, thanks!

[astrayblackcat]

The driver version popup should still likely be worked around (or potentially fixed by the devs? Embark is fairly attentive to Steam Deck/Proton compatibility) as it will likely always show due to it being read incorrectly.

As well as, of course, being completely bogus on Linux as it's referring to known issues with the Windows AMD drivers.

[simifor]

While I haven't gotten the game to hang again on dam battlegrounds, I could reliably get it to hang my 9060 xt by spending a few minutes in "buried city". For those affected by the same there are currently two options, the easy thing to do is to disable ray tracing, or if you know how to compile mesa yourself, you can add the merge request number 38290.

[kisak-valve]

Arc Raiders voice chat requires AEV_QueryHardwareSupport

Issue transferred from https://github.com/ValveSoftware/Proton/issues/9202. @Skrappjaw posted on 2025-11-09T19:09:12:

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

[simonvanderveldt]

The above report sounds very definitive about it not working, but voice chat is working fine for me. Others can hear me just fine, both with regular as well as with Raider voice. I'm using Proton experimental, no launch options.

[Skrappjaw]

The above reports sounds very definitive about it not working, but voice chat is working fine for me, others can hear me just fine, bot with regular as well as with Raider voice. I'm using Proton experimental, no launch options.

Can you post your system info and what audio stack you have? pulse, pipewire, alsa, audio card ect? Distro? Im on OpenSuse pipewire and I have a USB audio interface.

[rcv11x]

Another error I want to report is that if you run the game with the variable: PROTON_ENABLE_WAYLAND=1 when you are in the game and press 2 to change weapons, it doesn't work for some reason. The 1 key, which is for changing the main weapon, does work. and if I change the weapon with the mouse wheel, it also works, but it's annoying that the 2 key doesn't work. The same thing happens with the q key, which is for selecting the inventory to browse. Sometimes it works and sometimes it doesn't. This doesn't happen if I run it normally without that variable.

pd: I have tested it with ProtonGE 25 and proton-cachyos.

[simonvanderveldt]

@Skrappjaw

Can you post your system info and what audio stack you have? pulse, pipewire, alsa, audio card ect? Distro? Im on OpenSuse pipewire and I have a USB audio interface.

It's nothing special. Gentoo, GNOME on OpenRC using pipewire 1.4.7 via wireplumber 0.5.10, no pulseaudio installed. Sound is onboard. No launch options, just Proton Experimental.

Screenshot of the voip part of the audio settings

pactl list-sources also lists it, but only during a raid, not when in Speranza/the menus.

pactl list source-outputs
Source Output #212
	Driver: PipeWire
	Owner Module: n/a
	Client: 201
	Source: 68
	Sample Specification: s16le 2ch 48000Hz
	Channel Map: front-left,front-right
	Format: pcm, format.sample_format = "\"s16le\""  format.rate = "48000"  format.channels = "2"  format.channel_map = "\"front-left,front-right\""
	Corked: no
	Mute: no
	Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	Buffer Latency: 0 usec
	Source Latency: 0 usec
	Resample method: PipeWire
	Properties:
		client.api = "pipewire-pulse"
		pulse.server.type = "unix"
		application.name = "ARC Raiders"
		application.process.id = "7265"
		application.process.user = "simon"
		application.process.host = "simon-desktop"
		application.process.binary = "wine64-preloader"
		application.language = "en_US.UTF-8"
		window.x11.display = ":0"
		application.process.machine_id = "<machine id>"
		media.name = "audio stream #3"
		pulse.corked = "false"
		node.rate = "1/48000"
		node.latency = "480/48000"
		stream.is-live = "true"
		node.name = "ARC Raiders"
		node.want-driver = "true"
		node.autoconnect = "true"
		media.class = "Stream/Input/Audio"
		port.group = "stream.0"
		adapt.follower.spa-node = ""
		object.register = "false"
		factory.id = "7"
		clock.quantum-limit = "8192"
		node.loop.name = "data-loop.0"
		library.name = "audioconvert/libspa-audioconvert"
		client.id = "96"
		object.id = "107"
		object.serial = "212"
		pulse.attr.maxlength = "384000"
		pulse.attr.fragsize = "1920"
		node.driver-id = "46"
		module-stream-restore.id = "source-output-by-application-name:ARC Raiders"

Maybe the 48kHz is to blame?

[mvykol]

Not sure if this should go here or somewhere else, but is anyone else having issues with Steam game recording working with this game? Works in other games but doesn't seem to be doing anything in ARC Raiders. I'm using Proton Experimental

OS: Arch Linux KERNEL: 6.17.7-arch1-1 CPU: 12th Gen Intel Core i7-12700K GPU: NVIDIA GeForce RTX 4080 SUPER GPU DRIVER: NVIDIA 580.95.05 RAM: 64 GB

[pollux78]

Another error I want to report is that if you run the game with the variable: PROTON_ENABLE_WAYLAND=1 when you are in the game and press 2 to change weapons, it doesn't work for some reason. The 1 key, which is for changing the main weapon, does work. and if I change the weapon with the mouse wheel, it also works, but it's annoying that the 2 key doesn't work. The same thing happens with the q key, which is for selecting the inventory to browse. Sometimes it works and sometimes it doesn't. This doesn't happen if I run it normally without that variable.

Valve does not have wine Wayland enabled on default proton, please report wine Wayland problems on proton-em github instead as that's where all of the patches come from with the custom proton runners

https://github.com/Etaash-mathamsetty/Proton/issues

[rcv11x]

Replying to https://github.com/ValveSoftware/Proton/issues/9164#issuecomment-3514926506

I have tried it with ProtonGE 25 and proton-cachyos and the same thing happens. I do not know why those keys do not work properly.