Macintosh

I've been very happy with the upgrade and participated on the TEST server prior to patch with no issues. But tonight, I've lost two ships due to suddent client crashes. The mechanics of how client crashes are resolved seem unfair beyond the actual bug that is causing it.

In the first instance, the client hung during a jump into evaulon (which was under incursion). The client hung. I had to kill the process from the monitor / task window. When I came back, I was in a pod, killed by a rat on gate.

The 2nd instance, I was moving cloaked 500km outside a mission room (not in it, and moving away from it) and sufferred a client hang that caused the app to close itself uninvited. When I logged back in, I was warped to gate and had my ship blown up by people waiting on gate. Definitely wasn't moving towards the gate, near it or anything prior to crash.

I've seen other issues where the chat windows become unresponsive but the mouse may work for a bit in other aspects of the game. I can enter text and nothing is echoed OR no keyboard commands work.

Prior to this smaller patch, if I was using two clients, one would inevitabley report a buffer overflow and close, but in tonight's case, I wasn't running two clients. In fact, I have 3 separate installs on my system, each installed from a different d/l into a different directory. Further more, I had cleared the cache on the instance that was crashing. I do that on a regular basis.

I have settings turned down but I did turn on the instation walk about mode today with low settings. Im running an i7 with 10.7.2 OS X on a vanilla install and 4gb of ram. It's a good, standard system.

The two concerns about these expensive, unwarranted losses are: DCs rarely result in death / coming back in a pod. Both results seem very unfair. Also, it seems like some type of resource exhaustion is occuring which is weird for a new-ish system.

I have put in petitions but have received no responses as of now.

Another odd thing, at times my ships show completely as white "cut outs" in some views. The same goes the tops and bottoms of planets in the PI "view planet" mode. I am also seeing that when my overivew has two tabs, the main tab frequently does not update distances as the ship travels through a system, unless I tab to the alternate tab and tab back to the tab I am attempting oto use.

http://imageshack.us/photo/my-images/94/ship2y.png/

There's one ship screen cap of ship "cut outs"

FYI follow-up. Other MAC OS X users have reported similar crashes and cut out views when turning DOWN their graphical settings. It appears that going with the lowest settings causes the client crash. As I have turned my graphics settings back up, the outright crashes seem to be gone! I appended this detail to one of the reimburse requests.

I did so and received a response of roughly "Can't tell what shows up on your screen, so can't do anything"

I did link both the freeze and the CTD threads, but that didn't seem to matter.

I suppose I'll try escalating with a link to your post here.

Just lose a pod with implant :(

The logic in the stock response is maddening. The implication is that there is a clear server side message that causes CCP to quietly reimburse people who have lost ships in some quiet and proactive way. I have had several corp mates now report similar issues with hangs on session change. Yet if CCP has no adequate server side reporting to address this, what are we to do?

Clearing cache isn't clearing this problem and the problem isn't going away. The other, affiliated issue, is that CCP should have meaningful logic tied to server side reporting that will prove what we already know when these things occur. Simple keep alives upon session change can point out if a client has gone dead. Im sure those in "the know" would have even more elegant solutions. Losing assets due to issues not related to game play is one thing, not being able to even stay in the game, having accepted those losses is another thing. This issue is not a transient, isolated issue. If there is no server side reporting, no response on bug petitions or reimbursement petitions are summarily denied, what conclusion can I reach about CCPs development or customer service processes? I am rather invested in this game, don't have plans to leave it, and I generally am a fan of CCP, but I feel let down over this ongoing issue.

"Graphical in nature pretty much backs up what we have been saying....well, some of us have been experiencing.

Client "Freezes" but only graphically, the client still runs and the toon will stay in game for HOURS, and you think it is locked or safely in a POS, when in actuality, you are being bumped or some other thing and you can even die and be podded while on your screen you are safe in a POS.

I am not sure whose "Fault" this is,, but it is certainly a function of the client and NOT our computer. Not sure if someone from the Mac team can enlighten the GM's about our plight, but I for one will NOT login my Titan until this bug is squashed. I would cry if I even thought about putting in a ticket on that.

The logs show nothing