deleted as not relevant to the report, apologies.
The recent iterations of Proton, 4.11-11 and 4.11-10 (maybe 4.11-9? unsure) have lead to a lot of Rust crashing but not actually killing the process. I've had to forcefully kill all STEAM processes and all Rust processes, then relaunch, multiple times, just to be able to play and connect.
Furthermore, the 4.11-11 and 4.11-10 branch have drastically reduced my performance vs 4.11-9, as I have a lot of frame stuttering and frame rate drop now. I wish I could enable the 4.11-9 beta branch again just to go back to reliable performance, but that was recently disabled with 4.11-11's release.
4.11-10 and 4.11-11 should have had their own version bump, I dunno... 4.12 maybe? So those of us could use either 4.11 or the new DXVK/etc improvements in the "4.12" so to say.
As of today's Rust update, Proton is no longer able to be used to play this game. It gets stuck on the EAC splash screen. Before this update, it would proceed past the EAC splash screen and the game could still be played as long as you connected to a server which does not have EAC enabled. That is no longer the case.
Yeah, it only presents an Exit button for me, and goes nowhere further. Unsure if this intentional by the Jackass that is Gary, or if this is something they're prepared to fix (they being Face Punch).
Was really looking forward to playing wipe day today, but nope! :(
Good thing us Linux gamers helped bank-roll this game years ago and now they just don't care.
Anyways, the latest issue seems to be resolved after another game update. Another thing worth noting is that the game seems to cleanly exit without problems now.
Seems like rust broke on the latest update (boat update)
Can confirm when running steam under wine via Lutris, Rust still works
and not only that it seems to fix a crash that used to happen
when pushing the "play game" buttion which shows the server list
it also fixes rendering issues like epilepsy inducing water, and the X marks being invisable for trees and ores
I know it is off-topic but lutris with "regular" wine that you are talking about is literally installing a full windows-version steam? Will it work out of the box or some workarounds are needed
Shall it be installed through this script https://lutris.net/games/rust/ ?
@alex9099 i just did add game (ID: 252490) on the "Wine Steam" runner after installing it (with -no-browser)
I don't actually know if that script installs on the Steam or Wine Steam runner
and as far as i can tell the Steam runner just calls steam to run the game normaly
Rust (3.9.2020 Update)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4175.
@TheBlackPenguin posted on 2020-09-05T23:46:59:
[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.
The game worked fine with Proton, but since the latest Rust update, the game crashes while loading. The error.log of the game report an Access Violation by the steam_api64.dll (error.log). The game now only works with a regular wine installation of steam.
Launch Rust with Proton
Hello @TheBlackPenguin, err:steamclient:create_win_interface Don't recognize interface name: SteamUser021 looks like the line of interest from the log. Related: #3886
5.13 seems to crash when joining a server instead of displaying "is Steam running" error (so it gets further).
Proton logs are humongous, how did you get one that was 2.5MB? Mine is 38...
EDIT: Direct link to full log here.
Possibly relevant: https://github.com/ValveSoftware/Proton/issues/4289#issuecomment-720020589
EDIT: Not relevant to the crash, but still seems to make a huge difference in framerate in the menu, so probably still a good idea for 5.13 users.
EDIT2: I've seen many people talking about editing an entrypoint to remove soldier, but I didn't find it last time I checked. If you think it could make a difference, could you explain how to do it kisak (or someone else in the know)? Thanks in advance :-)
Headsup:
Compatibility Report
Name of the game with compatibility issues: RUST
Steam AppID of the game: 252490
System Information
CPU: AMD Ryzen 3800XT
GPU: VEGA64
Driver/LLVM version: MESA 20.2.2
Kernel version: 5.9.8-zen1-1-zen
Link to full system information report as Gist: https://gist.github.com/plasticbomb1986/a68256a0ebf6d714fb7a98999cc2d002
Proton version: 5.13.2
Currently the game with proton 5.13-2 is pretty much OOB, except it cant connect to servers with EAC turned on. It does not crash at the server search window, neither to pushing the play button ingame, unlike previously did.
While i was playing for an hour now, it generated an about 100 MB proton log, filled with the same issue, will attach it later.
Does anyone know if we can do what they did to fix EAC for squad ? I'm pretty sure the EAC file mentioned is just for that game so I don't really want to try it. Could result in a ban idk. I did try https://github.com/imaami/eac-tools but it didn't load it even when I made it so it cant delete it but only read it.
Ex https://github.com/ValveSoftware/Proton/issues/938#issuecomment-655405271
It seems to just have an issue when downloading the EAC file
From Loader.log
[2021.01.08-10.46.57] [Connection] Connect result: No error (0) Response Code: 403 Destination IP: 13.226.18.100
[2021.01.08-10.46.57] [HTTP Error Response] HTTP Response Code: 403 Curl Code: 0.
[2021.01.08-10.46.57] Falling back to a secondary CDN path.
[2021.01.08-10.46.57] [Connection] Connecting to URL: https://download-alt.easyanticheat.net/api/v1/games/12/client/wine64/download/?uuid=[REDACTED]
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] Download Progress: 0%.
[2021.01.08-10.46.57] [Connection] Connect result: SSL connect error (35) Response Code: 0 Destination IP: 172.67.156.223
[2021.01.08-10.46.57] Connection to the Content Distribution Network failed! Curl Code: 35.
[2021.01.08-10.46.57] [EAC Callback] Code 901. Message: 'Connection to the Content Distribution Network failed! Curl Code: 35.'.
I've posted "Load.... & Crash" (Currently pending) on protondb. Just want to point out that it's appear the same issue as described by https://www.protondb.com/users/2044252607 & https://www.protondb.com/users/1749720343 .
So sad for a game that i remindber buyed as native linux. Hope to play this game again this year. <3
Does anyone know if we can do what they did to fix EAC for squad ? I'm pretty sure the EAC file mentioned is just for that game so I don't really want to try it. Could result in a ban idk. I did try https://github.com/imaami/eac-tools but it didn't load it even when I made it so it cant delete it but only read it.
Ex [#938 (comment)](https://github.com/ValveSoftware/Proton/issues/938#issuecomment-655405271)
It seems to just have an issue when downloading the EAC file
I think its that the file just doesn't exist. if you switch out the 12 in that link it gives with 55 (Squad's ID) and paste it in your browser, it downloads.
It actually download the eac file using eac tools which is strange. It seems like the game devs would have to add support for it like squad did unless you can get the full windows version to run some how.
But like about rust why tf does it have macos support and not linux support. Mac sux. Idk why they would rid the native linux version either. Most game engines allow you to develop for multiple os's easily. But the least they can do is add support for proton all they need to fix is the eac like squad did. But yeah the error code is a missing file so all they would have to do is add it then it would work. Full EAC and everything. EAC is crap anyways 2bh. Like most cheats could be blocked with a hardened server side that doesn't allow you to fly or do anything fishy and maybe just a server side anti cheat instead of an invasive client side one. But to be fair to the developers this is pretty hard to do unless you were designing it like that from the ground up because they would have to go through the whole server side code. People still bypass EAC either way. Best way is a hardened server side with a server side AI based anti cheat to detect aimbot and ESP. Its really hard to stop all cheaters its a cat and mouse game really.
A little personal rant about Linux:
The design of Linux is better than windows all its missing is a user base like windows has and that will give it more application support because it would make more sense for developers. Linux dominates the server market because it has both. Linux doesn't have to deal with crappy windows updates. Programs can be all updated at the same time by your package manager but on windows you have to update them all separately. On Linux you don't have to wait for the updates when you boot the computer all you need to reboot for is to load a new kernel which doesn't take time. The Linux network stack is way better than windows networking. Can windows filter millions of packets per second and be used on routers viably ? Linux also has more robust options for file systems too. It would also be benificial to game streaming providers as linux is more scalable than having to spin up a bunch of windows vms. There is also too many more benifits that I cant mention. All we need is a main stream Linux distro with a user base and application support. That doesn't require using the terminal at all for the noobs which would give it the application support for power users that like using the terminal and the beauty of Linux. Macos is the closest example of this(as its based off of Unix too and has good application support. Still not a Linux distro though) but we want this to be more popular than windows. I also think opensource and privacy should be a law and the default. No more of these big companies monitoring you like lab rats and brain washing you with propaganda and targeted ads. I hate people sometimes 2bh. This would cause the end of having to use wine/proton and other hacky things too.
But that file has to be corrupt or something. The one I got from eac tools is only 152kb and the one for squad is 4mb
The issue was closed instantly be Garry Newman I contacted them too but they simply closed the ticket there too..
It actually download the eac file using eac tools which is strange. It seems like the game devs would have to add support for it like squad did unless you can get the full windows version to run some how.
You are sure? Mine doesn't download anything.
Yeah it did for me which is strange. But like I think the devs would have to enable it. They probably have the wine64 version of EAC disabled. Idk I never made a game or used EAC before. It would probably just take enabling it because EAC is like a simple drop in anti cheat for game developers.
@jatin-cbs Where did you contact them before ? Did you use the submit a request thing on their website ?
@Synkstar Yes I used submit request on their website and also on Steam Discussions..
What about this: https://rust.nolt.io/ post it as like a public suggestion and get a bunch of linux users to flock to it. Well we need to get a voice of linux users.
Do you guys really think Gary is going to change his mind about supporting Linux? If he was going to, he would have a year or two ago. Nowhere near enough people read this thread, let alone will post there, to convince him to change his mind.
I'd love to be wrong, but you need to actually pay attention to his behaviour in the year-ish lead up time before they removed Linux support. He was very very toxic to the Linux community, blaming them/us for things that was clearly his fault (not even testing code, for example).
@BloodyIron idk its worth a try but that is very true. The only difference with this is im pretty sure the wine64 version of eac would just need to be enabled which would take like 30 secs or less. It is definitely there as EAC responds with a 403 which means forbidden. Correct me if im wrong.... The rust server does support linux but it uses mono
It would be a glorious day if we could convince Gary to change his mind. I would rather play Rust natively. Please, prove me wrong if you're reading this! Don't let me dissuade anyone from getting passionate about this and changing the world. I'm just trying to remind us what has happened, and it's actually more than I've said.
Rust was native on Linux (as a client) for the majority of the game's history. I for one was exceptionally frustrated to hear it lose native support on Linux, as I've had plenty of fun in the year+ before that happened (apart from the roll-out of Vulkan, which broke the game on Linux for 3 months for 100% of Linux gamers).
I'm not so sure if enabling EAC64 is the easy solution here, but if you want to try to convince Gary to change that, maybe not use the word Linux when engaging him/Facepunch?
One thing I would like to add is the people involved with getting EAC (Windows version) and other such things working through Wine, that effort is still being worked on. I do not represent them, just to be clear, but that is an avenue that could address this (when, maybe this year).
Either way, if Rust was playable on Linux again, on EAC servers, without any fuss, muss, or whatever. I'd play!
Rust is working again on NON EAC Servers with latest Proton out of the box. If you want to play with other linux users there is a friendly server with a good active admin, you can connect via the F1 console with: connect play.deadlock.com:1333 (around 40 players play here lately).
Honestly i don't have any hope in Garry and Facepunch, they will never do anything for Linux: https://www.reddit.com/r/linux_gaming/comments/43263f/garry_newman_regrets_supporting_linux_if_i_could/.
And don't have any hope in EAC too that is now owned by Epic Games so supporting Proton means supporting Steam/Valve and they don't want that.
My only hope and trust is in Valve, that i think should improve/make a new Valve Anti-Cheat that could be a new better alternative to EAC and friends.
EAC on Rust
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4624.
@davidaamesjr posted on 2021-02-17T02:15:00:
Just curious if there are any resolutions on the EAC not working for Rust on Proton.. requested a refund and I'm only played 3 hours on a windows box but cannot connect to servers on Linux.. main PC is linux, deleted windows anyway now.,, they are denying my refund request over and over again and wont forward me to a supervisor or manager or anything... really either want my money back or for it to work.. lol. Thanks.
<Blank compatibility report template omitted>
Rust seems to blow up with the latest update.
See attached PROTON_LOG=1 session log.
Proton 6.3-4 DirectX 11 won't install for Rust
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4887.
@EscapedAI posted on 2021-06-06T14:28:18:
Vulkan and 32-bit is enabled, I used this guide for my drivers, which is more detailed than your guide.
When running Rust, it will either not try or will get stuck half way with installing DirectX 11

