protofeckless wrote: »Yesterday: I got 2 hours of gameplay without a crash. Doing writs, the event dailies, and some skill point grinding.
Today: First crash after ~2.5 hours. Same content as above. Lots of zoning. Second crash after 3-3.5 hours grinding psijic and skill points (lots of zoning).
So there seems to be some progress this patch. I'm almost confident to run a trial if my guildies allow me to relaunch right before starting. But there's still lots to fix. It aint working yet. A night of PvP on a pop-locked server? Yah no joy.
Still have the issue of the game crashing on quit. Every time. Infinite spinner. Have to force quit.
Looking back at update 4.2.11:
"Mac Game Client
Fixed an issue where visuals would randomly flicker when moving around the world.
- Not sure what this means, but if it's erratic fps, then NOPE
Fixed an issue that would cause Mac clients to crash when quitting the game.
- Nope. Never fixed.
Fixed an issue where the Mac client would consistently restart in windowed fullscreen, even after changing it to fullscreen mode.
- I don't play fullscreen mode 'cause this game is the only app ever to lock MacOS (not crash, not kernel panic, not process dump - just lock the whole damn box into frozen state - after playing in full screen. Didn't even think this was possible on MacOS. Will never do fullscreen mode again. That said, every launch starts in a low rez / small windowed screen regardless and needs to be resized manually. I don't think it's relaunched into it's previous state once since Murkmire.
Fixed an issue where Command+Tab wasn’t working while in fullscreen mode.
- Nope. Well IDK, define "working". I can Command+Tab to put the game in the background, but that = death for this game. If I put it in the background and bring it forward again, no keyboard input is recognized by the game. Other open apps function normally. This game however, dies. I can't recall if this behavior started with Murkmire, but I think it goes back longer than that even. By my definition, Command+Tab doesn't work in any view.
In summary, the evidence doesn't suggest any of the reported fix code in 4.2.11 actually made it into that patch.
ErinSparkblade wrote: »I haven’t crashed since the last update. The only major thing I’ve noticed that’s different is that you have to get a lot closer to stuff before it’s rendered properly. My guess is the client was writing cheques that a lot of Mac cards couldn’t cash, and they’ve reduced the render range to fix that.
@FierceSam , I don’t know what your settings are, card etc, but have you tried dialing down the settings, especially any render ones, and seeing if things are more stable?
For the record, I’m on medium settings with an M380 2GB card - occasionally choppy, but not insta-crashing.
@FierceSam, I hear your frustration, amigo. Sorry your experience is not improving
That said, the fix is clearly not comprehensive and the Mac client still has significant build flaws that need to be addressed. Also a more enlightened communications strategy from ZOS re the Mac community would be a great QoL improvement.
Game client still crashes, but takes much longer. Extremely long load time between zones. Lag in cyrodial is almost unplayable sometimes 250 ms to 1500ms that's 1/4 sec to a second and a half at times. Stuttering is still present. Doesn't seem that much improvement and in some cases the client is worse than before latest poor attempt at resolution of this long standing problem.