Timberborn on macOS

[mechanistry]

Hi everybeaver,

The purpose of this thread is collect all information related to macOS support in Timberborn in one place. If you do not find an answer to your question or something doesn't work, please reply here or start a new discussion with "macOS" in its title.

Does Timberborn support macOS?

YES. Please refer to the game’s minimum requirements for details.

Does Timberborn natively support M1 / Apple Silicon?

YES. Starting December 1, 2021, the game runs in native mode (without Rosetta). This applies to the main branch and the experimental branch.

Does Timberborn support traditional / Intel Apple hardware?

YES.

The game freezes during launch, what should I do?

Some players reported that the game stops during launch. We are working on a permanent fix with Steam and our game engine. In the meantime, after clicking Play to start the game in your Steam client, try to select “Play macOS workaround”. Let us know if it solves your problem.

Finally

If you are happy with how the game works on your macOS hardware, don’t forget to comment below! (and include your specs)

[GothAlice]

I have put in 321 hours of play (I keep pause-in-background enabled, so generally if it's running, I'm playing it) so far on my iMac Pro (2017) running a 3.2 GHz 8-Core Intel Xeon W with 32 GB of 2666 MHz DDR4 and a Radeon Pro Vega 56 w/ 8 GB of dedicated VRAM. Initially I ran full-screen, though these days I run it windowed at 5120x2880, medium quality (for reasons), 100% scale and 110% UI scale on the internal 5K panel. I rarely leave the fastest speed unless paused to address something, or wishing to "place ahead of builders" to avoid needing to mess with explicit priorities.

Quality downgrade (initially ran it on maximum quality) is due to the growth of my colonies. Just loading a save can take a few minutes. The one just loaded has 218 beavers of 272 housing capacity. Second load pinwheeled, also not uncommon during saves and loads: 246/320. Saves are much faster operations, though. Third: 373/672. I'll upload some in-game screenshots of my higher density works, but have already uploaded some which may be demonstrative.

Sunrise chugs as pawns work out their immediate tasks in a mad rush, and I've identified on one map that where I'm looking can have a significant impact—as if having some particular object visible takes far more work. Haven't isolated the specific cause yet.

[jim]

The game itself runs fine on my 2017 iMac 27-inch with 3.8 GHz i5, 24 GB RAM, and Radeon Pro 580 8GB, but it freezes if I try to change the graphics settings (well, at least the resolution and the quality slider). With the latest experimental update, I was able to change the resolution one time.

[echo]

虽然很想了解，但是奈何看不太懂

[yucsam]

Originally posted by 小徐同学A:

虽然很想了解，但是奈何看不太懂

就是mac运行下的bug反馈贴而已，但一般也没啥人用mac打游戏吧.;.

[HiPhi]

the macOS workaround does not help in my case avoiding the game to freeze on the start screen using the experimental branch.
It works (with and without workaround) for the normal branch.
Odd thing is, the experimental branch started the first time, I played a map for some time, but now freezes every time.
I tried
* go back to normal branch, launch (worked), switch to experimental branch, launch (did not work)
* delete all experimental saves files (did not help)
* restart MacBook (did not help)

Specs:
MacBook Air M1 2020 with 16GB RAM running MacOS Monterey

update
I got it to work again, seems to be issue with resolution(?) settings.
1) go back to normal version
2) open game, hit start, settings, uncheck "full screen", choose a proper resolution
3) eat settings, exit game
4) switch to beta
5) start game
6) after loading a save file, go back to full screen if you prefer

I can only assume I got the game in this settings problem when moving the game to my external monitor after start (what always worked on normal game)

[GothAlice]

Now that you mention it, HiPhi, I do recall some strangeness with full-screen and resolution settings not being preserved when I switched branches the first time. I mentioned I typically run it windowed, but it returned to full-screen. It was oddly challenging to get it back the way I had it.

[red skunk]

Previously could not change resolution. But now I can and personally don't encounter any other issues on a m1 MacBook Pro, current on updates (runs well!)

[mechanistry]

This is just a quick update that we have just released a new build to the experimental branch (v0.1.0.0) which resolves the freezing/beachballing issues. Let us know if you still have any problems running the game on macOS.

[ok...cool]

M1 macbook air. Never had any problems with this game, before or after macOS work around, other than some resolution issues. But using windowed, then native mac fullscreen resolves this without issue. Processor wise its not amazing - map with 100+ beavers starts to lag. 150+ and it starts to get unplaybale. 200 and its too laggy to enjoy. Limits progression, but it's not a gaming laptop. The new update (mid Dec) nurfs power production too much, kind of game breaking at the moment - makes me want to put the game down till another update, not a mac issue though.

[jdking223787]

I can't see the map at all when i load up the game. I see all the tools but i can't see anything else. just a black screen.

[Dirken Topper]

14" M1 Max Macbook Pro — beachballs on start on all branches and startup modes I've tried.

[TopHatCroat]

Works great on 14" 10-core, no lag with ~150 pop so far, didn't play around with resolution or window settings, worked out of the box.

[booooyeaaaah]

Works great on 14" M1 MaxPro.

[Mister Jofel]

Played the beta a lot beginning of last year, bought the game on launch and played new maps. Beginning of this year, played another map and one that I created myself.
Didn't had any issues with playing the game.

I have a MacBook Pro (16-inch, 2019)

[Schmookeeg]

Just bought the game on the strength of the M1 support -- I have a basic M1 Mini with 8gb that I daily drive for work. I have had the black launch screen/beach ball in every combination of standard launcher or macos workaround, experimental or standard build. I also tried the -popupwindow startup command as referenced elsewhere in the discussion board.

I drive a 4K monitor off of the onboard HDMI and a second 4K monitor off of an Anker USB-C to HDMI dongle.

I have seen a "ghosted" / out of focus popup window fall behind the black fullscreen/beachball window, but I can't be sure it belongs to the game. I have never been able to catch it or switch to it, even using hotkeys.

I will play this on my PC in the meantime but am very excited for any updates to this. I'm looking forward to playing this in an M1 window during many many zoom calls :)