I am not sure how to reproduce this. It seems to possibly be specific to my system.
Rust worked on Proton 5.13-6 three months ago but for Linux gamers only 6.3-4 works now and that won't install Dx11 for me.
I have:
Hello @EscapedAI, just to check, does it get further if you try to run the game first with Proton 5.13, let it finish the first time setup, then set it to use Proton 6.3 after that completes or does the DirectX redist installer stall infinitely with Proton 5.13 as well?
Proton:
Bootstrap Tier0lsteamclient.dll caused an Access Violation (0xc0000005) in module lsteamclient.dll at 0033:8d3ab65c.
(I have also tried PROTON_USE_WINED3D=1 %command% without success.)





The recent update fixed my problems. Thank you!
@EscapedAI are you able to play on EAC servers? o.O!?!
@EscapedAI are you able to play on EAC servers? o.O!?!
No, there is a community one and I might start one without EAC for my friends.
Ubuntu 21.10 with Proton 6.3-6: Rust and EAC start OK without any need for tweaking, but I can't join official servers due to EAC auth timeout.
Game needs WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command% with experimental for videos to not be broken/tinted pink
Nice I just installed this game again today to check for EAC support (no support yet) and was wondering what the problem was :+1:
Synchronicity.
Thanks.
Game needs
WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%with experimental for videos to not be broken/tinted pink
Confirmed, this fixes the main menu videos for me
would be nice for facepunch to respond to this issue..
You mean here? Also to which issue?
@Zorrototo uh, well, anywhere really, and specifically supporting EAC under proton.
I think Facepunch believes it's EAC who are supposed to fix their code running in the proton emulation.
Here's an update tho : https://twitter.com/garrynewman/status/1531235676653510657
Proton games won't launch
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/9808.
@waaynee posted on 2023-07-07T08:54:13:
It seems like the new update broke launching proton games. If you start a game it says 'launching' as shown in the screenshot attached, but it will hang there. Already deleted compatdata as suggested in some reddit threads and tried any newer Proton version including the normal ones an GE.
Hello @waaynee, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
Hello @kisak-valve, thank you for your answer. I uploaded the gist here. Also, I added PROTON_LOG=1 %command% to the launch options but unfortunately there is no steam-252490.log file generated in my home directory. I guess because the game won't launch at all.
Since no log at all is generated, that hints that something went wrong before Proton had a chance to run at all. Skimming over your extended diagnostics information, I suspect you're seeing a symptom of #6809.
Unset MANGOHUD=1 in the environment you run Steam from and see if that has an effect, otherwise, completely close Steam, then run steam from a terminal and check if there's a hint in the terminal spew when you tell Steam to start the game with Proton.
I have a log file of Rust using PROTON_LOG=1 %command% used, I also had to add PROTON_LOG_DIR to get it to post a log file. The following contents of the log file can be found on this Gist.
https://gist.github.com/alkaris2/80892dd4e6800c9d40e79e2ea243690e
I also have an additional log file created by Rust that is makes when the game is running. The issue points to a bundle file being the source of the problems as of a recent update that was pushed for the game as of 7 July 2023 – 15:33:15 UTC, so it's probably not Proton related specifically, as there are reports of this same issue happening for some of those running this game on Windows 10/11, and will require FacePunch Devs to address the issue that their bundle asset is causing.
Skimming over your Proton log, these lines caught my eye:
err:steamclient:create_win_interface Don't recognize interface name: SteamUser023
err:steamclient:create_win_interface Don't recognize interface name: STEAMUGC_INTERFACE_VERSION017
These are provided by Steamworks 1.57 (https://github.com/ValveSoftware/Proton/commit/a33bbf115c3de5cc0ec6dda7305367968720e6bb) which is in Proton 8.0-3 (currently a release candidate) and Proton Experimental.
The problem was MangoHUD. Removing solved the issue. Thank you for your help and your time!
Any update on EAC support?
The game is still unplayable in its current state since all legitimate servers use EAC, tested today, on latest proton experimental, and Proton EasyAntiCheat Runtime installed, can't join servers due to EAC failing.
Can anything be done? I see other EAC games working with proton now.
Has communication/cooperation with Facepunch stalled? (referring to this statement)
Is there anything we/the community can do?
EAC is just not gonna happen. That's all. https://areweanticheatyet.com/?search=rust&sortOrder=&sortBy=
I think you can play it on virtual machine though, but maybe ask confirmation from EAC themselves they will give you the greenlight if they support the game on a Windows VM (but pretty sure they are OK with that).
Filter server by anti cheat status in Steam, you'll get a dozen where you can play, one being dedicated to SteamDeck from its naming.
EAC is just not gonna happen. That's all. https://areweanticheatyet.com/?search=rust&sortOrder=&sortBy=
I think you can play it on virtual machine though, but maybe ask confirmation from EAC themselves they will give you the greenlight if they support the game on a Windows VM (but pretty sure they are OK with that).
Filter server by anti cheat status in Steam, you'll get a dozen where you can play, one being dedicated to SteamDeck from its naming.
Dang didn't even know this would work with the Steam Server search! Thanks for that.
As for EAC for Rust through Proton, FacePunch need to tick that box. All they need to do is about a few minutes of work, and that's it. They don't even need to go through the Steam Deck Verified Program just to make that happen.
But yeah, don't let jerks like Gary (FacePunch) get in your way. Play on one of those EAC-disabled servers.
Rust without EAC is like skydiving without parachutes. Good luck.
Rust - EAC “NullClient” error (RX 6600, Proton 9.0 Beta, Ubuntu 24.04)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8653.
@blatbikes posted on 2025-05-03T18:35:39:
Its 4:03 am im going to sleep and will prob forget to look at this so idk im going crazy and got chatgpt to help me ahahahahahahahahah do i finish on an a or h?
Compatibility Report
Name of the game with compatibility issues: Rust
Steam AppID of the game: 252490
System Information
GPU: AMD RX 6600
Video driver version: Mesa 24.x (RADV)
Kernel version: 6.8 (Ubuntu 24.04)
Link to full system information report as [Gist](https://gist.github.com/): (will add shortly)
Proton version: Proton 9.0 (Beta) (also tested Proton Experimental and GE — GE fails entirely, Experimental crashes)
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
Rust launches fine and gets to the main menu. When I try to join any server, I get this message:
Disconnected: EAC: anti-cheat client protection not active (NullClient)
The EAC bear logo appears briefly but seems to crash or hang before disappearing.
EAC logs show successful install, but something is clearly not hooking or staying active.
Steam is installed via the .deb package from Valve’s site (not Flatpak).
Tried clean prefix, full EAC install, correct launch options (PROTON_EAC_RUNTIME=1), and environment variables.
Still no success. Proton GE is outright incompatible, and Proton Experimental crashes Rust.
Proton 9.0 Beta loads into the menu but EAC never activates.
It’s 4AM and I just want to play Rust and sleep — please help! 🙏
Reproduction
Launch Rust using Proton 9.0 (Beta)
Make sure EAC is installed (done via EasyAntiCheat_Setup.exe inside the prefix)
Use launch options like:
PROTON_EAC_RUNTIME=1 %command%
Game launches to main menu
Attempt to join any server
Get kicked with NullClient error
Proton-10.0-1Beta-Launch_options
Proton-10.0-1Beta-No_launch_options
Proton-Experimental-Launch_options
Proton-Experimental-No_launch_options
Proton-Hotfix-Launch_options
Proton-Hotfix-No_launch_options
When opening the game with "Proton Experimental", "Proton Hotfix" and "Proton 10.0-1(Beta)" the game launches properly but when clicking "Play Game" on the main menu or connecting to a server (through console or with +connect "serverip") a windows named "Rust - Unity 2022.3.41f1_0f988161febf" pops up, loads for a bit and the game closes. Every other option is clickable and can be interacted with (see "NEWS, INVENTORY, ITEM STORE, WORKSHOP, ETC"). The game run perfectly normal under proton-GE 9-27 and Proton 9.0-4.
This error occurs with and without the following launch options:
PROTON_LOG=1 %command%
PULSE_LATENCY_MSEC=60 gamemoderun %command% -force-d3d11-no-singlethreaded
The game run perfectly normal under proton-GE 9-27 and Proton 9.0-4 with and without the following launch options:
PULSE_LATENCY_MSEC=60 gamemoderun %command% -force-d3d11-no-singlethreaded
Had to downgrade Mesa from 25.1.0-dev (Kisak source) to 25.0.3 (Ubuntu 25.04 main repos) as the game would crash every time on the tail-end of asset loading when connecting to a server.
Tried:
Game works for me in Wayland (I primarily drive that now not Xorg for reasons I can't remember right now)
The reason I'm on Ubuntu 25.04, Linux Kernel 6.14.0, and Mesa 25.x is because I recently upgraded nVidia RTX 4070 -> AMD RX 9070 XT, and the new AMD GPU needed these versions to work (as in, ANY GUI at all).
Putting this out there as maybe it'll help some other muddled-up gamer like myself.
Replying to https://github.com/ValveSoftware/Proton/issues/3104#issuecomment-2877434526
I had the same issue also, however after switching to GE-Proton9-27 I was able to load into a server.
Replying to [#3104 (comment)](https://github.com/ValveSoftware/Proton/issues/3104#issuecomment-2877434526)
I had the same issue also, however after switching to GE-Proton9-27 I was able to load into a server.
With which version of Mesa?
Did they introduce Anti-Cheat in this or am I dense?
Setting launch options to bash -c 'exec "${@/Rust.exe/RustClient.exe}"' -- %command% fixes it.
Can we please just have Gabe talk to Garry and convince them to finally turn EAC on through Proton? Garry literally, multiple times, publicly, said they were going to do it and were working with VALVe on the matter, but haven't. I think we need our Lord Gaben to step in and have some convincing discussions. Or something to similar effect.
anti cheat not recognized
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9776.
<Blank issue template omitted>
@MrTKusa commented on 2026-05-13T01:58:47:
No anti-cheat = no playing Rust
As far as I know there is no support for EAC in Rust under Proton. You'll have to play on server without EAC enabled, basically a handful not more available.
https://areweanticheatyet.com/?search=rust&sortOrder=&sortBy=
As far as I know there is no support for EAC in Rust under Proton. You'll have to play on server without EAC enabled, basically a handful not more available.
https://areweanticheatyet.com/?search=rust&sortOrder=&sortBy=
There is support for EAC under Proton, but it's up to the developer to toggle it on their end to work with Proton, it's just a checkbox they tick.
so Facepunch is against Linux gaming?
There is a good rational about not enabling EAC to work under Proton. It's up to them, they don't want to, that's just it.
@garrynewman what do you think? If this is never going to happen we might as well close this issue.
There is a good rational about not enabling EAC to work under Proton. It's up to them, they don't want to, that's just it.
No there isn't. Gary himself publicly on Twitter was saying he was working with VALVe and EAC to get EAC working through Proton, on and off for an entire year. Then once it was publicly put out there (EAC through Proton in general, not just for Rust), Gary and Facepunch stopped talking about it and have refused every time asked about it to turn it on. EVEN THOUGH THEY ADVOCATED FOR IT AND SAID THEY WERE WORKING ON IT.
That's not rationale behind leaving it off, and there is no rationale for Facepunch to keep it off. It's trivial work to turn on, and literally the rest of the game works flawlessly on Linux (I know because I've been playing Rust on EAC-off servers for years now). So the barrier to entry is a checkbox they refuse to check.
@garrynewman what do you think? If this is never going to happen we might as well close this issue.
This thread, just like all the others in this repo, are about general Proton issues for each game, not a singular one in this case being anti-cheat. This thread should not close as a result because other issues can crop up over time unrelated to the anti-cheat, which is what this thread (and the others) serve.
The prudent course of action is to convince Facepunch to enable EAC through Proton. All the work is done for them, even work they themselves claim to have done. They just need to actually listen.
Rust "Network error" Proton Easy anti cheat ERROR
Issue transferred from https://github.com/ValveSoftware/Proton/issues/10042.
@LoniDev1 posted on 2026-08-06T11:21:03:
Starting causes:
Network Error:
No anticheat module has been found for this game and platform
(Facepunch or Valve has fixed this error before it worked like 10 months or 4 months ago, but with the release of the Steam Machine it would be nice if this could be fixed in any way)
Just Start Rust with probably any Proton version.
Not sure about a solution, but there is a workaround for that, set your launch options to:
bash -c 'exec "${@/Rust.exe/RustClient.exe}"' -- %command%
From what i understood the main executable tries to launch the anticheat (which then will launch RustClient.exe), this fails with that error. If you start RustClient.exe directly it works (without EAC ofc)
@LoniDev1
Yeah @alex9099 I've already tried that and its "playable" with still a lot of game crashes and everything, but i think its a facepunch problem but could also be fixed if there would be a proton workaround.
The game devs do not want to support Linux for Rust. EAC will not work so you're out of luck anyway.
Yeah @alex9099 I've already tried that and its "playable" with still a lot of game crashes and everything, but i think its a facepunch problem but could also be fixed if there would be a proton workaround.
Haven't had it crash on my machine (nvidia 1080ti, 32GB ram, amd ryzen 7 5800XT, cachyOS with proton hotfix), can you give the logs of when it crashes?
Has it ran on that machine before without problems?
proton hotfixx3 2026-08proton experimentalx5 2026-08ge-proton9-27x2 2025-05proton 10.0x1 2025-05proton 10.0-1x1 2025-05proton 9.0-4x1 2025-05proton 9.0x1 2025-05proton 8.0-3x1 2023-07proton 6.3-6x1 2021-09proton 5.13x1 2021-06proton 6.3x1 2021-06proton 5.13-6x1 2021-06proton 6.3-4x1 2021-06proton 5.13-2x1 2020-11PROTON_LOG=1x5 2025-05PROTON_EAC_RUNTIME=1x1 2025-05PROTON_EAC_RUNTIME=1),x1 2025-05PROTON_LOG_DIRx1 2023-07MANGOHUD=1`x1 2023-07WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1x2 2022-03PROTON_USE_WINED3D=1x1 2021-06PULSE_LATENCY_MSEC=60 gamemoderun %command% -force-d3d11-no-singlethreadedx1 2025-05PROTON_EAC_RUNTIME=1 %command%x1 2025-05WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%x2 2022-03PROTON_USE_WINED3D=1 %command%x1 2021-06lsteamclient.dllx1 2021-06steam_api64.dllx1 2020-090xc0000005x1 2021-06
Compatibility Report
System Information
I confirm:
steam-252490.log
Symptoms
There are several problems with this game when run via Proton.
Despite all these problems, once a person manages to get in-game, it works quite well (better than the native version ever did for me).
Reproduction
3a. Click on "Play Game". The game will now crash.
3b. Alternatively, click on "Quit". The game will hang for a short while, but eventually the window should disappear.