These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Linux

 
  • Topic is locked indefinitely.
 

Multiple Client with new NeoCom Patch
Author
Previous Topic Next Topic
Rastuasi
Crunchy Crunchy
#1 - 2012-01-24 14:29:42 UTC
I am running Ubuntu 10.04 64bit with WINE 1.3.37 and after this mornings patch I can no longer launch more than 2 clients. My RAM is not even close to full nor is cpu...

Is anyone else having this bug? And if so, is there a known fix?

I launch eve and it just crashes after splash screen when i get more than 2 clients running.

Thanks,
Rastuasi
Bent Barrel
#2 - 2012-01-24 14:32:10 UTC
Rastuasi wrote:
I am running Ubuntu 10.04 64bit with WINE 1.3.37 and after this mornings patch I can no longer launch more than 2 clients. My RAM is not even close to full nor is cpu...

Is anyone else having this bug? And if so, is there a known fix?

I launch eve and it just crashes after splash screen when i get more than 2 clients running.

Thanks,
Rastuasi


launch client, configure neocom, close 1st, launch 2nd, configure neocom, close 2nd, launch both ... does that work ?
Rastuasi
Crunchy Crunchy
#3 - 2012-01-24 14:46:47 UTC  |  Edited by: Rastuasi
Bent Barrel wrote:
Rastuasi wrote:
I am running Ubuntu 10.04 64bit with WINE 1.3.37 and after this mornings patch I can no longer launch more than 2 clients. My RAM is not even close to full nor is cpu...

Is anyone else having this bug? And if so, is there a known fix?

I launch eve and it just crashes after splash screen when i get more than 2 clients running.

Thanks,
Rastuasi


launch client, configure neocom, close 1st, launch 2nd, configure neocom, close 2nd, launch both ... does that work ?


Nope, which is what I do EVERY patch anyways, just launch one, let it get itself sorted. It just crashes on the third one...after incarna it did it on the fourth one, but the fourth was just when my friend was visiting and needed to change is queue cause he forgot and shut his comp, we saw the same behavior.

EDIT: Also, if I start 2 then start a third while still at log in screen it disconnects the other 2, wont let them log in. Also if you do not have this bug, are you running a different distro?
Bent Barrel
#4 - 2012-01-24 15:56:06 UTC
Rastuasi wrote:
Bent Barrel wrote:
Rastuasi wrote:
I am running Ubuntu 10.04 64bit with WINE 1.3.37 and after this mornings patch I can no longer launch more than 2 clients. My RAM is not even close to full nor is cpu...

Is anyone else having this bug? And if so, is there a known fix?

I launch eve and it just crashes after splash screen when i get more than 2 clients running.

Thanks,
Rastuasi


launch client, configure neocom, close 1st, launch 2nd, configure neocom, close 2nd, launch both ... does that work ?


Nope, which is what I do EVERY patch anyways, just launch one, let it get itself sorted. It just crashes on the third one...after incarna it did it on the fourth one, but the fourth was just when my friend was visiting and needed to change is queue cause he forgot and shut his comp, we saw the same behavior.

EDIT: Also, if I start 2 then start a third while still at log in screen it disconnects the other 2, wont let them log in. Also if you do not have this bug, are you running a different distro?


I am not running multi clients at all ... was just a quick suggestion :-) I see you already accounted for it.
Nebu Retski
Lead Farmers
#5 - 2012-01-25 09:29:15 UTC
Before anyone can actually help you, please provide detailed information:
- 32 bit or 64 bit OS and what distribution
- wine version
- what are the errors you are getting in the terminal when you try to run 2 clients?
- what command are you using to start both clients?

I run a 64 bit Arch linux with wine 1.3.32 (I think, not this computer) and 2 clients run just fine.
Rastuasi
Crunchy Crunchy
#6 - 2012-01-27 16:16:10 UTC
Rastuasi wrote:
I am running Ubuntu 10.04 64bit with WINE 1.3.37 and after this mornings patch I can no longer launch more than 2 clients. My RAM is not even close to full nor is cpu...

Is anyone else having this bug? And if so, is there a known fix?

I launch eve and it just crashes after splash screen when i get more than 2 clients running.

Thanks,
Rastuasi


Right there was all the info you asked already stated. I do not run this via terminal, I use a script that was suggested here on the forums.


#!/bin/bash

eveNum=`ps aux | less | grep "ExeFile.exe" | wc -l`
wine explorer /desktop=EVE$RANDOM,1600x900 "C:\Program Files\CCP\EVE\eve.exe"


and I attached a launcher that just runs that.

I run 2 clients perfectly fine, it's the third one that I cannot get started.
Bent Barrel
#7 - 2012-01-28 07:28:51 UTC
Rastuasi wrote:
Rastuasi wrote:
I am running Ubuntu 10.04 64bit with WINE 1.3.37 and after this mornings patch I can no longer launch more than 2 clients. My RAM is not even close to full nor is cpu...

Is anyone else having this bug? And if so, is there a known fix?

I launch eve and it just crashes after splash screen when i get more than 2 clients running.

Thanks,
Rastuasi


Right there was all the info you asked already stated. I do not run this via terminal, I use a script that was suggested here on the forums.


#!/bin/bash

