2) Note that all recent Mac OS X versions are 64bit. A pure 32bit Mac OS X does not exist anymore and hasn't ship in a number of years.
3) The game launcher is in fact a 64bit executable. However the game client itself is still 32bit.
4) The Mac OS X version exhibits significantly less hitching compared to the Windows version running on the same hardware (this is 10.9.1 versus Windows 7).
5) The Mac OS X version still crashes at least once every 30 minutes while playing in Rohan because it:
5a) either runs out of memory (the C++ new() operator throws an OOM exception but the game doesn't install a default exception handler -> the OS kills the app because of an unhandeled exception).
5b) or it crashes while trying to do an occlusion query because of a invalid pointer dereference.
So in the end, while Lotro could be a very decent Mac OS X game, it falls short of this goal because of its extreme crash habit. Also every time the game crashes the system crash dialog comes up and offers you to restart the game. But when you push the Reopen button then the game immediately crashes again because the game client expects that it gets started by the launcher and that the launcher passes the log-in details via CLI arguments. Naturally that won't work with the system crash dialog. The way that the client should work is that the launcher writes the log-in info into the user defaults and the the game client should pick it up from there when it starts. This would work as long as the launcher and the game client would use the same suite name to access the user defaults. Then the game client could restart as expected when the user hits the Reopen button in the crash dialog.[/QUOTE]
Yet another update and these things are still a problem. I'm glad some typos were fixed in dialogue boxes or whatever....but this stuff literally ruins the game!