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

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

Test Server Feedback

 
  • Topic is locked indefinitely.
 

Another variety of "Can't get onto SiSi"

First post
Author
Previous Topic Next Topic
MisterNick
The Sagan Clan
#1 - 2012-03-02 15:49:00 UTC  |  Edited by: MisterNick
Autopatching: Fine
New Launcher: Opens successfully.

While the new launcher window does open, it is determined to connect to TQ according to the Server & Status display. This issue did not crop up before this new launcher. It doesn't actually matter about this, however, since the client crashes every single time before even making it to the login screen.

I've run the repair tool numerous times, even made a new copy of my TQ and updated to current SiSi patch (that took a while), still same result of client crash before login screen.

Any ideas?

EDIT:

Running the Windows client on Vista 32-bit

"Human beings make life so interesting. Do you know that in a universe so full of wonders, they have managed to invent boredom."
Palovana
Inner Fire Inc.
#2 - 2012-03-02 16:37:56 UTC  |  Edited by: Palovana
I was getting the same thing under Wine 1.4rc5 this morning, the window title was "Microsoft Visual C++ Runtime Library" and the error text was:

Runtime Error!
Program: C:\Program Files\CCP\Singularity\bin\ExeFile.exe

abnormal program termination

[OK]

Edit: the launcher displays TQ, its status and user count but actually did connect (in previous builds) to Singularity. Using the Launcher repair tool patched my Sisi install back to the TQ version and required me to re-patch to Sisi version which still fails in the same way displayed above.

Please support: export of settings in editable format

Your stuff goes here.
CCP Habakuk
C C P
C C P Alliance
#3 - 2012-03-04 16:43:03 UTC
Hi! For the case, that you are using old Radeon cards (for example the Radeon X1600): We know about a crash at loading of the login-screen, which should hopefully be fixed with the next patch on Singularity.

If this crash happened with any other configuration: Please send a bug-report and include logs and the crash dump.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
MisterNick
The Sagan Clan
#4 - 2012-03-04 18:42:04 UTC
CCP Habakuk wrote:
Hi! For the case, that you are using old Radeon cards (for example the Radeon X1600): We know about a crash at loading of the login-screen, which should hopefully be fixed with the next patch on Singularity.

If this crash happened with any other configuration: Please send a bug-report and include logs and the crash dump.


As it happens i'm using the X1550, so sounds like i'll be sorted after the next patch.

Thanks Habakuk Cool

"Human beings make life so interesting. Do you know that in a universe so full of wonders, they have managed to invent boredom."
Palovana
Inner Fire Inc.
#5 - 2012-03-05 18:26:41 UTC  |  Edited by: Palovana
CCP Habakuk wrote:
Hi! For the case, that you are using old Radeon cards (for example the Radeon X1600): We know about a crash at loading of the login-screen, which should hopefully be fixed with the next patch on Singularity.

If this crash happened with any other configuration: Please send a bug-report and include logs and the crash dump.


Build 346707 is now on Sisi, and I am using NVidia rather than ATI.

The crash is not occurring within the launcher, as the Program Files/CCP/Singularity/launcher/cache/launcher.log file contains no crash information, only a "successful" run of the launcher.

I'll fire up the LogServer and try it again and attach that to a bug report.

EDIT: Bug report # 129374

Please support: export of settings in editable format

Your stuff goes here.
Buzzy Warstl
Quantum Flux Foundry
#6 - 2012-03-05 19:16:11 UTC
For the Wine case, perhaps this is what you are looking for (from the debug.log file, also nVidia):
[0305/093402:ERROR:network_change_notifier_win.cc(111)] WSALookupServiceBegin failed with: 8

Nothing else in any of the usual logging locations on my system.

http://www.mud.co.uk/richard/hcds.htm Richard Bartle: Players who suit MUDs
Palovana
Inner Fire Inc.
#7 - 2012-03-05 20:20:11 UTC
Buzzy Warstl wrote:
For the Wine case, perhaps this is what you are looking for (from the debug.log file, also nVidia):
[0305/093402:ERROR:network_change_notifier_win.cc(111)] WSALookupServiceBegin failed with: 8

Nothing else in any of the usual logging locations on my system.


Actually I found THIS and sure enough, setting *msvcr100 to BUILTIN in my winecfg fixed it (no need to use "winetricks vcrun2010" or similar either).

Please support: export of settings in editable format

Your stuff goes here.