Linux

Thanks for response.

I have since figured out that, after launching one instance for account A, I can alt-Tab back to Eve-launcher and launch second instance for account B. I can then alt-Tab between instances.

Remaining problem is that I want each instance on its own display head, not both on same head and alt-Tab between them.

My machine has three heads and runs Xubuntu 14.04.

Under Old Regime, I use most excellent recipe from

https://forums.eveonline.com/default.aspx?g=posts&m=4568464#post4568464

For one head, I use X-desktop-launcher that has

Command:
env WINEPREFIX="/home/xxx/.wine" taskset 4 wine C:\\Program\ Files\ \(x86\)\\CCP\\EVE\\bin\\exefile.exe \/triPlatform=dx9
Working Directory:
/home/xxx/.wine/dosdevices/c:/Program Files (x86)/CCP/EVE/

For other head, I use

Command:
env WINEPREFIX="/home/xxx/.wine" taskset 8 wine C:\\Program\ Files\ \(x86\)\\CCP\\EVE2\\bin\\exefile.exe \/triPlatform=dx9
Working Directory:
/home/xxx/.wine/dosdevices/c:/Program Files (x86)/CCP/EVE2/

I do not use DISPLAY parameter to select head, as prescribed in recipe, because I get proper head by putting X-desktop-launcher on head I want and clicking on it there. Instance then runs on that head.

Under New Regime, how to launch second instance of EVE on second head?

I thought maybe to drag Eve-launcher window to other head, but am not using Xinerama, so cannot drag windows between heads.

So question remaining is, "How to multi-head?"

The problem is not launching them, that works fine. The problem is getting them to display in "Fixed Window" mode on two different screens at the same time.

Only the client for the main screen will display correctly in fixed window mode. Whenever I try to get the second client to use fixed window mode on the second screen it will automatically move to the primary screen. The only way I can get the second client to stay on the secondary screen is to keep it in windowed mode, which means, that I have a title bar and a task bar stealing screen space.

Another, actually more problematic issue is that the control-key seems to get stuck a lot. This leads me to disabling my hardeners instead of activating my weapons. I don't know if this is also related to the control key getting stuck, but I can also often not get the settings menu when pressing the "Esc" button. I then have to alt+tab into a non-eve window and come back to eve to get it to work.

Also I can't paste anything in the IGB via ctrl+v, I have to use the right mouse click menu.

I am using XFCE on a fresh Manjaro install. With AMD ATI Radeon R9.

I used fixed window mode and clients always open on the primary, which is where the launcher is; this is what I want probably two thirds of the time, so I have not tried to change it. I'm also using XFCE, and I use alt+drag to move the borderless, fixed-window-mode clients around as needed. Changing settings in the escape menu when the client is on a non-primary monitor sometimes moves them to the primary when I close the menu. I move the window back when that happens, and, while annoying, I probably won't be editing settings often enough to worry about it.

I set the window size (for fixed window mode) by editing core_public__.yaml, as I said earlier, because of similar difficulties. Have you tried selecting fixed window mode in the client, getting the window resolution you want, and then moving the window to where you want it? Does that work for you?

Thanks for response!

Yes this is exactly my situation: on other machines, where have Xinerama, I move windows freely between heads. Without Xinerama, cannot do this.

Sounds like the incorrect LD_LIBRARY_PATH handling in evelauncher.sh caused your problem. When that variable is empty, an empty search path (meaning the CWD) is added at the end. When you set the variable manually, an empty entry is no longer added as the current value is used instead. However, if you changed more than setting LD_LIBRARY_PATH, then it could be anything. (Example of how to prepend to LD_LIBRARY_PATH. You'll need your own evelauncher.sh instead of modifying the existing as launcher updates overwrite it.)

First: Many thanks to CCP Snorlax for this Launcher. Great work.

I had EVE running well on wine for many years (roughly a decade IIRC). Took a bit of fiddling sometimes, occasionally didn't work a for a couple of days after a new EVE upgrade release (or a few hours after a wine version introduced a regression) - but 99% of the time everything was fine.

But my machine was due for a storage upgrade and so I used this occasion of a fresh Ubuntu 16.04 install to try this new unofficial, unsupported ;-) evelauncher.

