Factorio Forums

Steps to reproduce:

1. Download a fresh install, 64bit .tar.gz for linux.
2. Extract the files to a directory
3. run factorio in the /bin/x64/ directory
4. Game loader reaches about 5~10% and crashes.

Additional Info:

• When running from terminal (via ./factorio) I get the following output:

  Code: Select all

  libpng warning: iCCP: known incorrect sRGB profile
  libpng warning: iCCP: known incorrect sRGB profile
  libpng warning: iCCP: known incorrect sRGB profile
  radeon: Failed to allocate a buffer:
  radeon:    size      : 390070272 bytes
  radeon:    alignment : 8192 bytes
  radeon:    domains   : 4
  radeon: Failed to allocate a buffer:
  radeon:    size      : 390070272 bytes
  radeon:    alignment : 8192 bytes
  radeon:    domains   : 4
  /home/madara/Games/factorio/config/config.ini: cannot open file
  Segmentation fault (core dumped)
  

Steps to fix:

1. Create a directory config in the installation folder
2. Create a file config.ini inside the created config folder
3. Run the game

If it crashes, run it again, the game will run in low graphics mode.

Quote from: https://forums.factorio.com/forum/vie ... =18&t=2220

cube wrote:We can't include the file in the package, because not everyone has it in the same location.

I'm not an expert on Linux but Linux also have support for relative path locations (http://www.linuxnix.com/2012/07/abslute ... xunix.html)
So if you make your Linux distribution so that game tries to acces all of it's files based on relative path location to main program executable you shouldn't have any problems (similar as ZIP version for Windows)

All linux versions have a /home/user directory which (should be) owned by the user.
Also, it doesn't matter where the file is on each distro, it matters where the game expects it to be. As long as you know your own directory structure, it doesn't matter what distro you're on.

I don't see any issue in doing it like this:
You know the location where you want to OPEN the config file.
If it isn't there, then simply create it and the directory?

There is of course the question whether the config should live in ~/.factorio or <factorio_dir>/config
Having separate config dirs for diferent versions is useful with the awesome fast-paced release cycle.
Having the ~/.factorio one would ensure it's actually writable for (future) system-wide installations.
I have no idea how to answer it.


@ Relative path support:
Of course.. given that factorio manages to locate it's data files, I'm sure the same method can be used for 2nd-type config


PS: There is an even older thread for this issue (https://forums.factorio.com/forum/vie ... 29&p=17020) It doesn't really identify the cause, though.

The bug is in the fact that factorio writes its config file relatively late in the shutdown procedure. And if something fails before writing them .. .well, they end up not written.
That's probably also a source of the re-enabling mods bug and stuff. It needs to be fixed, but there was no time before 0.9.0 release ... hopefully we will fix it now.

So the issue is actually quite grotesque?
(Config file cannot be written because is crashes because the config file cannot be read because the config file does not exist)

MF- wrote:So the issue is actually quite grotesque?
(Config file cannot be written because is crashes because the config file cannot be read because the config file does not exist)

Yes, something like that.I moved the saving to as early as possible for 0.9.1, let's see if it helps

I unpacked the game, renamed the unpacked folder to include the game version.
(Huh? Am I the only one who keeps more versions at once??)
And ran the main executable and it loaded without crashing.

I have to admit I didn't (re)move ~/.factorio, so I'm not 100% sure.
EDIT: Actually, there was no ~/.factorio .. only ~/.factorio-0.2-to-0.5 dir I archived old world in