Page 1 of 1

[0.12.29] Was working, but now it crashes on start up.

Posted: Sat Apr 09, 2016 5:10 pm
by de4
No matter what I do it crashes on start up, I've re-dled it 5 times.
Log:
0.000 2016-04-09 09:55:56; Factorio 0.12.29 (Build 17931, mac, steam)
0.000 Operating system: Mac OS X 10.11.3
0.000 Program arguments: "/Users/me/Library/Application Support/Steam/steamapps/common/Factorio/factorio.app"
0.000 Read data path: /Users/me/Library/Application Support/Steam/steamapps/common/Factorio/factorio.app/Contents/data
0.000 Write data path: /Users/me/Library/Application Support/factorio
0.000 Binaries path: /Users/me/Library/Application Support/Steam/steamapps/common
0.147 Graphics options: [FullScreen: false] [VSync: true] [UIScale: 100%] [MultiSampling: OFF] [Graphics quality: normal] [Video memory usage: high] [Light scale: 20%] [Screen: 255]
0.151 Available display adapters: 1
0.151 [0]: resolution 1280x800px at [0,0]
0.151 Create display on adapter 0. Size 1180x700 at position [40, 32].
0.255 Initialised OpenGL:[0] Intel HD Graphics 4000 OpenGL Engine; driver: 2.1 INTEL-10.12.13
Factorio crashed. Generating symbolized stacktrace, please wait ...
0.406 Warning Logger.cpp:334: Couldn't symbolize stacktrace: (resolving symbol failed: fread)

#0 0x100449149
#1 0x7fff8a470eaa
#2 0x10194f000
#3 0x1007ff1c8
#4 0x100806424
#5 0x1007b9db6
#6 0x10020f5b8
#7 0x1002015e9
#8 0x1001ff438
#9 0x10032b21e
#10 0x10032a094
#11 0x1008008d7
#12 0x7fff96205c6f
#13 0x7fff93f4fc13
#14 0x7fff93f4fb90
#15 0x7fff93f4d375
0.419 Warning Logger.cpp:334: Couldn't symbolize stacktrace: (resolving symbol failed: fread)

0.419 Error Util.cpp:78: Unexpected error occurred. You can help us to solve the problem by posting the contents of the log file on the Factorio forums.

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Sat Apr 09, 2016 5:19 pm
by daniel34
Try setting the launch options to "--max-texture-size=4096".
To do so, right click on the game in your library, then select properties, then set launch options.

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Sat Apr 09, 2016 5:38 pm
by de4
daniel34 wrote:Try setting the launch options to "--max-texture-size=4096".
To do so, right click on the game in your library, then select properties, then set launch options.
When i plug in -max-texture-size=4096 the game won't open, otherwise putting in --max-texture-size=4096 didn't do anything. Thanks for they try though,if I make a mistake please let know.

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Sat Apr 09, 2016 6:35 pm
by daniel34
de4 wrote:
daniel34 wrote:Try setting the launch options to "--max-texture-size=4096".
To do so, right click on the game in your library, then select properties, then set launch options.
When i plug in -max-texture-size=4096 the game won't open, otherwise putting in --max-texture-size=4096 didn't do anything. Thanks for they try though,if I make a mistake please let know.
Sorry, the mistake was on my part. max-texture-size has to be changed in the config file and not in the launch options, you can find it here: /Users/me/Library/Application Support/factorio/config/config.ini

It's set to 0 by default, you need to change it to 4096.
Image

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Sat Apr 09, 2016 7:05 pm
by de4
daniel34 wrote:
de4 wrote:
daniel34 wrote:Try setting the launch options to "--max-texture-size=4096".
To do so, right click on the game in your library, then select properties, then set launch options.
When i plug in -max-texture-size=4096 the game won't open, otherwise putting in --max-texture-size=4096 didn't do anything. Thanks for they try though,if I make a mistake please let know.
Sorry, the mistake was on my part. max-texture-size has to be changed in the config file and not in the launch options, you can find it here: /Users/me/Library/Application Support/factorio/config/config.ini

It's set to 0 by default, you need to change it to 4096.
Image
Ok, I put changed it but I am still getting an error.
Here is my current log:

0.000 2016-04-09 12:04:06; Factorio 0.12.29 (Build 17931, mac, steam)
0.000 Operating system: Mac OS X 10.11.3
0.000 Program arguments: "/Users/me/Library/Application Support/Steam/steamapps/common/Factorio/factorio.app"
0.000 Read data path: /Users/me/Library/Application Support/Steam/steamapps/common/Factorio/factorio.app/Contents/data
0.000 Write data path: /Users/me/Library/Application Support/factorio
0.000 Binaries path: /Users/me/Library/Application Support/Steam/steamapps/common
0.013 Graphics options: [FullScreen: false] [VSync: true] [UIScale: 100%] [MultiSampling: OFF] [Graphics quality: normal] [Video memory usage: high] [Light scale: 20%] [Screen: 255]
0.014 Available display adapters: 1
0.014 [0]: resolution 1280x800px at [0,0]
0.014 Create display on adapter 0. Size 1180x700 at position [40, 32].
0.105 Initialised OpenGL:[0] Intel HD Graphics 4000 OpenGL Engine; driver: 2.1 INTEL-10.12.13
Factorio crashed. Generating symbolized stacktrace, please wait ...
0.154 Warning Logger.cpp:334: Couldn't symbolize stacktrace: (resolving symbol failed: fread)

#0 0x100449149
#1 0x7fff8a470eaa
#2 0x10194f000
#3 0x1007ff1c8
#4 0x100806424
#5 0x1007b9db6
#6 0x10020f5b8
#7 0x1002015e9
#8 0x1001ff438
#9 0x10032b21e
#10 0x10032a094
#11 0x1008008d7
#12 0x7fff96205c6f
#13 0x7fff93f4fc13
#14 0x7fff93f4fb90
#15 0x7fff93f4d375
0.163 Warning Logger.cpp:334: Couldn't symbolize stacktrace: (resolving symbol failed: fread)

0.163 Error Util.cpp:78: Unexpected error occurred. You can help us to solve the problem by posting the contents of the log file on the Factorio forums.

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Sat Apr 09, 2016 8:41 pm
by posila
This person had exactly same stacktrace and managed to fix it by rebooting their Mac.

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Mon Apr 25, 2016 12:18 pm
by Smarty
has this problem been resolved?

Re: [0.12.29] Was working, but now it crashes on start up.

Posted: Mon Apr 25, 2016 12:26 pm
by Klonan
Smarty wrote:has this problem been resolved?
They would probably be back here on the forum if they still had a problem,
Moving it to resolved