Timberborn update 6 crashes immediately on startup from steam, MacOS

Comments: 12

Oldest • Newest • Most likes • Fewest likes

• Add a comment
• 26 Nov, '24
  Ian M

  Highlighted comment
  
  drwxr-xr-x 4 (computer name) staff 128 26 Nov 14:44 Editor
  drwxr-xr-x 3 (computer name) staff 96 9 Oct 2021 Timberborn.app
  
  Is the output when running `ls -l` on the timberborn folder.

  Copy link to this comment
• 27 Nov, '24
  Gin Fuyou Admin Pinned

  Apparently update has increased minmal OS version to 11.0 and it's a hard requirement (from Unity I assume), so you either have to upgrade OS or revert to older game version, I fear.

  Copy link to this comment
• 15 Oct, '24
  Gin Fuyou Admin

  Do you have mods? Remove them if you do. Note that it has to be done manually, reinstalling game won't work.
  If not, please share you player.log, it should be created always. Instructions are in the pinned topic

  Copy link to this comment
• 15 Oct, '24
  Ian M

  the two logs in the folder are 0 byte files, it crashes pretty much instantly.

  Copy link to this comment
• 16 Oct, '24
  Gin Fuyou Admin

  Can you try starting game from terminal app?
  I fear it would be nearly impossible to provide any help without at least some debug information.

  Copy link to this comment
• 17 Oct, '24
  Engineer in Training

  Are you using windows 7? Update 6 will not run on it, happened to me too.

  Copy link to this comment
• 17 Oct, '24
  Gin Fuyou Admin

  Top post has MacOS mentioned 3 times ^ ^"

  1 Copy link to this comment
• 17 Oct, '24
  Ian M

  Started from terminal app, log refreshes, i.e. updates to today's date and time, but still zero bytes in size. Terminal line returns with: "LSOpenURLsWithRole() failed for the application [application location] with error -10810"

  3 Copy link to this comment
• 23 Nov, '24
  Ian M

  Any update on this bug?

  Copy link to this comment
• 24 Nov, '24
  Gin Fuyou Admin

  Sorry, i've missed it. Can you please check if timberborn executable file actually marked as executable? In terminal run `ls -l` n folder with the binary (I just don't know how you do it in GUI, if you do - just check)
  It should have `x` (eXecutable) flag. `chmod +x filename` to make it executable.
  Otherwise error looks ambiguous.

  Copy link to this comment
• 28 Nov, '24
  Ian M

  Thanks will try that..

  Copy link to this comment
• 01 Dec, '24
  Ian M

  Can confirm, updating to Ventura has fixed issue. Thanks for the support

  Copy link to this comment