Macintosh

I seem to be getting a lot of DC's goin thru gates in large fleets. The odds seem to be almost 50%...
Client performance is slow and very laggy, even with brackets all off and graphics set to lowest, i had like 1 FPS...

This basically means null sec blob pvp is impossible for me as things stand.

MBP early 2011
Processor 2.3 GHz Intel Core i7
Memory 8 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6750M 1Gb RAM

ps. anyone running this with bootcamp / parallels? can u share ur experiences?

The random freezes continue to be random; most of the time I'm fine but this last Saturday EVE would literally not stop freezing; it would freeze up again within 5-10 minutes of rebooting the client. The computer had been freshly reboot, no other applications were running, all the graphics settings were as low as possible and sound was turned off.

iMac 2.66 Core 2
4 GB RAM
Radeon HD 2600 Pro 256 MB
OS 10.6.8

I then switched to my laptop. There's a lot less software clutter on the laptop, as it's pretty much just used for holidays and to play my alt in EVE. Zero freezing problems, just a few graphical glitches like the spinning black warp tunnel. I've also never experienced a single freeze with EVE on my laptop, just constant graphic glitches.

MBP 13" 2.3 Core i5
4 GB RAM
Intel HD 3000 384 MB
OS 10.7.3

MBA 13-Inch mid 2011
1.7GHz Intel Core i5
4GB 1333 MHz DDR3
Intel HD Graphics 3000 384MB
Mac OS X Lion 10.7.4

Experiencing crippling random freezes. Actions stop first (i.e. warping, attempting to jump will be ignored) followed by sharp framerate drops (down to 1-2 fps).

Attempts to log out or quit are also ignored and further grind down the system. Eventually eve attempts to return to the Desktop, where I have to force quit it.

Sad face as this always happens at inopportune moments.

Current problems I've encountered on Mac:

1) Frequent freezes followed by logouts and crashes.
2) Textures. Both on planets and while warping.
3) Sound. Many sounds don't play.
4) Occasional horrible lag.
5) Character Creation is almost impossible to navigate it's so slow. (And having graphics on lowest settings results in a portrait picture taken with appalling low-res textures.)
6) It seems after each new update Mac Eve performance gets slower and slower and I'm forced to turn off more effects.

Come on CCP! Just because Mac users are in the minority doesn't mean we should wait so long for these fixes!

Yeah I figured I would add my story to this thread of tears. Playing EVE three weeks and whole time I have had issues with the client freeze. Filed a petition and tried all different kinds of graphic combinations, using a VPN client or not, rebooting before I play. Anyway not really sure if anything really makes a difference. Some days I basically can't play this game. Other days I get a few good hours before a freeze.

Curious to me how random this is and how it only seems to affect some users and even then with differing levels of severity. I have a retina MBP maxed out 2.7, 16 gig ram. My suspicion is I need to shutdown before I play and after a freeze to reduce the frequency of freezes. Not really sure about this or anything else really. One thing I did notice is sometimes after my client freezes when I reboot and restart my computer the internet signal strength bar will be kind of blinking single bars up and I can't connect to the internet requiring another restart. I often get the socket something or other box when my game freezes. I don't think it's my connection because I can play blizzard games online without a worry or concern, what a difference.

Anyway I bought a years subscription anyway cause I like the game that much. Unfortunately I agree with the sentiment behind the CCP should stop the mac client because I don't think they are being very ethical touting this product with such an obvious bug. Anyway I am using it at least until Windows 8 comes out and then I will probably boot camp it as much as I don't really want to.

Not sure what the fix is but a native mac client seems like the only real fix for now and for the future. I am sure CCP has studied this and has good reasons for not doing it. These posts will hopefully provide some player context and maybe get one or two people in CCP to do the right thing and maybe we get a good solid product or at least they put a label on the mac client admitting to the bug so buyer can beware. I get the free trial and all that but it just seems not very ethical to peddle a bad product.

This is probably your problem. EVE is fidgety about your 'net connection. For instance, it doesn't like sharing your internet connection with any Torrent clients.

Notice that I didn't say "the Mac EVE client." If this is your problem, and you switch to the Windows client, the odds are good that it will still be your problem.

Having the same issue. Happens randomly every 15 min or so... Really makes the game unplayable. Please fix this soon CCP!

My client has been surprisingly stable lately. Not a single freeze but a few disconnects, half of them when jumping through a gate. It seems like something has been fixed and I am very happy.

Maybe you could look over DC mechanics because often they happen silently and you notice it only when trying to activate a mod. Sometimes you can kick a reconnect by opening the wallet. It would be nice if the client was aware of the DC and informed you about it.

Also, mumble stays on-line so it doesn't look like a problem with my connection.

But all-in-all a HUGE IMPROVEMENT. Thanks!

I'm starting to get DCs more often. The most recent one was in a mission. It happened when I recalled my drones. The client just showed them orbiting my Vexor, no matter what I did. Then I noticed that the Damage Control was permacycling, no matter what I did, quit, and restarted.

At least it wasn't like the time I DC'd under fire and logged back in to find myself in half armor with no drones, but it's still unsettling.

Wow. So it's trying to free memory it didn't allocate, and then consistently failing to allocate memory at all. Looks like (a) bad pointer(s) from here.

I'm going to go out on a limb and say that the bulk of those errors are from Cider. That doesn't mean it's Cider's fault, necessarily, but the greater speed and reliability of the Windows client makes it likely that Cider's mapping between Windows' memory-manipulation API and OS X's has a couple of holes.