I've found a fix to my audio problem. Adding tsched=0 in /etc/pulse/default.pa fixed it for me.

...
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect tsched=0
...

I didn't need the fix for WINE 3.0 to WINE 3.15 and the sound issue appears to be something specific to Proton.

@sdack You mentioned that locally there is no crackling sound.

Apart from the standard setup procedure (installing necessary wine modules like corefonts etc) have you done anything else to your local wine environment?

I can confirm that all it needs to make the game work is to set the windows version to WinXP. Noticed no sound issues on my end so far. I did not install anything with winetricks, btw.

@Ristovski No. For me does EVE not need any winetricks, which means no core fonts or other stuff. Apart from the "Windows XP"-mode does EVE Online run out-of-the-box for me. On my local WINE installation for EVE did I only have to follow the steps that are required for DXVK to run. This is for Debian 10 "Buster" aka testing.
Other distros may need dotnet40, corefonts and possibly other winetricks applied before it runs. Also note that I don't use the outdated Linux-native launcher by CCP, but only the Windows-native launcher, which comes with the Windows installer for EVE.

What is interesting is that (at least with wine 3.13), the game works on any Windows version in Wine. The only issue I ran into is random crashes in the _trinity_dx11 dll which I think is caused by not having the whole games content pre-downloaded, as it only happens when you warp out on new systems. The audio crackling seems to go away after some time as well.

I will do some further testing today with multiple wine prefixes.

Or one line and less to change per game:
$ WINEPREFIX=$HOME/.steam/steam/SteamApps/compatdata/8500/pfx winecfg

@byte1024 No, don't do this. It has the chance to pick up the wrong winecfg and screw it up for you.

Update: No crackling audio on Wine 3.15 for me, running Eve in it's own prefix with no additional winetricks installed. Do note I am running Eve with DXVK_LOG_LEVEL=none which seems to make it more stable and stop Eve from uploading the DXVK logs to the CCP servers.

Update: Crash resolved, apparently the version of glibc I had had a bug where calling sin() with certain values caused a page fault. I'm guessing due to my performance flags Wine did not reveal the full backtrace. Resolved by upgrading glibc.

DXVK 0.80 now features a state cache, which is kept in the same directory as the log files. The state cache can currently not distinguish between multiple instances of the game, which makes the state cache currently unusable with multiple clients. The consequence is a crash in dxgi.

To disable the state cache does one need to set the environment variable DXVK_STATE_CACHE=0.

The path is quite different for me. But when I go to the desired folder, there's no wineprefix to export.

here's what's in my folder:

pjotr@pop-os:~/.steam/steam/steamapps/common/Proton 3.7/dist/bin$ dir
wine wine64 wine64-preloader wine-preloader wineserver

@Peter-Nijenhuis It's probably because ~/.steam/steam/ is a symbolic link to ~/.local/share/Steam/.

@sdack yeah, that was also my thought.
However, there's no wineprefix to export, since the only files which are present in that particular folder, are:
wine wine64 wine64-preloader wine-preloader wineserver

@Peter-Nijenhuis Try ~/.steam/steam/steamapps/compatdata/8500/pfx/ and see if it exists and what's in there.

@sdack those folders exists.
In ~/.steam/steam/steamapps/compatdata/8500/pfx/ I see the following:
Folder: dosdevices
Folder: drive_c
File: system.reg
File: user.reg
File: userdef.reg
File: .update-timestamp

That's all in the pfx folder.

@Peter-Nijenhuis This is your WINEPREFIX directory. So you have to set the variable to this directory before you run winecfg. And don't use the winecfg, which comes with your distro's WINE installation, but do use ./wine winecfg within the Proton bin-directory, or else will it pick up the wrong WINE version.

@sdack perfect :)
I just got one step further.

So I did this:
$ cd "/home/pjotr/.steam/steam/steamapps/common/Proton 3.7/dist/bin"
$ export WINEPREFIX="/home/pjotr/.steam/steam/steamapps/compatdata/8500/pfx/"
$ ./wine winecfg

A Wine window pops up, and I could change it from "windows 7" to " windows XP"

However, I also see this in terminal:

$ ./wine winecfg001f:err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory
001f:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\WineBus": c0000142
001f:err:winedevice:create_driver failed to create driver L"WineBus": c0000142
0013:err:service:process_send_command service protocol error - failed to write pipe!
000d:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 1114

Furthermore, the launcher doesn't start.

@Peter-Nijenhuis Try a clean install and do it over. Maybe your repeated attempts have messed it up. You really should only need to set it to "Windows XP"-mode. If it then still won't work then you'll have to dig deeper. Maybe try to get it running just with a standard WINE installation and using only DirectX9 over OpenGL to see if this works at all before you go start with Steam Play / Proton and with DirectX11 over Vulkan.

WINE 3.20 has fixed the issue around the "Windows XP"-mode and there it is no longer required to set it.

As soon as Proton gets updated to WINE 3.20+ should EVE Online run out-of-the-box and without requiring the "Windows XP"-mode fix any longer.

I'm having a number of issues with this.

The first error is show as soon as I launch it:
A certificate error has occurred: Server's certificate is not trusted https://hello.myfonts.net/count/2d83e2.

If I click ignore it's not shown again, if I click cancel that same error is shown multiple times.

The next error is the same, however the URL is https://az416426.vo.msecnd.net/scripts/a/ai.0.js.

The last issue, probably the worst part: The game will launch then after the loading bar that says "Authorizing" it will crash and report in the launcher that the client closed unexpectedly.

@matty-r: CCP has made changes to their login service recently. See here:

https://www.eveonline.com/article/pi6klt/security-changes-to-the-eve-sso

This will likely be the source of your problems. If the problems don't resolve themselves then wipe the game and reinstall it. See if it helps. Others have had issues since the SSO changes under Windows and Linux, all outside of Steam. So unless you've made sure this is a problem with Steam Proton itself should you just stick to the game's forum for help.

@sdack none of these issues are preset on Windows. However i'm able to play on linux if I just double click on the eve.exe, however trying to play through steam will continue to close unexpectedly.

@matty-r: I cannot tell you what your problem is. It is working just fine for me. Only to be sure did I wipe it all and did a full reinstall of Steam and the game (including the "Windows XP"-mode fix). It continues to work. I suggest you remove all characters from the EVE launcher (see "forget accounts" in the launcher settings to EVE) and try again. This could be anything from a simple network glitch to a broken installation or a Steam-incompatible distro.

Can confirm changing to windows xp fixed a clipboard copy/paste issue i was having. Also fixed (so far, about an hour in) freeze issue i was having that just started today...

Changing the wineprefix to Windows XP was also required for me. Game does not start otherwise.

There are major performance issues with the latest Proton 4.11. Disabling FSYNC fixes those.

I wanted to let you know that your solution worked, and EVE is now running under proton 4.11.8 flawlessly again.

@kisak-valve Okay, it DID eventually error out. Checked the logs. # of files open exceeded limit. Upped it to 200k (which seems pretty high but I figured it would let me check this out further). I notice that it's at 13490 files open right now (just sitting there at the beginning of the actual game with the spaceship sitting there). They are all from this game (or the game and wine, running this game). This is on 4.11-11. It might do the same thing on the older Proton release.

@kisak-valve Thank you! I appreciate it! This was the first time I ran into that for Proton!

Game works fine with proton 5.0-2.

Using Proton 5.0-7, the only thing that doesn't seem to work for me is some of the audio.
Weapons firing, explosions, afterburner/micro warpdrive etc. These sounds are completely absent for me.

All UI related sounds work just fine and music works fine.

Sound didn't work for me the first time the game started, but it worked from the second time on. Maybe it's an issue with the download of the content and once it's downloaded and cached locally it works fine.

The only issue I found in the game so far is that it freezes every few hours of gameplay and need to be terminated forcefully and restarted. This both with proton 5.13-1 and 5.0-10 with the former feeling slightly worst and having the freeze a tad more frequently.

Uh I think I found something

eventfd: Too many open files
eventfd: Too many open files
10882.797:00f0:0730:err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased

I have 500k at the moment, will try to increase to 1 million.

Uh I think I found something

eventfd: Too many open files
eventfd: Too many open files
10882.797:00f0:0730:err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased

I have 500k at the moment, will try to increase to 1 million.

this did the trick. No more crashes. So this is something to take into consideration as quite a few Linux distro don't allow such an high number of open files by default. I'll open a bug to the Fedora steam package, there is a quick solution, which would be dropping a file in /etc/security/limits.d/. A bit controverse, not everybody will like this I suppose... we'll see and maybe there are better solutions to this.

This game does not work with proton experimental or the 5.13 series. It does however (fully) work on 5.0. No issues whatsoever on 5.0.

Sure, here you go. I can't upload .log to github so here is a .zip.

log.zip

gist - https://gist.github.com/SimplyCorbett/541d51b4b8a04b46263449733885931a

New EVE Launcher update just hit, and new issue.

The launcher no longer loads properly, and instead loads a gray screen with the settings, minimize, and close buttons in the corner. It also loads a second window titled "Server list - EVE Launcher" with text bottom left saying "An exception occurred while creating web GUI - falling back to server list view"

While the server list will let you get in-game, logging in via the in-game screen has been disabled in favor of the launcher, which you currently cannot log in from, at least from what I can tell.

I've tried Proton Experimental, 5.13-6, and 3.16-9, to no avail.

