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.
 

New EVE Launcher in testing on Singularity

First post
Author
Ravow
Quebecorp
Removal
#81 - 2013-05-21 19:53:37 UTC
Fixed.

Bash script who check current version and installed version.
If version is not the same, run repair.exe and after, exefile.exe.
If version is the same, just run exefile.exe

no more launcher.
Veldar Reku
Wu Xi Holdings
#82 - 2013-05-21 19:55:07 UTC
The new launcher works just fine with Wine.

$ wine --version
wine-1.5.25

If you are getting connection timeouts, it has nothing to do with Wine. Wait a while for update servers to become less overloaded (so they don't time out), or use Chribba's workaround that seems to have worked for some.

Now, I think the login in launcher is a little over the top, but maybe CCP wants a unified login UI code for something. Not sure what. Generally, you can have unified login infrastructure as an API component separate from the UI code. Model/View separation and all that jazz..
Torgeir Hekard
I MYSELF AND ME
#83 - 2013-05-21 20:02:04 UTC  |  Edited by: Torgeir Hekard
Torgeir Hekard wrote:
Launcher fails to start after update with the error "could not load python.dll"


UPD:

Installed PlayOnLinux. Installed wine 1.5.30 with it. Didn't bother installing EVE in PlayOnLinux and just used the updated wine version to start the repairer. On the second try it worked and corretly patched the client.

Launcher still welps with python error with wine 1.4, but works with 1.5.30. Once. Then you need to clear it's cache or get a broken window (the login part).

Launcher still tries to kill my CPU. Possibly related to this funny stuff:

it starts with fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
followed by err:ntdll:RtlpWaitForCriticalSection section 0x7bcb3ae0 "rtl.c: peb_lock" wait timed out in thread 0036, blocked by 002c, retrying (60 sec) (several different threads. About 8)
and finally ends with err:seh:setup_exception_record stack overflow 1248 bytes in thread 003e eip 7bc401ef esp 08610e50 stack 0x8610000-0x8611000-0x8710000 (again, about 8 different threads)

PS: seems all the threads are waitinng for something blocked by the thread 002c and then welp.
Karti Aivo
KarmaFleet
Goonswarm Federation
#84 - 2013-05-21 20:07:37 UTC
Oh Thanks for a launcher that even locks me out of my windows machine <3

clearly you had to ship this and there was no way around!
Doublewhopper
Temporary Assignment
#85 - 2013-05-21 20:08:59 UTC
Veldar Reku wrote:
The new launcher works just fine with Wine.

$ wine --version
wine-1.5.25

If you are getting connection timeouts, it has nothing to do with Wine. Wait a while for update servers to become less overloaded (so they don't time out), or use Chribba's workaround that seems to have worked for some.

Now, I think the login in launcher is a little over the top, but maybe CCP wants a unified login UI code for something. Not sure what. Generally, you can have unified login infrastructure as an API component separate from the UI code. Model/View separation and all that jazz..


I use wine-1.5.27 and the launcher is just a white box with a button to close it.

In the background firefox tries to reach a website which it cannot open.

No matter how long, the launcher stays a white box.

Do i have to change my dll overrides or install anything else?
Sentinel Eeex
Thunderwaffe
Goonswarm Federation
#86 - 2013-05-21 20:39:20 UTC  |  Edited by: Sentinel Eeex
Tried pretty much everything I could (or what was suggested here or elsewhere), for past few hours. No luck on Ubuntu 12.04 and wine from Wine Team PPA (1.5.30).

When running launcher, I get the "offline" screen, when running eve.exe directly, it just hangs and nothing ever happens.

I'd really like to find out, though, who was the genius that decided to notify players about this major upgrade 5 minutes before the upgrade.

Real ******* genius.

edit: seems like whining helps, managed to get the launcher login screen and start the game after 50+ tries, so it would appear updated version still works on Linux (at least on mine).
Anun Hen
Perkone
Caldari State
#87 - 2013-05-21 20:51:18 UTC  |  Edited by: Anun Hen
well, derp ... it worked. Once.

the launcher just updated itself, validated the client, and launched the game.
~That was the 1st time.
Now, on the 2nd time, the field on the left to enter your username/password and then click play does not show up.


Instead, I have the following show up:


so, who knows why it worked once but not after anymore :itsamistery:

Ok, it's still possible to launch the client directly (located in Program Files/CCP/EVE/bin/ExeFile.exe) and bypass the launcher.
Obviously not for long, since somebody has to justify his existence at CCP by forcing down his launcher on everybody.

And now, getting that perma error 7 crap, even after clearing cache etc etc
So, why did this work fine the 1st time but never again after?
Woo Mi
Federal Navy Academy
Gallente Federation
#88 - 2013-05-21 21:01:16 UTC  |  Edited by: Woo Mi
Success. somewhat...
Wine 1.4
Ran launcher with:
#!/bin/sh
# client : b,n
# patcher : n,b
export WINEPREFIX="$HOME/.wine_eve_0"
#export WINEDLLOVERRIDES="*msvcr100,*msvcr90,*msvcr80=b,n"
export WINEDLLOVERRIDES="*msvcr100,*msvcr90,*msvcr80=n,b"
export WINEDEBUG=-all
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8
wine explorer /desktop=0,1920x1200 "C:\Program Files/CCP/EVE/eve.exe"

This seemed to update the launcher and the game.
However, I couldn't start the game via the launcher with the b,n settings.
To be sure, I ran Chribba's script, and after that I was able to run the client directly with:

#!/bin/sh
# client : b,n
# patcher : n,b
export WINEPREFIX="$HOME/.wine_eve_0"
export WINEDLLOVERRIDES="*msvcr100,*msvcr90,*msvcr80=b,n"
#export WINEDLLOVERRIDES="*msvcr100,*msvcr90,*msvcr80=n,b"
export WINEDEBUG=-all
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8
wine explorer /desktop=0,1920x1200 "C:\Program Files/CCP/EVE/bin/ExeFile.exe"

Questions:
Should I update to wine 1.5.30?
What do I need to do to provide debugging info to anyone who has a clue about the workings of wine?
Doublewhopper
Temporary Assignment
#89 - 2013-05-21 21:01:57 UTC
They updated the launcher. It works now also with Linux.
Doublewhopper
Temporary Assignment
#90 - 2013-05-21 21:10:08 UTC
Have to invalidate my last statement.

It worked for me once. Now i can't get the login fields and the button to appear...otherwise the launcher seems to work.
Marsan
#91 - 2013-05-21 21:10:45 UTC
Sigh it's going to fun documenting the various ways this breaks various versions of wine on wine hq... Thankful I have a 2 week skill slotted.

Former forum cheerleader CCP, now just a grumpy small portion of the community.

Anun Hen
Perkone
Caldari State
#92 - 2013-05-21 21:11:30 UTC  |  Edited by: Anun Hen
Doublewhopper wrote:
Have to invalidate my last statement.

It worked for me once. Now i can't get the login fields and the button to appear...otherwise the launcher seems to work.


Same, it works ONCE.
Then after that, you get that error -7 message.
Even after clearing cache etc

Also:

Ok, it's still possible to launch the client directly (located in Program Files/CCP/EVE/bin/ExeFile.exe) and bypass the launcher.
Obviously not for long, since somebody has to justify his existence at CCP by forcing down his launcher on everybody.
Marsan
#93 - 2013-05-21 21:16:03 UTC  |  Edited by: Marsan
If the launcher is not working try running ExeFile.exe in {your eve dir}/bin. ( generally C:\Program Files\CCP\EVE\bin )

If the above doesn't work try the repair tool.
( generally C:\Program Files\CCP\EVE\repair.exe)
http://wiki.eveonline.com/en/wiki/Client_Repair_Tool

PS- Also note that the launcher appears to be borked for Windows too.
http://evenews24.com/2013/05/21/eve-launcher-support-thread/

Former forum cheerleader CCP, now just a grumpy small portion of the community.

Anun Hen
Perkone
Caldari State
#94 - 2013-05-21 21:25:52 UTC
If we can get that Error -7 issue fixed, we would be back in business
what puzzles me is why it works perfectly the 1st time and never again after that.
Neuntausend
GoonWaffe
Goonswarm Federation
#95 - 2013-05-21 21:37:49 UTC
Anun Hen wrote:
If we can get that Error -7 issue fixed, we would be back in business
what puzzles me is why it works perfectly the 1st time and never again after that.



It does seem to work one out of ten times after the first launch. But I am with the Devs here, it's most likely a wine problem. Since the thing is live now, maybe someone should go and issue a bug report? I would do it myself but that would take effort.

I might still do it at some point if none of you is less lazy than I am.
Anun Hen
Perkone
Caldari State
#96 - 2013-05-21 21:45:51 UTC
Neuntausend wrote:
Anun Hen wrote:
If we can get that Error -7 issue fixed, we would be back in business
what puzzles me is why it works perfectly the 1st time and never again after that.



It does seem to work one out of ten times after the first launch. But I am with the Devs here, it's most likely a wine problem. Since the thing is live now, maybe someone should go and issue a bug report? I would do it myself but that would take effort.

I might still do it at some point if none of you is less lazy than I am.


going to bed now, our fate is in your hands :we're######:
took me 8 tries to get it to work (i.e. not show the error 7), so it CAN work, it's just temperamental
Arduous Nolen
Renumerative Endeavors
#97 - 2013-05-22 00:12:45 UTC
Seems like there are problems all over with the new launcher. I was stuck with the "Error -7" as well , until running the client directly:

wine "C:\Program Files (x86)\CCP\EVE\bin\ExeFile.exe"

Running fine with Ubuntu 12.10, wine 1.5.29.

Let's hope they get this fixed before anyone gets bright ideas about removing login from main executable.
Torgeir Hekard
I MYSELF AND ME
#98 - 2013-05-22 02:51:06 UTC
Okay, seems like the dreaded Error -7 is, indeed, random and not connected with clearing the launcher cache. Which is kinda good because I don't need to clear the cache, but kinda bad, because I don't have control over it.

There is another problem, though.

The new launcher breaks the logic behind virtual desktops. That is, I can't spawn multiple instances of eve online in different virtual desktops from one launcher.

Therefore, when using launcher, to get different virtual desktops it's required to start multiple instances of launcher (with "close after game launch" option). Naturally, only one instance of launcher can be run at a time. Naturally, it can't close properly, because the threads are left in gridlock for a minute after closing the launcher. Which leads to the fact that you can only start the client once a minute. Those that hate multiboxers should probably rejoice at this point.

Why do we even need a multithreaded launcher? Does it participate in Folding @Home or something?
Midnight Hope
Pator Tech School
Minmatar Republic
#99 - 2013-05-22 03:00:07 UTC
Doublewhopper wrote:
Have to invalidate my last statement.

It worked for me once. Now i can't get the login fields and the button to appear...otherwise the launcher seems to work.


Same issue here. The launcher validates everything ok, but the username/pswd and "login" button don't show up. Something is scrcewed up with the way it displays them.

Torgeir Hekard
I MYSELF AND ME
#100 - 2013-05-22 03:17:05 UTC
Midnight Hope wrote:
Doublewhopper wrote:
Have to invalidate my last statement.

It worked for me once. Now i can't get the login fields and the button to appear...otherwise the launcher seems to work.


Same issue here. The launcher validates everything ok, but the username/pswd and "login" button don't show up. Something is scrcewed up with the way it displays them.



It's the Error -7. It's just written in invisible letters. You can see it by selecting the text.