Happy New Year to all pilots!
Some little changes on my website to more explain, how to use the new standalone installer.
HTH 
God I am so confused by all of this, and the layout of this forum
I downloaded the latest ubuntu and the latest eve launcher from some eve website, and i went thru the wiki steps and the launcher doesnt launch the game.
it just says stop
what do i do, i dont know how to linux
Today i have updated all versions of my scripts (standalone, aur and big installer on aur) for compatibility to the released wine stable version. If the older versions are working to your complete satisfaction and you don’t need the implemented winetricks verb reinstall function there are no need to update to this version.
– fly safe o7
Quick question: how can I update DXVK to the latest version on my installation, which was based on your scripts? The evewinetricks script lets me install the latest DXVK, but it seems that it won’t let me update it or remove and re-install it.
The reinstallation is always forced which means, based on the winetricks version you become always the installed version fom DXVK. At the moment are version 0.96 the latest, so if you want 0.94 then use
evewinetricks --force dxvk94
in a terminal. Which DXVK versions from your winetricksversion are supported can you see in the menu. If you have a versioned DXVK installed, then will evewinetricks by changed wine versions this DVXK reinstall, an unversioned DXVK means always the latest and newest version.
Thank you! And if I have both latest and an older version installed, how should I remove the older one (if I should)?
Sorry for waiting long time for an answer. There is no need to remove old files from DXVK. In case of an update the old files will be overwritten from the new ones. If you want to disable/remove DXVK just launch evewinecfg and remove the DXVK entries there. Wine will use then his buildin libraries again instead of the DXVK libraries.
Today i have my scripts updated to the new version from evelauncher 1456645. Please have a look on my site or on AUR to see the changes.
1 Like
Thank you! Thanks to your former instructions I was able to update DXVK through evewinetricks --force dxvk which pulls the latest version, and the launcher seems to update itself.
By looking forward to the coming 64bit client of EVE Online i have today my AUR packages updated to revision 4. Changes are described on the AUR website. If you want to move to an 64bit setup for the coming test on Singularity i recommend to remove your actualy environment in your $HOME and setup EVE completely new. The things you must do for this are:
cd ~/.local/lib/EVE/SharedCache/wineenv
rm -f .update-timestamp
rm -f *.reg
cd drive_c
rm -rf Program*
rm -rf windows
After doing this you have cleaned up your eve wine environment but EVE’s binaries and your EVE settings are in place for the new 64bit environment which you become by starting the updated evelauncher.sh or desktop launcher now.
– fly safe 07
Update: Standalone Package on my website or now in sync with AUR package.
Yet another update: All packages updated again because used bashism.
1 Like
Another minor update for my installer packages and scripts. If the previous version work well for you there is no need to update to this version. Have a look at AUR for Arch-based distributions or at my homepage at Setup Solution for EVE Linux Launcher for some explanations.
– fly safe o7
Today i have my stuff updated to the new evelauncher version 1501045. Download adresses have not changed since the last post, have a look there. If you have used my scripts before, then the launcher updated to this version you can exchange the launcher files from CCP with the optimized ones from my packages by replacing the files with following commands:
cd $HOME/.local/lib/EVE
rm -rfv ./Launcher
tar xvf /opt/evesetup/lib/evelauncher-1501045.tar.gz
mv evelauncher/ Launcher/
If you using the AUR native package you can do this with this commands:
cd $HOME/.local/lib/EVE
rm -rfv ./Launcher
tar xvf /opt/evesetup/lib/launcher-1501045.tar.xz
Missing locales should the evelauncher.sh script adding when she are missing after the replacing.
– fly safe o7
Hey Gharim_Turen,
I just went thru your guide and it went flawlessly all the way until launching the actual launcher.
I tried starting it from the app launcher but after the firsttime wine-fixes it does i only get this (Im on Manjaro)
QObject::startTimer: Timers can only be used with threads started with QThread
Could not initialize GLX
/home/linkus/.local/lib/EVE/Launcher/evelauncher.sh: line 14: 3737 Aborted (core dumped) “$dirname/appname" "@”
EDIT: deleted all libxcb files in /home/linkus/.local/lib/EVE/Launcher and now all works! thanks! 
I suppose, you have build the independed installer and used him on Manjaro. I using Manjaro too atm and have build an AUR package with makepkg so that i can use Manjaro’s own QT and Xlibs. It saves space in your $HOME by using system files which you have maybe always installed and you have an evesetup in your package pool. Give it a try, its not hard to build an installer package especially for ARCH-based distributions. You can do this with following commands:
cd <path to extracted>/evesetup
makepkg
Thats all. Then you can install this package after remove the other installation by running
sudo ./evesetup-1501045-0-x86_64.run
sudo pacman -U --asdeps evesetup-1501045-0-x86_64.pkg.tar.xz
If you do so, dont forget to exchange the launcher files by using the commands which i have described in the post before for an AUR native package.
Oh and btw, welcome to the EVE Linux Forum 
Hi, iam new to Linux, i have the latest Linux Mint. Launcher starts but the game doesnt launch …
Anyone knows a solution?
Hello Gharim Turen,
After using the latest version of the installation script, I keep getting
ERROR: “winecfg” from “Custom Wine path” not found!
Whenever I try to run one of the binaries.
Is there something I can do to fix it?
EDIT: no matter, this is my fault - I had two versions of the script active at once. I’ll take care of it myself
Welcome to eve on linux She Lob.
Unfortunately with that tiny snip it is impossible to see exactly where it all started.
Perhaps we need to back up to step one and find out if you did:
- Straight new Mint install; then wine; then windows eve client or
- Tried one of the online posted methods with a modified linux launcher. (aka Eve Uni or Gharim Turen’s excellent work).
A new evelauncher version is coming in, so i have update my scripts too. Downloads are this time only possible from AUR because i have at the moment no access to my website to update the downloads there.
The most important change on the build are, that you can now integrate the downloaded evelauncher binary archive in the distribution independed installer or download the evelauncher binaries later by installing the setup. If you want to integrate them just copy the downloaded archive in the evesetup directory and then build the installer. The AUR package uses the libraries from the system as always and integrate the dependencies from evelauncher itself by build time.
– fly safe o7
Hi Gharim,
Still busy 
To let you know I’m still alive 
latest EVE Launcher Linux 1514997 is out with the anticipated 64bit opt-in YAY.
Running now with wine-staging 4.8 (4.9 has issues) 64bit. No (performance) issues sofar.
Sadly the 64bit optin doesn’t stick after (re)starting the launcher.
Keep up the work 
Hoi Roesjka, nice to see you too.
Yeah i’m still on fiddling on my launcher scripts which are now updated to 1514997. Had a bad day with four fixes at one day but now it works as intended.
Running EVE atm on Manjaro with wine-devel 4.8 and DXVK 1.2.1 in 32- and 64-bit mode. No advantages or issues through the 64bit mode here. On Debian stable with wine-stable 4.0.1 and DXVK 1.2.1 from time to time little hickups (crashes) in wine which are gone after an restart from EVE (maybe driver issues).
I think, as long the 64bit mode on linux are beta the opt-in will not stick. Same as the annoing WINEDEBUG option, which i must set every restart from the launcher because she where cleared also. Would be nice when this somedays are fixed.
For the WINEDEBUG option I set it with export WINEDEBUG=-all in .bashrc. Then I don’t have to worry abt. it in the settings.