henryfakesmile, on 08 April 2014 - 02:33 AM, said:
my games are crashing like fk,,,, do you know how to read these crash report ?
both of my iMac are brand new just freshly delivered my home few days ago ... with gtx 780 & sad .. so there's no way my mac's problem..
version = 0.01
Well, that's the ZOSCrashReporter report so it is pretty useful to get some idea of the reason.
Basically it is showing a known memory related issue in the Mac client. In PVE questing etc. it can crash after 2-3 hours when it hits the limit.
In Cyrodiil AvA big battles it is crashing within 30-45 minutes with lots of other players around, which seems to be a big factor in this.
It is a known issue and there was some changes implemented from the last mass beta to the launch build which reduced frequency of crashes from then but in AvA especially it is still a problem. The development team is continuing to monitor and work on further improvements.
In the meantime I would suggest lowering settings in particular Texture Quality to Medium
(lower are applicable) as it reduces memory requirement. For performance (FPS) reducing Shadow Quality to Medium
or lower will make the biggest difference.
Depending on the Mac model settings need to be reduced in any case in PvP
as there are also other issues which case frequent crashes including being grouped and at log in screen which appear to be server-side related but it's early days yet.
Check out the ESO Mac Technical Support
section (also available in FR & DE) on the official forums where we are gathering more feedback and details/ reports on this thread
. All other main issues for the Mac client have now been addressed with some other smaller fixes in the works.
Personally I am finding ti working really well with Ultra-High settings with a few tweaks in questing and general PVE. Hopefully there will be some more changes made to the client to help in PvP and for them to address the cross-platform issues that exist currently.
Longer term, a move from the 32-bit client (Mac & PC for backward compatibility reasons apparently) to 64-bit will provide a permanent solution.
if you would like to check out Apple eso .crash
reports for this issue then there are some posted as ZIP attachments in that thread linked above. All of them appear to point to out of memory issues:
Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
I could post an example here but don't want to spam the forum.
But if you have any further advice or comment on them it would be appreciated.