GM_Mechanic

Clearing the client cache files should not affect this since the client is crashing. However the shared resource cache may be corrupt. I would run the verify option in the launcher.

• Start the Launcher
• Click on the cogwheel in the bottom left corner of the launcher window.
• Click on the Reset Options & Cache tab
• Click on the Shared Cache Settings.
• You may see some progress in the bar at the bottom. Once its completed its task please click on the ‘Verify’ button and the verification process will begin.

You most likely have a fixed window size. You will have to change to windowed mode or delete the config file you may have used to set a fixed window size for the client.

It’s possible that this issue is caused by cookies saved on your computer. To delete the cookie files please follow the steps below:

• Press and hold the Windows key on your keyboard while pressing R (this will open a run window).
• Copy and paste the following line into the run window: %LOCALAPPDATA%\CCP\EVE\
• You should see a few folders there. One should be named QtWebEngine
• Open that folder. Then open Default.
• Delete the two of the files in there. Cookies and Cookies-journal.

Then try logging in again.

We have been communicating with the developers regarding the issues that have affected MacOS users, and we are happy to let you know that these issues should now be resolved with the latest version of wine and this is considered to be a permanent fix to these issues rather than any previously provided workarounds.

This latest update should ensure compatibility with the 64 bit version of the client, resolve any issues with the client not starting properly or repeatedly crashing as well as that the game should continue to work after updating to Catalina.

For this change you will need to change your wine to the latest version. To do this please do the following:

• Start the launcher.
• Click on EVE launcher in the apple menu at the top left corner of the screen.
• Select preferences.
• Enable ‘Run clients with 64 bit’.
• Make sure that ‘Use Dev version’ is not enabled.
• Make sure wine version is set to latest. If it is alread...

Please also ensure you meet the minimum requirements, for example 64 bit version requires Mac OS X 10.12 or later.

This error means you are trying to run a 64 bit client on a 32 bit wine. You need to either switch your client to 32 bit or switch your wine to wine-4.15-Staging-whinehq-binary-207

Start launcher
Click on EVE launcher in the apple menu at the top of the screen
Select preferences.
Make sure Run clients with 64 bit is ticked.
Make sure wine version is set to latest or wine-4.15-Staging-whinehq-binary-207
Click ok

This might be because the client is running out of memory. I’ve not been able to reproduce this on my side though.

The workaround would then be to lower your resolution. 1920*1080 is the highest resolution supported for EVE Online. The higher the resolution the more memory the client will consume.

We are aware of this issue and it is being looked into. In the meantime I suggest you switch to 32 bit client.

That could be a permission issue. The launcher may not have the correct privileges to save its settings. Try starting the launcher up in admin mode and then save the settings.

Right click EVE Online icon,
Select Run as Administrator.

That’s because the 32 bit client can only use 3.6GB of your computers available memory while the 64 bit client can use all available memory.

The above solution does not have anything to do with the 64 bit client freeze issue. It only helps with the issue were players are getting Client launch failure error.

Only workaround for the 64bit client freeze I’ve found so far is running the 32 bit client. wine-4.15-Staging-whinehq-binary-207 should work with both 32 bit and 64 bit.

It’s most likely unrelated, I have now reproduce the issue with the 64 bit client freezing, so far the only workaround seems to be switching to the 32 bit client. We are aware of this issue and we are currently investigating.

This means that your launcher failed to connect to launcher.eveonline.com, and is usually a network issue. You should be able to resolve this with a restart. If it still does not work you can try clearing the launcher cache.

• Please open the Finder and press the Cmd key and , key to open Go To Folder.
• Copy and paste the following into the Go To Folder text box and press enter.

~/Library/Application Support/CCP/EVE/Qt/WebEngine

• Right click on the folder named ‘default’ and select move to trash.
• Start the launcher and see if the issue persists.

If the issue still persists I would try waiting awhile and then try again, as it’s most likely a network issue in your area which hopefully resolves itself.

Some Ethernet cards have ...

This issue occurs when you have a 32 bit wine but try to run a 64 bit client. To resolve this issue either switch to a 32 bit client or change the wine version to either latest or wine-4.15-Staging-whinehq-binary-207

If it is already on latest then it has failed to update correctly in which case changing to wine-4.15-Staging-whinehq-binary-207 will allow you to run the 64 bit client.

You can find instructions on how to change wine here:

Ah ok I misunderstood. I think that is a wine error, deleting wine and wait before clicking play. There is a bug that may allow you to start a client before it has finished downloading wine, if that occurs then the client will nuke it’s own wine install causing all kinds of weird errors like the one posted above.

Not possible, it was updated 2 days ago. The previous version that was published more then a month ago was wine-4.4-staging-xxxx, the current version is wine-4.15-Staging-xxxxx, please try switching to wine.4.15 and delete wine emulator like I explain in my post then restart and see if that does anything for you.

Try my Configure launcher for 64 bit guide:

The highest supported resolution is 19201080, if your resolution is higher then that try lowering it to 19201080 and see if the issue persists. If it does try lowering it even more and see if the issue persists. Might be a memory issue, especially if your running the 32 bit client. The bigger the resolution the more memory the client requires.

I would try clearing your client side cache.

Workaround would be to not use a Magic mouse and instead use a mouse with two buttons. And there might be some other tricks you can use that some Advanced Mac users might know, but I’ve not researched those yet.