Cannot play on Mac I see red screen on game main menu.

[Outsider]

Hi,
I have MacBook Pro (2019), Ventura 13.1.
Intel Core i9, AMD Radeon Pro 5500M, 16G.

I cannot start play The Long Dark.

When I start the game and instead of game menu I see red screen. Please help me.

[nautofon]

First of all, there will be an update to the game shortly that is supposed to address a major issue with the Mac version. This update may or may not solve this particular problem.

https://steamcommunity.com/games/305620/announcements/detail/3644011092477392080

In case you don't want to wait, or if the update doesn't help, you will need to force OpenGL mode to launch the game. The game should run using OpenGL, but performance will be worse. Check out Hinterland's support portal for an explanation of how to do that.

However, the game does work on Metal (no OpenGL) in principle. I have seen such a red screen on my iMac (2020, Radeon Pro 5700), but what usually helps is exiting the game and trying again. Sometimes I have to try multiple times, but it always launches fine eventually for me. (However, other players have reported different results.)

For exiting the game, personally I found it more effective to navigate to the in-game "Quit" option by arrow keys and sound rather than ⌘Q, but YMMV.

BTW, the developer doesn't usually provide support on Steam. To get help from them directly, you need to get in touch through their support portal.

[alastairkendall]

You will not be able to play until the update is released.

[nautofon]

Actually TLD 2.02 plays fine on the Mac today. (Metal for me, even, though YMMV; see above.)

[Outsider]

Helped set startup parameter -force-glcore

[Earofcorn001]

Originally posted by Outsider:

Helped set startup parameter -force-glcore

This fixed it. Thanks.

Edit: Had same issue, working fine now :)

[rush_247]

Originally posted by Earofcorn001:

Originally posted by Outsider:

Helped set startup parameter -force-glcore

This fixed it. Thanks.

Edit: Had same issue, working fine now :)

If issues persist use -disable-postprocess instead.