Greetings, my fellow iron clad warriors of honor and dignity. It is my deepest regret and a terrible burden to bestow upon fellow Mac-bearing hopefuls of this heart-wrenching news: Chivalry: Medieval Warfare fails to launch on Mac.
Worse yet, this is an issue that has obviously been rampant across the community since late January. Most disappointingly, Torn Banner has refused to acknowledge this fundamental problem with their recently released product. Are they working on a fix? Will they ever fix it? Will they offer any form of apology or refund? Nobody knows.
This isn’t an issue for all Mac users, but it’s definitely an issue for a lot of us.
The following is a chronologically sorted listing of threads full of people experiencing this issue:
It’s obviously surprising to see such a longstanding, common, and fundamental error untouched by the follow-up support that any new release requires. It’s especially disheartening that Torn Banner is ignoring these outcries from their new user base, without even offering a temporary workaround for the more tech-savvy users.
THE ISSUE ITSELF
The game launches, displays the Unreal logo, then the Torn Banner logo, and then displays the initial loading screen. A loading screen that never ends. The animations in the loading screen play fine, and the bottom-right spinning sword indicator spins fine. The fans ramp up, the loading screen continues, but the main menu never loads. The game starts up in a windowed mode, and without focus. Command-tabbing to the Chivalry application does not succeed, and the OS appears to see the application as unresponsive (despite the loading indicator spinning smoothly). I wonder if this is an issue primarily for Yosemite users.
I have tried my best to troubleshoot this for as long as I could stand, to no avail. Trashing configs, steam verifying the game cache, opting into the [patch33] beta, launching the executable file with the command-line argument to open directly to a map (aocffa-arena3_p) – I’ve been able to make any progress on this issue. It doesn’t appear other users have had much success with their troubleshooting efforts, either.
If any Mac users have reached any success, progress, or clues in their troubleshooting efforts, I’m sure we’d all be appreciative to hear it.