Factorio Forums

On loading, my MacBook Pro (Lion) machine becomes unresponsive.

Here's the factorio-current.log:

19217.730311 Info AllInOne.cpp:141: 2014:11:04 13:18:10; Factorio 0.11.1
19218.006504 Info AllInOne.cpp:237: Loading mod core 0.0.0 (data.lua)
19218.038565 Info AllInOne.cpp:237: Loading mod base 0.11.1 (data.lua)
19218.428141 Info AllInOne.cpp:237: Loading mod base 0.11.1 (data-updates.lua)

Its loaded about 10% when my machine freezes and then I have to do a hard reboot.

Machine info:
Mac OS X 10.7.5
2.4 GHz Intel Core i5
4 GB 1333 MHz DDR3
Intel HD Graphics 3000 384 MB

It's not bricked, then.
When a device is bricked, it can be only used as a paperweight ever since.
(Unless you happen to own some specialized equipment that is)

Fair point, I've edited the subject line.

Maybe a silly question, but - how long have you waited?
For me - the first time I tried 0.11.1 it got stuck for a fair amount of time at 10%, but then got on. Subsequent runs were much faster.
I think it has to do with older mods, so you could try removing all the mods you have, or try waiting more time...

sillyfly wrote:Maybe a silly question, but - how long have you waited?
For me - the first time I tried 0.11.1 it got stuck for a fair amount of time at 10%, but then got on. Subsequent runs were much faster.
I think it has to do with older mods, so you could try removing all the mods you have, or try waiting more time...

This is the crop cache mechanism loading. It can take a while (a minute?). Basically the game precalculates how to "crop whitespace from the images" so they take less space in the VRAM. It only happens when the version changes.

An update, I tried waiting, but after more than half an hour nothing was happening. I also tried 0.11.2*, but it freezes at the same point.

my factorio/mods/mods-list.json is:
{
"mods":
[
{
"name": "base",
"enabled": "true"
},
{
"name": "trailer",
"enabled": "false"
}
]
}

Thanks for the suggestions


* factorio-current.log
0030.299984 Info AllInOne.cpp:141: 2014:11:14 02:19:13; Factorio 0.11.2
0031.078171 Info AllInOne.cpp:216: Loading mod core 0.0.0 (data.lua)
0031.116156 Info AllInOne.cpp:216: Loading mod base 0.11.2 (data.lua)
0031.723116 Info AllInOne.cpp:216: Loading mod base 0.11.2 (data-updates.lua)
0033.552819 Info AllInOne.cpp:152: Initial atlas bitmap size is 8192
0033.589539 Info AllInOne.cpp:91: Created atlas bitmap 8192x8186
0033.590704 Info AllInOne.cpp:91: Created atlas bitmap 8192x4747

I can confirm 0.11.3 also crashes in the same way. I should add that when it does freeze, the factorio window looks intact but the rest of the OS background partially disappears as though it was part the way through rendering the screen and then got stuck; I think something interesting is happening in the graphics driver.

For reference: someone else seems to have the same issue.

I observed more or less the same behavior on my system (Debian linux with radeson-si and mesa GL driver; GPU is a Raden HD7850).

The problem did not occur when I switched to low graphics mode mode. Can you try if this works for you too?

I finally god rid of it by adding the line 'max-texture-size=4096' to the [graphics] section in config/config.ini. Since then it works like a charm without low graphics mode too.

I already had low graphics mode, but I have a breakthrough! Thanks chlue!

If I have 'max-texture-size=4096' then I can run on higher graphics without having crazy artefacts on 0.10.12. It does get laggy though.
And I can now run 0.11.3 (laggy if I don't have graphics level on low).

Are there any side-effects from setting the max texture size?

infinitehubgear wrote:Are there any side-effects from setting the max texture size?

Performance will be a little worse.

Given that without this line the game seem to freeze certain systems or lead to graphical corruptions (I blame the video/open-gl driver for this ultimately trough) it may make sense to make this the default setting or at least make it easier to find out about this setting. I just read about it by luck when scrolling trough an intel gpu related thread.

My cousin had the same issue, and setting the max texture size and low graphics helped him clear the 10% hurdle but now he seems to be crashing at 90%
OSX Yosemite
it's an iMac

It looks like your cousin has a different issue. Perhaps he can make a new bug report with more details?

Regarding the line "max-texture-size=4096", is it only relevant when crop cache mechanism is loading during a new update? I notice that if I remove the line I can still load and play factorio.

infinitehubgear wrote:It looks like your cousin has a different issue. Perhaps he can make a new bug report with more details?

Yes. Wait for 0.11.6 (that version should be available for mac again) and check again. If it still crashes, create a new bug report.

infinitehubgear wrote:Regarding the line "max-texture-size=4096", is it only relevant when crop cache mechanism is loading during a new update? I notice that if I remove the line I can still load and play factorio.

max texture size is applied every at every game start.

I noticed when I started 0.11.7 for the first time, it did hang at 10% loading for half a minute, but it loaded smoothly after that.

I didn't have the "max-texture-size" setting in my config file, so it seems like this particular crop caching issue is solved for this version on my machine.