[2019] How to configure the launcher for 64 bit version, How to configure the launcher for 32 bit version

The 64 bit version of the launcher requires wine-4.15-Staging-whinehq-binary-207 to work. If you run the 64 bit client while having wine-1.9.17-143-g91037ca-ccp-master-72 you will get an error stating that a file is missing from your bin folder. This is because the older wine version can only run 32 bit applications.

To configure the launcher for 64 bit version please do the following.

• 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
• Close the launcher and the client if either is running.
• In finder, click Go to Folder and copy paste the following

~/Library/Application Support/EVE Online/p_drive/Local Settings/Application Data/CCP/EVE/SharedCache

• You should see a folder named Wine – move that folder to trash.

To configure the launcher for 32 bit version please do the following.

• 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 NOT ticked.
• Make sure wine version is set to wine-1.9.17-143-g91037ca-ccp-master-72
• Click ok
• Close the launcher and the client if either is running.
• In finder, click Go to Folder and copy paste the following

~/Library/Application Support/EVE Online/p_drive/Local Settings/Application Data/CCP/EVE/SharedCache

• You should see a folder named Wine – move that folder to trash.

If you are trying to run the 64 bit version and your wine version is set to latest and the client is not starting then you may be encountering a bug where the latest is not updating automatically to the latest wine-4.15-Staging-whinehq-binary-207, if that is the case simply click on latest and change it to wine-4.15-Staging-whinehq-binary-207 and that issue should be resolved. After it works once I do recommend you switch to release as so that you get future updates to wine automatically (Once we fix the bug of course).

Hi Odama III

The reason you were able to use those shortcuts was because we added something called CCP-master which mimicked the Windows or PC behavior. Unfortunately ccp-master was causing a conflict with the 64 bit client and therefore we had to remove it. I’m not aware of any plans to address this at this time.

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.

I would try clearing your client side cache.

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.

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.

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

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 preference window and open again and switch back to latest. This is to fix those launchers that may be stuck on old wine versions that are no longer available.
• Click Ok.
• Close the launcher and the client if either is running.
• In finder, click Go to Folder and copy paste the following:
  “~/Library/Application Support/EVE Online/p_drive/Local Settings/Application Data/CCP/EVE/SharedCache”

You should see a folder named wine – move that folder to trash. Restart your launcher and wait for a few minutes for the launcher to update before starting the game again.

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.

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.

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 were locked the first time which is why that works if no client is running.

I finally managed to reproduce this issue. To resolve this issue I had to 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. 
Click Ok.
Close the launcher and the client if either is running.
In finder, click Go to Folder and copy paste the following:

“~/Library/Application Support/EVE Online/p_drive/Local Settings/Application Data/CCP/EVE/SharedCache”

Delete wine
Delete resfiles.  (be warned this will cause a big download on launcher restart )
Start launcher. Launcher should no longer allow you to start before wine has been downloaded.

I reproduced this a few times and then tried the fix in various ways, the workaround above resolved the issue. The error in log lite will be the following error.

Unknown
CryptAcquireContext
BlueOS::Startup(): InitVerificationContext failed
1 : blue.BlueOS: BlueOS::Startup(): InitVerificationContext failed

Post at the top has been updated with the latest data.