You can try it with version 5.0-10, with it runs the game..

EVE works with the current proton version but if I try to resize the game when its in window mode there is a good chance it's going to crash the game. Anyone have a solution for this?

Note that the new launcher will have issues in the future: https://forums.eveonline.com/t/new-launcher-new-linux-error/319782/104?u=davos_shaile

The launcher works perfectly but I cannot launch any game clients. "Game client assigned to ... as closed unexpectedly".
With the logger activated, I have the following surprising line: "Execution of DirectXRedist.exe failed (exit code 9009)"
Is there something I am missing?
I'm on NixOS and think I have all proton's requirements. my drivers are also up to date: Mesa 21.1.3 with LLVM 12.0.0.
Is there a way to debug this?

I'm also having issues with logging into the game. I can get to the character screen and then it just dies on me when entering the game.

Hey, my issue is with vulkan actually, so it is irrelevant to the discussion, my bad

I've done further testing. It turns out with an intel 8700k the game will not get past character login. But with an AMD 3900x the game plays flawlessly.

That's what I'm seeing on my end anyway. I swapped the SSD/OS between nodes so the configuration is the exact same.

EVE Online still does not work out of the box, even with Proton 6.3.8-RC, without the workaround outlined here: https://forums.eveonline.com/t/client-not-launching-properly-solved/335585/2
A patch for this issue exists, but have not been mainlined yet: https://www.winehq.org/pipermail/wine-devel/2021-October/199483.html
Bugreport: https://bugs.winehq.org/show_bug.cgi?id=51821

EVE developers are moving certain features of the game to microservices on a separate server, on Proton but NOT on any wine (vanilla or staging) these features error out without a timeout exception (unfortunately performance on regular wine is trash compared to Proton). I've scoured through the Proton log but could not find anything noteworthy.

unfortunately performance on regular wine is trash compared to Proton

@EntropicEffect Just to be sure, did you install DXVK inside Wine? That could be causing the degraded performance as it would be using Wines DirectX->Vulkan translation layer, which is not as performant as DXVK.

Another idea would be to try Wine with the esync/fsync patches, which is what Proton has iirc, or try Wine with the TkG patchset (builds can be found here)

EVE developers are moving certain features of the game to microservices on a separate server, on Proton but NOT on any wine (vanilla or staging) these features error out without a timeout exception (unfortunately performance on regular wine is trash compared to Proton). I've scoured through the Proton log but could not find anything noteworthy.

It looks like AIR and Skill Plans are both working in Proton Experimental, now.

Hello,

EVE Online frequently crashes when doing orientation agent missions (I've not yet tried to fly on my own and do other kind of contents). It freezes and after alt-tabbing out an back, I get a Steam application 8500 stopped responding, and I have no other choice than to kill it (waiting doesn't recover the game). I've done this on proton 8.0-5 and proton experimental, with and without PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command%.

Edit: The freeze happens several seconds after warping in a zone and engaging enemies, or activating the warp gate.

Regards.

To help others who've mentioned Eve constantly crash - it looks like a bug with running the game in DX12 (gathered from here https://www.protondb.com/app/8500 )
Changing to DX11 seems to be the current workaround.

launching eve online sometimes (70%) causes audio to drop for a second or two at random intervals. Quitting game won't fix the issue until a reboot. Using pipewire

latest launcher update broke it, anyone have a fix for it?

@fuzunspm @wereii
I found the previous launcher for download: <Link removed by moderator>
Replace this folder with ~/.local/share/Steam/steamapps/common/Eve\ Online/app-1.10.0
Solved the issue for me, at least until a solid fix comes out.

I have fixed it by downloading the older launcher directly from CCP, as seen in this comment on eve forums
https://forums.eveonline.com/t/eve-launcher-on-linux-lutris-not-working-after-launcher-update-5-08-2025/485547/29

thank you so much @OlavioH @wereii

After the Nvidia 575 driver there are occasional screen stutters, and even worse after setting PROTON_ENABLE_WAYLAND it will crash right after the game has been running for a while (but the launcher itself doesn't crash)

The game is back to crashing before it even properly starts. I've tried multiple proton versions to no success

Alt-tabbing away from the launcher or the game to another Xwayland window (including back to the launcher, a second client, and other games) breaks input for me most of the time on GNOME 49. It makes multiboxing impossible. It doesn't happen if I use the wayland driver (from GE-Proton), but that makes the launcher render as a fully black window (EDIT: black window fixed by --in-process-gpu).

System Information

• GPU: RX 7800 XT
• Video driver version: Mesa 25.2.3
• Kernel version: 6.17.0
• Link to full system information report as Gist: https://gist.github.com/andrei8l/d5d5385c64db287a5bfaeca600f16d20
• Proton version: 9, 10, experimental, GE-Proton 10

steam-8500.log