Macintosh

Back in March, we announced adding support for Wine as an alternative to Cider, the wrapper used to run the EVE client on OS X. The feedback we have received has been very positive, with most players reporting improved stability and performance.
We are now planning to stop supporting Cider in September, so we encourage everybody that hasn't done so already to switch to Wine. The latest launcher prompts you to make the switch to Wine, making this process quite straight-forward.

What is Wine?
As stated on www.winehq.org Wine is a compatibility layer capable of running Windows application on several POSIX-compliant operating systems, such as Linux, Mac OSX and BSD. Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods and allowing you to cleanly integrate Windows applications into your desktop.

Wine options
You shouldn't have to change any Wine options, and these may change at any time as we get feedback.
For now, the main option is what version of Wine should be used - we provide daily builds from the Wine git repository (git://source.winehq.org/git/wine.git). If you select 'Use dev versions' you can choose any of a number of recent daily builds, or to always use the latest one. If you leave the dev versions checkbox unchecked, you can select from stable builds that have had some testing.
The WINEDEBUG field allows you to set a value for the WINEDEBUG environment variable that controls debugging output from Wine. This can be useful for tracking down issues, but should in general be left empty.

What if it doesn't work?
Go to Preferences and select Cider for the wrapper, then everything should work as it did before. Please do tell us about it, either by posting in the feedback thread or by filing a bug report. Our goal is to improve the Mac experience and we need your feedback on this to do that.

EDIT: The last launcher update failed to persist the Wine preference - there is a second update where you may be prompted again - apologies for the inconvenience.

I'm having pretty much a faultless experience under wine , long may it continue.

i'm having the same problem with fixed window mode

Do you have a Retina display?

Mid-2011 iMac here, 3.4GHz i7. Graphics is AMD Radeon HD 6970M.

Game is super smooth on Cider - 45+ FPS with all graphics on and maxed except antialiasing. Switched to Wine, left defaults. Looked on in station, maybe a tad slower, but after undocking graphics run full speed about a second, pause, then run normal a second, then pause, etc. FPS counter actually shows "peaks" occurring at that time. The slight frame rate drop is disappointing but the glitching/pausing breaks the game. If you need additional logs/data please let me know.

Could you try running at a lower resolution, and lower graphics settings, in particular the post-processing and anti-aliasing? It sounds like it might be running out of memory, this would help confirm it. Please add this information to the bug report.

I updated from Cider to Wine today.

Fullscreen mode works great. It's noticeably faster and smoother on my macbook pro 15" retina at 2880x1800.

When I run windowed mode with a smaller resolution so that I can work with my other windows, the client begins to glitch. If I try to drag and move a window to reposition it, it will jerk and stutter as it moves across the screen. While in empty space, clicking in space and dragging it to reposition the camera will also display the same jerky stutter or shaking. One time, while moving the camera, it got stuck or something and the screen starting spinning in circles very fast until I tried to move the camera somewhere else. Very dizzy. I was unable to recreate this.

Going to fullscreen seems to resolve these issues instantly.

When changing desktops it minimises the client when in full screen mode

Yes, I have a Retina display

I tried it again, and switched the graphics to a lower setting, turned post-processing to low, and already had anti aliasing disabled. Changes took effect, and then the second I opened the map, the cursor was a question mark again, and the client locked up as before.

Tried again, found that everything was fine with the lower settings, until I opened the Map Beta. Crashed as before. Tried again, turned settings back up, tweaked a couple of things, and it ran just fine... UNTIL I opened the Map Beta. Then it instantly changed the cursor to a question mark and got the beach ball of death.

It seemed to be tied to the Map Beta. Every time I tried to access it when I am docked this happened.

BUT I realized that I have a gaming mouse with the default Ctrl + F10 for the Map Beta shortcut set to a button. So on a lark I changed that, in case there was a conflict of some sort.

When I changed the keystroke binding to something else and changed the command in EVE, the problem went away.

So somehow there was a conflict with the command using the mouse software and WINE. Should not happen, but it was happening.

EDIT: I have found that any mouse binding that includes a Function key in it causes the problem