EVE Online (8500)

[sdack]

EVE Online

The game EVE Online doesn't run out-of-the-box with Steam Play / Proton 3.7. However, this is an issue specific to WINE and the game itself. When WINE is manually set to run in "Windows XP"-mode, using winecfg, then Steam Play will start the game and the game will run normally. It then starts the EVE launcher, allows to login, starts the client and runs in DX11 with all graphics options set to high at ~90fps on an Nvidia GTX960.

To switch Proton into "Windows XP"-mode does one need to enter into the shell the following command:

$ cd "/home/user/.local/share/Steam/steamapps/common/Proton 3.7/dist/bin"
$ export WINEPREFIX="/home/user/.local/share/Steam/steamapps/compatdata/8500/pfx/"
$ ./wine winecfg

After which one can select "Windows XP" at the bottom of the WINE configuration tool.

Note: The paths need to be adjusted to the current user and the exact directories for Proton and the game. Make sure you're typing it in as shown above so it picks up the right winecfg. Don't use the winecfg that comes with your distribution. The path ~/.steam/steam/ may also be used and can be a symbolic link to ~/.local/share/Steam/ depending on the type of distro you're using. I.e.: ~/.steam/steam/steamapps/compatdata/8500/pfx/ for the WINEPREFIX and ~/.steam/steam/steamapps/common/Proton\ 3.16/dist/bin/ for the binaries.

The OS used for this was GNU/Debian 10 "Buster", Nvidia driver 396.54.02 (Vulkan beta).

Other reports on EVE Online suggest a variety of winetricks in addition to the above. However, none of these are in fact required for Debian and may only be required for other distributions.

Additional information:

• Nvidia driver releases prior to 396.54.02 can show flickering or even cause freezes.
• Depending on the window manager and compositor may it be necessary to enable Force Composite Pipeline in the settings to the Nvidia driver for the game to render correctly (see Display Configuration -> Advanced).
• The game launcher can consume unusually high cpu resources or even hang, when left running for too long. This appears to be caused by too much output coming from WINE and DXVK. Should this occur should one set WINEDEBUG=-all and DXVK_LOG_LEVEL=none as environment variables to suppress the output.
• DXVK 0.80 features a state cache, which needs to be disabled when running multiple clients, because it's currently not easily possible to have multiple state caches per executable. The environment variable DXVK_STATE_CACHE=0 needs to be set to prevent the use of the state cache.

More information regarding EVE Online on Proton can be found in the Linux section of the game's forum. https://forums.eveonline.com/t/steam-play-beta-all-games-are-available-for-download-to-linux-steam-client/99843

One minor issue remains, which is crackling sound. As this has been observed with quite a few oth`er games and not just EVE Online does this seem to have a different cause. So I'm mentioning it here, but the game works otherwise fine. Using a locally installed version of WINE 3.15/DXVK 0.71 does the game play without crackling sound. So this will possibly fix itself in the future with a newer Proton version I hope.

Update: Audio issues was fixed with https://github.com/ValveSoftware/Proton/issues/1223#issuecomment-418521585

[sdack]

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.

[Ristovski]

@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?

[smirgol]

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.

[sdack]

@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.

[Ristovski]

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.

[ghost]

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

[sdack]

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

[Ristovski]

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.

[sdack]

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.

[Peter-Nijenhuis]

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

[sdack]

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

[Peter-Nijenhuis]

@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

[sdack]

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

[Peter-Nijenhuis]

@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.

[sdack]

@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.

[Peter-Nijenhuis]

@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.

[sdack]

@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.

[sdack]

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.

[matty-r]

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.

[sdack]

@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.

[matty-r]

@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.

[sdack]

@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.

[Blacksmoke16]

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...

[Xandaros]

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.

[kisak-valve]

EVE Online

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3202. @aravoth posted on 2019-11-10T16:40:30:

Compatibility Report

• Name of the game with compatibility issues: EVE Online
• Steam AppID of the game: 8500

System Information

• GPU: NVIDIA 360m
• Driver/LLVM version: 340
• Kernel version: 4.15.0-66
• Link to full system information report as Gist: https://gist.github.com/aravoth/421aa47dfc3b4924a622ab54f426686d
• Proton version:4.11.8

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.

Proton log is too large to post link to gist here : https://gist.github.com/aravoth/45d32fc84bf326f067b7c7f5afaa6f85

Symptoms

Game crashes at start. Worked flawlessly under proton 4.11.7. Cannot get past the launcher.

Reproduction

Running EVE with proton 4.11.8 reproduces crash every time

[kisak-valve]

Hello @aravoth, your system is well below the minimum requirements for support with Proton in general and it's not clear how the game was running before. That set aside, you might get lucky if you add PROTON_USE_WINED3D=1 %command% to the game's launch options.

[aravoth]

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

[kisak-valve]

Eve Online Crash on Proton 4.11-11

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/6813. @z5d69 posted on 2020-01-06T15:46:52:

Your system information

• Steam client version (build number or date): December 16, 2019 (runtime version 0.20191210.1)
• Distribution (e.g. Ubuntu): OpenSuse 15.1, 64-bit, all patches applied
• Opted into Steam client beta?: [Yes/No] No
• Have you checked for system updates?: [Yes/No] Yes, please see above
• Proton Version v4.11-11

Please describe your issue in as much detail as possible:

When I try to run Eve Online, it won't start the game. Typically it abends with a C++ error in wine (window opens with that). Startup takes several minutes (which I thought was the way the game worked as I have ONLY steam on linux) even before the crashing started. Either way, I'm unable to exit the game without completely shutting down display-manager and killing all processes for steam / proton.
HOWEVER, when I run on 4.2-9 it all runs fine without any of the problems I see in 4.11-11.
I'm fine with running on 4.2-9 for now but concerned that, after 4.2 is deprecated, I won't have any ability to run the game. I have run into similar problems with Proton versions so I thought it was a good idea to submit an issue before 4.2 was retired.

Steps for reproducing this issue:

With ONLY ONE character created (no idea if that matters for this as I'm new to the game).

1. Select Proton 4.11-11 for running Eve Online.
2. Hit Play
3. Hit Play on Eve startup window.
4. experience C++ wine crash.

[kisak-valve]

Hello @z5d69, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[z5d69]

@kisak-valve I appreciate the assistance! Okay, NOW, when I go back to 4.11-11, it works fine. I removed the logging and did this again. Still no problems. The only thing I noticed is that right-clicking on Eve doesn't allow me to go to properties unless I exit Steam and go back in. I don't think that has anything to do with my original problem, however. I guess I'll continue to monitor it!