Shortly after 16.04 was started for the first time – without any wine install (no playonlinux or anything) - but Steam for Linux was already installed - I installed this launcher.

Initial setup and download (wine and assets) went smooth enough - but then nothing happened when I pushed the play button.

After going through the terminal output and log files I had to install the following 4 packages to get EVE going:
libgnutls30:i386
libfreetype6:i386
libldap-2.4-2:i386
mpg123:i386

As others in this thread have reported out-of-the-box success - I'm assuming that above packages are installed by playonlinux or otherwise in typical wine setups.

The launcher complained about a missing steam appid file (I bought EVE back in 03 - long before there was a Steam version) - so I made it shut up by creating a steam_appid.txt file with just 8500 in it (EVE appid according to steam database). It probably made no difference for the actual working of the launcher and game.

Finally I extracted an icon from the exe and created a desktop file for it - so now it looks nice in the Unity launcher.

As others have reported before, the IGB gives me trouble (crashing actually). Worked fine in my old install so I'm confident that can be fixed. I did try the linking of libgnutls.so.26 -> /usr/lib/i386-linux-gnu/libgnutls.so.30.
But that didn't do the trick for me. Will debug that later - can live without the IGB for a while.

So on the whole I'm very happy with the evelauncher. And it's only a few little tweaks away from being out-of-the-box perfect.
A deb would have been nice - but I don't want to be greedy - it's already ok as it is.
And I'm sure resources for stuff that's officially unsupported are limited. :-)

Again thanks for providing this evelauncher - it's much appreciated.

Thanks for your work!

Is the any chance we could use system-wide wine and/or custom game launch command (at least from "Server list")?

If you unpacked the evelauncher somewhere within your home folder hierarchy you shouln't run it with sudo.

In terminal and assuming you switched into your evelauncher folder - simply do this:

./evelauncher.sh

sudo is for when you want to run stuff with root (= Administrator) priviliges.
You do that for installing packages or changing system configuration.

shell scripts that are installed by you into your own home folder has your own access permissions and therefore can be run by you (without root priviliges).

I'm not familiar with zorin - otherwise I would tell you how to create a desktop file to have a nice launcher icon on your desktop.

WOW,

Thank you CCP Snorlax, you have no idea how long i have been waiting for this.. again thank you .....


The launcher and game runs great, totally stoked about that ....

although one issue that i am getting errors on is that there is no audio, this i can mark down to not having a correct lib installed ..

I'm running Ubuntu 16.04 (4 day clean install) i don't think that the errors are launcher related, they seem more wine related?

ERROR OUTPUT:

"err:module:load_builtin_dll failed to load .so lib for builtin L\"winepulse.drv\": libpulse.so.0: cannot open shared object file: No such file or directory"
"err:module:load_builtin_dll failed to load .so lib for builtin L\"winealsa.drv\": libasound.so.2: cannot open shared object file: No such file or directory"


now, i have done some poking around thinking that maybe im missing the libpulse.so.0 and libasound.so.2 libs, but im not they are actually installed and up to date, but the system im running is 64b, im going to go out on a limb here and guess that they are looking for the 32b

if anyone could point me towards a solution that would be awesome

i appreciate all your hard work with this launcher CCP Snorlax, please keep up the good work, im sure there are a lot of us in the linux community that will help you if you need anything


Clock

libasound is ALSA. If you don't have pulseaudio (libpulse...), Wine will failback to ALSA (the actual driver) but it look like your missing the alsa 32bits library. EVE will work without pulse audio but you will need alsa in that case (and alsa will always be required anyway)