eveNum=`ps aux | less | grep "ExeFile.exe" | wc -l`
wine explorer /desktop=EVE$RANDOM,1600x900 "C:\Program Files\CCP\EVE\eve.exe"


and I attached a launcher that just runs that.

I run 2 clients perfectly fine, it's the third one that I cannot get started.


drop the eveNum line from the script, you are not using it anyway and it's incorrect. then try.
Xorphix
School of Applied Knowledge
Caldari State
#8 - 2012-02-03 06:31:46 UTC
I ran fine on wine 1.1.37 on ubuntu which was the most stable for Eve for me yet, but after Crucible was introduced I couldn't start more than 1 client, the second complained about missing .dlls.

I updated to wine 1.3.37 and that fixed the issue, however the client crashes now if I'm typing while docking (can't have all eh?).

But in order to launch more than 2 clients, I figured Eve has some folders with some temporarely files, which I assume is some place it unpacks those .dll files, and that causes multiple clients to conflict. So a quick and dirty way to get around this, was creating multiple .wine folders, I simply copied my current .wine folder to .wine1, .wine2, .wine3 etc, and use this script to launch my Eve:

#!/bin/sh
START="Eve"+`date +%s`
LOGIN_NAME=`whoami`
env WINEPREFIX="/home/$LOGIN_NAME/.wineX" nice -n 0 wine explorer /desktop=$START,1280x720 "c:\program files\ccp\eve\eve.exe" &

I have a script for each client and that sets WINEPREFIX to point to the .wineX I wish to start, with a title of "Eve-date", so its possible to launch multiple copies of the same .wineX, if need be.

Its a super lame way of doing it, but it seems to work(TM), but maybe someone found out what directory inside Eve's files that contains conflicting files, maybe this can be improved to only differ on those folders.. ?
Marsan
#9 - 2012-02-05 17:46:32 UTC
I've been running 2 clients for over a year. The only issues I see is if I have an old hung client, and if I start 2 eve clients at once.


My eve startup script:
killall ExeFile.exe &>/dev/null
sleep 1
killall -9 ExeFile.exe &>/dev/null
wine explorer /desktop=4,1280x1024 ~/.wine/drive_c/EVE/eve.exe &
sleep 15
wine explorer /desktop=5,1280x1024 ~/.wine/drive_c/EVE/eve.exe

Note if I have to patch I kill both clients and run
wine explorer /desktop=3,1280x1024 ~/.wine/drive_c/EVE/eve.exe


PS- I can't really speak to docking issues as I dock maybe 2 to 3 times a month. (worm hole dweller) I do find it's best to either shut off the station environment or get into ship spinning view. Running 2 clients walking in station is very taxing on your system.

Former forum cheerleader CCP, now just a grumpy small portion of the community.
Rastuasi
Crunchy Crunchy
#10 - 2012-02-06 02:04:24 UTC
Thanks for the tips, I tried the multiple wine folders, still does the same when even launching from them separately. As for station docking, well I use spin mode anyways.

In the end, I've converted to linux mint 12, only issue is the nvidia 290 driver is bad...won't reboot with it installed, so I have to stick to the restricted driver 280 they provide, thus I cannot launch captains quarters anyways. Dunno what would have changed with linux mint 12 when it's based off ubuntu, but at least I can launch 3 accounts again. Now if only I could figure out why cq makes the program error out..anyone else get that?

Thanks,
Rastuasi
Xorphix
School of Applied Knowledge
Caldari State
#11 - 2012-02-11 09:48:49 UTC  |  Edited by: Xorphix
I have to admit that wine on linux is starting to need some many quirks to be stable enough to PVP, currently I have:

* No sound, as it often crashes, I can run sound on one client stable, but multiple clients crashes
* Jukebox will often kill ur client
* Starting multiple clients at same time, will often load splash screen and then fallback to blue desktop
* Don't even get me started on patching..
* Some wine versions work, others doesn't, always a history of what works for you(TM)
* Walking in stations is just plain killing ur client. it works, it looks horrible, and its usually what crashes ur client

When patching, I download the latest patch from the Eve website into my homedir as "patch.exe", just replace the old one and run this script:

#!/bin/sh
START="C"+`date +%s`
LOGIN_NAME=`whoami`
env WINEPREFIX="/home/$LOGIN_NAME/.wine" nice -n 0 wine explorer /desktop=$START,1280x720 /home/$LOGIN_NAME/patch.exe
env WINEPREFIX="/home/$LOGIN_NAME/.wine2" nice -n 0 wine explorer /desktop=$START,1280x720 /home/$LOGIN_NAME/patch.exe
(and repeat for each wine)

When I have a client thats gone haywire, it usually have a ghost process in the background causing every wine within that wine directory to screw up also, which is why I have a killswitch:

#!/bin/sh
START="C"+`date +%s`
LOGIN_NAME=`whoami`
env WINEPREFIX="/home/$LOGIN_NAME/.wine" wineserver -k
env WINEPREFIX="/home/$LOGIN_NAME/.wine2" wineserver -k

Not sure if anyone can benefit from these :-)
Oh, I know I can use ~ instead of all that $LOGIN_NAME junk, but it was what was in the original script I stole from, never changed it ;-)