|
Author |
Thread Statistics | Show CCP posts - 18 post(s) |
|
CCP Atropos
C C P C C P Alliance
213
|
Posted - 2013.05.07 15:00:00 -
[1] - Quote
HI guys, just a heads up regarding incoming changes that we're working on for the EVE Launcher. Whilst the usual caveats apply regarding supporting Linux, I would appreciate it if you could give it a whirl, and let me know if there's anything that could be an easy fix.
Here's the thread in the Test Server forum. Product Owner, EVE Launcher | Team Special Circumstances |
|
|
CCP Atropos
C C P C C P Alliance
219
|
Posted - 2013.05.07 15:45:00 -
[2] - Quote
That's not the new Launcher though. Please read the first post in the thread I linked.
The version you're using is v.1.32 which is NOT v.2.1.528861-beta.3. Product Owner, EVE Launcher | Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.14 10:36:00 -
[3] - Quote
Posting this here as well since it is most likely of interest to you:
It might be worthwhile trying to replace the certificate file found in the (launcher path)/appdata/EVE_Online_Launcher-2.1.(version)-beta.3.win32 folder with a more recent one, for example with the one located at http://curl.haxx.se/ca/cacert.pem - hope this helps. :-)
The reason is that the certificate file we were shipping up to now seems to have some issues on Mac. Senior Programmer Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.14 15:29:00 -
[4] - Quote
We know that we might have a bit higher usage than before temporarily because there are some more threads that are running but it shouldn't be overly silly (though Python's threading module is annoyingly greedy it appears). It certainly shouldn't be at 100% as it was mentioned in a previous post, though. Senior Programmer Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.14 16:45:00 -
[5] - Quote
Mikail Thiesant wrote:Tested the new launcher 2.1.534643-beta.3 The -7 error is unfortunately still there. launcher.log http://pastebin.com/mWhHXHbxdebug.log was not created this time.
Sadly the logs show nothing. However, since we had similar issues on the Mac (which was then resolved using a different certificate bundle) I'll look into whether we can get more useful logging out of chromium embedded for these situations which should help us gaining some insight on what exactly might be going on there. Senior Programmer Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.14 17:56:00 -
[6] - Quote
Mr M wrote:CCP Aporia wrote: After some more digging about in the source code for the browser engine then it turns out that Error: -7 indicates that there was a time out in the underlying SSL connection. Why exactly that happens is currently unknown to me, but if I find something I'll let you know. What Windows versions are you guys running in Wine?
1.5.27 here at the moment. I find it odd that it's only the iframe with the login button that times out and never the rest of the launcher window.
I find that odd as well. It would be really great to see how normal chrome would run in wine with our landing page, but if I remember correctly from the other thread that's not easily doable?
And about the cpu usage, I'll increase the sleep duration in each thread but there might be something else going wrong since none of the threads should run at more than 100 Hz and that should rarely, if ever, cause enough load for 100% CPU usage on a single core given the amount of work that is actually being done by the launcher. Senior Programmer Team Special Circumstances |
|
|
CCP Atropos
C C P C C P Alliance
224
|
Posted - 2013.05.14 23:15:00 -
[7] - Quote
The login dialog is handled in an iframe, and so might be reporting differently against the embedded images (which are also HTTPS) failing to load. What's interesting is that the Python layer (and it's SSL handling) doesn't have this error, indicating that the problem might exist in a wine library outside of our control. The embedded webpage must be HTTPS to allow the login to occur in a secure context.
What I don't understand however, is why it's only an intermittent error. Product Owner, EVE Launcher | Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.15 13:52:00 -
[8] - Quote
Katrina Bekers wrote:In WINE we can select which version of Windows we present to the programs. IIRC, they can go from 95/98 all the way to 8.
Is there a particular target you devs are looking for? I guess XP and 7 should be the most common ones, with Vista and 8 trailing a bit behind...
I-¦d recommend to run at least Vista, though XP should work just fine as well. Senior Programmer Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.15 13:54:00 -
[9] - Quote
Kontalaa wrote:Wine HAD problems with HTTPS (only accepting one cert and unable to check the cert-line invalidating the auth of the site called). This was fixed long ago with a manual patch - however they didnt want to push it upstream because it looked too much reverse-engineered from MS-Code. Seems like another (similar) patch has been submitted in the last weeks. For me (Ubuntu 13.04, Wine 1.5.29) the IGB with SSL works: http://pwning.de/stuff/eve/httpsIGB.png[...]
The launcher is not using the same browser framework as the IGB does, so there are differences in how some things are handled. Senior Programmer Team Special Circumstances |
|
|
CCP Atropos
C C P C C P Alliance
224
|
Posted - 2013.05.16 10:58:00 -
[10] - Quote
Eoras Northwind wrote:Launcher is still v.1.32 as of this report. openSUSE 12.3, 319.17 nvidia driver with wine 1.5.30 from Open Build Service Games channel. If it reports as v.1.32 then it's the old Launcher. If you're connecting it to Sisi then it's simply the old Launcher with the new landing page.
Eoras Northwind wrote:With the patches between the 12th and 15th of May the launcher/updater went from missing large amounts of imagery to functioning mostly as it does under Windows 7 including loading animations. My desktop distribution's nightly wine packages were also updated to 1.5.30 in that time, so this confounds my testing.
The buddy offer window in the lower corner of the launcher alternates between broken and visible with logins. The links do properly fire off to your default desktop browser, though. As I said above, this is only the webpage display; you're apparently still running the old Launcher
Eoras Northwind wrote:If you use a virtual desktop in Wine. the minimal 800x600 window is too small for the new launcher. At least 1024x768 desktop resolution is needed with this launcher. I think 1024x768 is the minimum size for EVE so I don't know why you would ever be running at 800x600 and be expecting normal performance anyway.
Eoras Northwind wrote:Closing the launcher will leave graphics artifacts until it completes closing. Visible tearing is also seen when dragging the launcher around with the mouse.
I have noticed increased load due to the Test server launcher maxing out two of my desktop cores. The load on the GPUs was high enough to spike temperatures, but not enough to raise the PowerMizer settings from lowest. The temperature spike was only on the graphics card for the display the launcher was using and followed if restarted on a different one. The processes match those reported by others, a pair of launcher.exe processes. This is not seen with the TQ client.
There are never any logs reported by any running logserver for the launcher. Regarding logs, the LogServer.exe is only for the game client. The Launcher logs into a folder called cache, under the launcher folder. Product Owner, EVE Launcher | Team Special Circumstances |
|
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.16 13:33:00 -
[11] - Quote
Fair enough, I don't know about the specifics of Wine. Even though I do run only Ubuntu boxes at home then I never had any need to actually run Windows things on them. :-) It is kind of curious that there are apparently hardly any differences within Wine, because I know for a fact that some of the Windows APIs we are using behave very differently between the different Windows versions. Senior Programmer Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.16 14:45:00 -
[12] - Quote
Sipphakta en Gravonere wrote:
Try clearing the browser cache folder in the launcher directory. If that doesn't help then I am a bit at a loss, the log files look good though. Senior Programmer Team Special Circumstances |
|
|
CCP Atropos
C C P C C P Alliance
224
|
Posted - 2013.05.16 15:51:00 -
[13] - Quote
If you're able to login, it should show you the EULA. Product Owner, EVE Launcher | Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.17 14:44:00 -
[14] - Quote
Karti Aivo wrote:CCP Aporia wrote: And about the cpu usage, I'll increase the sleep duration in each thread but there might be something else going wrong since none of the threads should run at more than 100 Hz and that should rarely, if ever, cause enough load for 100% CPU usage on a single core given the amount of work that is actually being done by the launcher. I really hope this get fixed before this launcher is shipped, or at least theres an option for the old launcher then since that one is working pretty fine. On a sidenote i cant really get why you would build a LAUNCHER that consumes more ressources than the actual game itself on min. settings.
That's because of whatever wine does. My Mac Mini sits at 2.1% CPU, my Windows at 0%. This is mostly because multi-threading in Python is expensive, it performs a ton of system calls to check the GIL. Now in the case of the native windows and mac environment that is a heavy, yet insignificant prize to pay for keeping the UI responsive. However, in the case of running in Wine that seems to get worse because Wine needs to translate those Windows system calls to whatever Linux is using.
I do agree that this is not an optimal situation but it's an acceptable one for us. Rewriting the launcher in something else than Python does currently not make a lot of business sense - and trust me, I want to do it because f.e. our memory consumption is way too high and the start up times is way too slow, IMHO. This may or may not change depending on how the market evolves (and even then a native python client would perform a lot better than running inside Wine), but for now I'll have to refer you to the Wine guys and ask them what exactly it is that makes the launcher so super expensive in their environment. Senior Programmer Team Special Circumstances Friend of Walking Avatars |
|
|
CCP Aporia
C C P C C P Alliance
74
|
Posted - 2013.05.17 17:56:00 -
[15] - Quote
Nebu Retski wrote:CCP Aporia wrote:(and even then a native python client would perform a lot better than running inside Wine) Why don't you just make a native python client. Python is cross-platform so it should be possible for you to do this. All we need is for you to add a extra entry for us where we can put our client launching command into it.
Because Linux is not an officially supported platform and that makes it impossible for our team to justify spending time on it. While python runs perfectly fine on Linux, then the lesson we learned from Mac OS is that there are a lot of special cases that we need to take care of for each operating system. Starting with where the EVE client lives, where it stores its settings, etc. on to some non-standard python libraries we are using that would require porting and compilation (for which Linux distribution? Would Ubuntu be sufficient?). Since none of us on the team has EVE running under Wine (at the moment) then it is near impossible to deal with those issues.
That being said we're looking into low hanging fruit that might crop up with the launcher on Linux, but it's things like this SSL timeout (Error -7) where we simply cannot justify spending time on it when it's not straight forward. Senior Programmer Team Special Circumstances Friend of Walking Avatars |
|
|
CCP Atropos
C C P C C P Alliance
224
|
Posted - 2013.05.17 21:18:00 -
[16] - Quote
For the immediate future your LInux based experience will still function acceptably; even though Wine fails to handle multi domain SSL connections. The EVE client can still be started, and logging in can still be accomplished there, much as you currently do.
However, since our goal is to allow alternative authentication methods, and those are designed to be implemented via web-services, at some point in the future the in-client login methods will be removed. There's no ETA for this at this time, but I am aware of the effect this would have on the EVE Linux community.
I can't promise that we will be able to fix these issues, since they appear to be fundamentally broken in Wine, but given that we're having this very discussion should point out that we're at least aware of the issues the new EVE Launcher experiences on Linux, even if we're not able to address them.
Product Owner, EVE Launcher | Team Special Circumstances |
|
|
CCP Aporia
C C P C C P Alliance
88
|
Posted - 2013.05.21 18:43:00 -
[17] - Quote
Karak Terrel wrote:The general problem seams to be that the webservers which deliver the configuration and the html for the launcher respond very slowly. They eventually respond, but the launcher timeouts way before that. So I installed a local squid proxy to cache the needed sites locally. However if i start the laucher now I just get a python traceback. Not sure now if that is because of the proxy settings or because of some other stuff. http://pastebin.com/raw.php?i=7KxcViiE
The webservers are still under heavy load and thus it occasionally times out getting that information. This is a general problem at the moment. Senior Programmer Team Special Circumstances Friend of Walking Avatars |
|
|
CCP Atropos
C C P C C P Alliance
308
|
Posted - 2013.05.31 11:00:00 -
[18] - Quote
Nebu Retski wrote:Frazier wrote:Valencia Mariana wrote:Frazier wrote:Can someone from CCP tell us whats your schedule for removing the ingame sign on, please? Because if this is removed we will be unable to sign on. And I doubt that there will be much change in regards to the launcher until then.
Will we be able to play after Odyssey or should I cancel my account right away. Hope not, just returned to EVE after half a year. This please. Here is a response from CCP: https://forums.eveonline.com/default.aspx?g=posts&m=3078762#post3078762 What a bullshit response. "It won't be before Odyssey", that's not an anwer to the question that was asked. Bloody hell if you don't already know if it will be for Odyssey or not, then maybe that's a sign that whatever you had in mind of doing is most definately NOT ready and thus should NOT be shipped. Or it could be that it's a dependency that involves several teams changing many layers of our logon tech stack at the same time, and that to specify a date now, would be giving people a date which might very well change. Product Owner, EVE Launcher | Team Special Circumstances |
|
|
|
|