So far I've had very little luck on Mac with either 1.6.2f2 or 1.6.2f3 due to a couple of different freezing issues.

I've got two test machines here, one running macOS 10.12.4 and the other 10.12.5. The results vary a bit between them, but both are pretty unplayable.

Test Systems

- Macbook Pro (late 2013)
- macOS Sierra (10.12.4 / 10.12.5)
- Nvidia GeForce GT 750M
- 16 GB RAM
- NOT USING GOG GALAXY (it's not installed on either machine)

Tested Versions

- War for the Overworld 1.6.2f2 (with and without DLC)
- War for the Overworld 1.6.2f3 (with and without DLC)

Symptoms

Originally I ran WFTO 1.6.2f2 on the macOS 10.12.4 machine. Every 5-10 seconds the game would freeze for 2-4 seconds during all menu scenes (main menu, end of level, etc.) and cinematics. The game levels themselves played alright though.

I reinstalled when WFTO 1.6.2f3 was pushed live. The menu lags/freezes didn't go away, but additionally clicking "Play" for the first campaign now completely freezes the game which requires a force quit. So this was worse.

I tried WFTO 1.6.2f3 on the macOS 10.12.5 machine. On that machine I didn't encounter any menu lag, but the game still entirely locks up when clicking "Play" for the first campaign level, rendering the game unplayable.

Notes

When the menu freezes occur, the full game is frozen -- no animations, mouse movement, etc. But the game does resume after a few seconds.

For 1.6.2f2 (on 10.12.4), there are no specific sound issues. When the cinematics freeze the sound freeze-skips along with them, so it appears to be a full lag of the cinematics themselves, and not just a graphical issue.

For 1.6.2f3, after clicking "Play", the game locks up before the cinematic even begins. The Screen is mostly black, but there does appear to be a random level-related texture image over on the right side of the screen when the lock-ups occur (on both test machines).

What I've Tried

- Disabling "Automatic Graphics Switching"
- Closing all other running applications
- Reinstalling
- Running with and without the DLC installed
- Running on another machine

Any other suggestions on getting WFTO to run?

Mine did something similar. Every 15 seconds or so (same time every time) it would freeze for a fraction of a second. I fixed this by downloading the 32-bit version.

My machine is way more capable than the game needs.

Both test systems are the same hardware specs. One running macOS Sierra 10.12.4 and the other on 10.12.5. The game lags with regular freezes on the 10.12.4 machine.

I disabled cinematics (option: "Disable Cutscenes") on the 10.12.5 machine, and that did allow the game to run, which is great. Thanks! That does kind of take away the game's story and humor, though.

Unfortunately, the 10.12.4 machine still freezes every few seconds during the game's menu screens.

Screenshots attached:

(1) wfto-cinematic-freeze.png — Screenshot when cinematics are enabled and "Play" is clicked (full game lock-up)
(2) wfto-cinematic-freeze-monitor.png — Activity monitor when cinematic freeze occurs
(3) wfto-random-freeze-monitor.ong — Activity monitor time view for CPU usage while main menu is running. High user usage (blue) is when the game is not frozen. Low points are during the freezes. The game ceases pretty much all CPU usage, even though the system isn't using it for anything else.

Could some of these freezes be caused by codec issues?

Alternately, it looks like version 1.6.2f3 uses Unity Player 5.4.4f1 (according to the *.app version info). On the Steam forums for WFTO, I've seen a couple older reports (presumably from your team) that these random freezes have been caused by incompatibilities between Unity and the more modern macOS distributions. If this is still the case, are there any open Unity engine threads addressing the topic?

Thanks for the candid response. I wish you luck in the 5.6 update.

As a dev myself—including working with Unity—I know updates on Mac and Linux can be ...trying... and I appreciate that you guys are putting in the cross-platform effort.

In the mean time, I updated the 10.12.4 machine to 10.12.5. Unfortunately, the regular-interval freezes are still present on that machine, so for now I'll assume it's something to do with that particular machine's configuration. If I happen across the specifics I'll let you know ;)

I'll keep an eye out for updates and post back if the issues are resolved, but for now I'll mark your previous post as the solution. Thanks.

Though probably inconsequential, the 32 bit note is potentially interesting.

Lee, out of curiosity (and without getting into proprietary specifics), did you happen to change the thread model between versions—e.g. single-thread the 32 bit version and multi-thread the 64 bit?

Of course, it probably wouldn't explain my issues here unless the menus or overlay animations are run on a separate thread.