You will need to move the file into the proper location. For most Steam or Lutris users who don’t alter the saved file location, it should be a simple task. However what you should do is use your file manager’s search to find “eve-online/app-1.10.0” location. Be sure to allow it to search hidden folders.
The instructions above assume a lot about common Steam directories and is done on one command line. One should get to know their system and where these files are found.
Only Steam stores this file folder in; $HOME/.local/share/Steam/steamapps/common/Eve\ Online/
To break down the steps, I took to do this for myself be sure to find your own path;
Opened Terminal Emulator and copied the wget line and executed.
Opened my Thunar File Manager and found the eve-online-1.9.4-full.nupkg listed in my home directory.
Right clicked on it and “extract here”.
Then opened the new folder.
Within you see a net45 folder.
I dragged this folded and dropped it to my $HOME/.EVE/drive_c/users/John/AppData/Local/eve-online
I then renamed net45 to app-1.9.4
Cleaned up deleted the nupkg and folder from my home.
Remember to choose your file location and not mine. Hope this helps.
Oh ok… thank you gotcha now. I was not understanding, I read that as “I was looking for a directory” called ‘app-1.9.4’ in under that parent directory structure. ::smacks head::
Sorry but i did what you said, first i dont find the updater.exe on GE proton, so steam doesnt detect it, i rollback the launcher, but is still not opening the launcher
Edit:
For some reason i coulnt make it start from Steam library, BUT i went to the folder where is located the game files, and run eve-online.exe directly with wine, and it runs the launcher, im updating to see if i can make the client run too
New Edit:
I make it run with wine64, but on max settings gets lagged even when on windows it went 60fps at maximum settings
steam branch: stable
version: 1745876290
client build: mon, apr 28 5:09 pm utc -8:00
web build: fri apr 25 5;04pm utc -8
stamp api version : steamClient022
Install method: via Debian support page https://wiki.debian.org/Steam
OS: Debian 12 Stable
Eve version/build: not sure since it stopped loading
I was able to install steam and eve and run with Proton 10.0 for about 1 week. However, after the client closed due to daily downtime on the Thursday or Friday the 8/9th (don’t remember which day) I am no longer able to get Eve to load. The Eve icon loads in the task tray; however, it quickly goes away. I have gone through each version of Proton; however, nothing seems to help.
Looking for Linux users who use Steam with Proton to see if they are having the same issues, or if they have a stable work around.
Deleting the launcher 1.10 it will load now. But every time I try to do anything like go into training my client stops responding. Is this happening to anyone else?
I went through these steps. Tried with and without “PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 %command% -dx11” in the Launch Options. I click Play, Steam tells me the game is Launching, then that it is running, then it quietly fails and the Stop button goes back to Play. I guess I just won’t be playing Eve. Hopefully they’ll release a Linux native launcher again. I don’t understand why they discontinued it in the first place.
Never mind. I had only renamed the 1.10 launcher folder. I finally just deleted it with the 1.9 launcher in place, and it brought up the launcher. Of course, it crashed, but once I change to DirectX 11, I was able to play the game!
Of couse it crashed? Why don’t you fix DirectX12 / vkd3d-proton with the known workaround? (VKD3D_CONFIG=force_raw_va_cbv)
On wine i don’t have problems with DirectX12 when i apply this. Also as asked above, everything else seems to be also working for me. The client does not stop responding after i moved the app-1.10.0 folder to a completely different location.
Okay, I can confirm that something is happening. Here is a quick guide for everyone who doesn’t like working with the terminal: What I did in Steam and what I did in Lutris: Under Steam: Uninstalled and reinstalled EVE Online (it first downloads about 200 MB). Right-clicked on the game, browsed the game files, and deleted the “app1.10” folder under .steam/debian-installations/steamapps/common/Eve Online. Downloaded and extracted the package eve-online-1.9.4-full.nupkg (presumably original, downloaded from the CCP server). Copied the net45 folder from /lib/ in the extracted archive into the Steam EVE Online directory, renaming the folder to app-1.9.4. Started the game via Steam; the launcher starts and downloads another 5 GB.
Followed a similar procedure: In the Lutris EVE folder (for me, .eve/drive_c/Program Files/Eve Online), deleted the “app1.10” folder. Inserted the net45 folder from the extracted archive. Pointed Lutris to the eveonline.exe in the “new” old app1.9.4 folder and started it. Here too, the launcher downloads about 5 GB; a launcher update was announced.
Simply Stroopwafel preventing WINE users (yes, they detect us, and yes, they help with workarounds just for us) from auto-updating from 1.9.4 to 1.10.0, so we don’t break our 1.9.4 every time the Launcher tries to self update.
This is an example of how, behind the scenes, there IS work being done to ease up our (allegedly small) client base.
Do you have any proof on that? Because i have quite some proof that this is not the case. EVE installations that did the update and were manually modified will not update again since day one. Your behavior that is attributed to CCP is the default behavior since day one. I hope you all did not delete the app-1.10.0 folder or backuped the EVE installation folder before deleting it. You might need to restore to it in the future.
The second proof that i have is that i have machines that are on 1.9.4 and where turned of since before the update. Now guess what they will do when i fire them up? They will not experience any kind of detection and sparedness from being made unusable.