Adara, launch your file exporer and navigate to your home directory. View hidden items by using the shortcut ctrl+h. You should see a directory in there called “.eve”.
So here the path to your Eve files within the .eve directory would be your prefix. Typically, the full path in this instance would be something like “/home/.eve/wineenv/drive_c/tq”
Another location for you might be in the Steam directory for Eve, e.g.: “/home/.steam/steam/steamapps/common/Eve Online”
Explorer around your system. You might have multiple installations/locations.
The prefix just points to the root of the virtual windows drive, not the actual eve installation. So in that example the prefix would probably be /home/user/.eve/wineenv
If it complains that it’s not a valid prefix then whatever tool you used to install it is doing weird/custom stuff with the setup and I can’t really help you. Using convenience tools and wrappers around wine programs makes it hard to diagnose problems because they add layers of complexity to something that get in the way of troubleshooting. Most of the people in these threads that are having trouble with the patches/workarounds are people using the deprecated native launcher or lutris it seems like.
Just for reference, here is all that is required to get the game to run on a direct wine setup:
Download the windows launcher
Install the latest wine-staging (6.19)
Create a new wine prefix with the desired install (prefix) location
Play the game with the workarounds described in this and other threads until the patch that fixes the bug is merged upstream. Depending on your distro, Wine will probably create a desktop launcher for you with all the parameters set that you need to play, so launching it will be more convenient going forward.
If you notice the pattern above, WINEPREFIX before wine commands just tells wine which virtual Windows system you want to use when doing things. If that folder doesn’t exist it will be created the first time. It’s considered best practice to keep separate prefixes for different programs so that hacks to fix one program don’t affect others. I keep all my prefixes under a common directory like /home/renard/prefixes.
Thanks for the step by step, I’ll try to make a new one then. I didnt use any other helping tools, just what you described, but the concept of prefixes is still something that it will take time for me to get. I only play EVE, and I dont have time for other games really, so I probably dont need a folder to save them all. I was trying to add dxvk to my existing .eve but this one is using the deprecated Linux Launcher, which is still working, surprisingly, but with a lot of CPU overhead.
I wonder if I can download the most recent windows launcher to set it up…
And yes, you are right, I have a bunch of EVE installs, trying different things hoping one would work. With Lutris I had 2, then I had Steam, and the Linux Launcher.
@Obrym: Thanks, but I dont think you noticed that I already was seeing .eve However you did point out that my path was incorrect.
I’ll follow Renard’s guide and make a new one.
PS: Ok, followed the instructions to the letter, in all forgot to rename user to my user haha. Its currently installing. I’ll copy the launchdarkly.pyd once its done. Ah, also the eve profiles for my clients. Thanks Renard
Good luck! Also note that installing EVE this way doesn’t mean you can’t continue to use Lutris/steam/etc for other games. It’s helpful to know how to do this manually in cases where things don’t run with Lutris and require manual troubleshooting steps with normal wine.
Try launching the game and making sure it runs before migrating your profiles IMO. I’ve never actually moved profiles before but any Windows guide should do, just look in PREFIX/drive_c/EVE/SharedCache for where to put them
Is there some way to configure the launcher to prevent it from updating? I’ve been clicking cancel, but the dialogue glitched out today and the update was unavoidable.
On the other hand, is there some way to roll back to a previous launcher?
The workaround is to move a file one directory up in the latest Windows launcher, or to apply a patch to wine or wine-staging that fixes the root cause. Using an outdated launcher is an older “workaround” for a previous problem that was already fixed in wine
I’ve followed your steps exactly. I move the file launchdarkly_client.pyd up a directory. then I run WINEARCH=win64 WINEPREFIX=/path/to/prefix wine eve.exe
The launcher starts and communicates with the eve servers. I am logged in. When the play button is available I click it. I get the little pop up telling me that the client is launching. After 10 minutes, nothing has happened. std err is uploaded at the link below.
Sounds like you didn’t set launchdarkly to read only after moving it. In the launcher options toggle the option to launch with loglite and see what a errors you get.
You have to either set it to read only or move it AFTER starting the launcher because the launcher actually deletes it when it starts
Wish we could put those instructions pinned at the top it would save a lot of time for many to find the way to use it. Oh, and I’m running Wine Staging 6.19.
and after I did the launcharkly_client.pyd fix EVE is now working flawlessly on my laptop with Wine 6.22 under Ubuntu 21.10 . Even let’s me switch between my nvidia GPU and the integrated intel graphics in the options.
I had given up on EVE in Linux and had resorted to using an old windows machine to hold the fort until my subscriptions ran out.
I received an answer from the crossover folks who indicated that Version 21.1.0 should work. I originally tried the trial Version 21.0.0 with no luck. it was just before they came out with the new version.
Clean Linux Mint install and Clean Crossover install. Ran right out of the box.
No wine install on the mint system.
And it runs well. I’m back in EVE in Linux again.
Lovely Christmas present.
This is also on another EVE linux thread.
Almost forgot. A tidbit from Crossover.
“You might want to reach out to CCP to see if they have an immediate solution. They have historically tested against CrossOver/Wine for compatibility.”
Go figure.
However you did point out that my path was incorrect.
So far on idle, docked, getting 35-53% cpu usage (with 5 clients), which is great 