Black screen behind UI Elements is a known issue and being looked into, is not related to wine as it is also occurring for Windows users.

The issue with starting clients after deleting wine occurs only if you start the client before the launcher has downloaded and updated wine (this is a bug, you’re not supposed to be able to). Switching between 32 and 64 will effectively cause then launcher to update the files ...

That most likely means your wine install is corrupt. Either reinstall EVE from scratch or delete the wine folder in the shared resource cache folder called sharedcache.

That most likely means that wine got corrupt. I recommend you delete the wine folder and then start the launcher. Wait at least 10 minutes before logging in or hitting play. Otherwise you may lock files in place before the launcher has updated. Causing wine to get corrupt again.

The server determines when the object is destroyed not the client you are using. So the overflow you see is simply latency between your client and the server, but if you actually manage to lose ammo on an empty shot then that would be a bug and you should file a bug report about it.

Please note that bug reports are generally not a two-way communication. Your report will be reviewed by the Quality Assurance team and if they require any further information they will respond. If however the information you provide is sufficient for them to investigate then generally they will not contact you or respond to the bug report.

Should work now with latest wine 4.17, did on my imac. No issues so far.

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.

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.

Remove all accounts from the group. Then add them in the order you want them.

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 already on latest switch to wine-4.17-Staging-winehq-binary-208, close the prefe...

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.

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

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.

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

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.

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 automatic power settings available in an attempt to save energy. In some cases, these low-power settings, such as sleep mode can interfere with the launcher connecting if the net card does not wake up in time. In which case a launcher restart should resolve this as...

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: