Macintosh

Since the release of Mosaic, I have noticed that if you start up a second instance of EVE for a different EVE account and subsequently exit that second instance the first instance of the game will lock-up.

Once this lock-up happens, you have to use Force Quit to stop the first instance. Even worse, all subsequent attempts to press the "Play" button on the launcher seem to do nothing at all. The animation of the Play button changes to "Launching...", but nothing at all happens. This even happened after stopping and starting the launcher.

At first, I discovered that rebooting the Mac would then allow the Launcher to actually start the game and used this solution at first to fix the problem. Unfortunately, this started happening so often that rebooting was becoming annoying.

I then started digging into the issue a little more and discovered something interesting in the ~/Library/Application Support/EVE Online/ directory. I found multiple subdirectories with names that started with "wineserver-" that had just two files in them: "fd-socket" and "socket". On a dangerous whim, I deleted all of the directories that started with "wineserver-" and was immediately able to start the game from the launcher.

It would seem that the information in these wineserver-* directories can become corrupted for the first instance of Eve when you start and then subsequently exit a second instance of EVE for a different EVE account.

Please let me know if this work-around is as dangerous as it seems to be and take this information as clues to why these types of lock-ups and subsequent refusals to launch occur.

Here is a step by step procedure that occasionally causes this situation to occur and my dangerous work-around:

1. Start up Launcher and log in with user account X and then press Play
2. Choose your character from account X and play EVE for a while
3. Without shutting down the game for account X, return to the Launcher and switch accounts to account Y
4. Choose your character from account Y and play EVE on that Y character while you also play EVE on the X character
5. Exit the game for the Y character normally
6. Return to the X character game to find that the game is no longer responding to commands
7. Kill the X character game using OS X "Force Quit..." functionality
8. Restart the Launcher and log in with user account X and then press Play
9. Realize that the game didn't get launched even though the Launcher Play button animation changed to "Launching..."
10. Realize that no matter how many times you click the Play button that the game just isn't going to launch
11. Using OS X terminal, type the following dangerous BASH command:

rm -rf ~/Library/Application\ Support/EVE\ Online/wineserver-*



12. Press the Play button on the launcher and watch the game launch normally.

Thanks,

Hoeveer Parmala

This has been working this way for a long time. Closing the client kills the wineserver process, rendering all other open clients that depend on it frozen. Easy workaround is to click on the client window you want to close, hit Option+Command+ESC, brings up the task kill list, just kill the highlighted EVE process. It won't kill the others. If you shut them down this way, you won't freeze the others.

this doesn't work anymore. It looks like it works for a moment but then you click on the other client to get back to playing and it freezes. What's also new is the unresponsive launcher.