when trying to start the game at version 16.51 after downgrading from 17.15 (and subsequent re-install, and clear cache) the game instantly crashes.
I tried system updates but that didnt fix the issue.
>>> Adding process 21669 for game ID 427520
0.088 Operating system: Linux (Arch rolling)
0.088 Program arguments: "/home/jaap/.local/share/Steam/steamapps/common/Factorio/bin/x64/factorio"
0.088 Read data path: /home/jaap/.local/share/Steam/steamapps/common/Factorio/data
0.088 Write data path: /home/jaap/.factorio [71602/269715MB]
0.088 Binaries path: /home/jaap/.local/share/Steam/steamapps/common/Factorio/bin
0.100 Error Util.cpp:49: Invalid value "none" of BoolWithAuto at ROOT.graphics.texture-compression
------------- Error -------------
Invalid value "none" of BoolWithAuto at ROOT.graphics.texture-compression
---------------------------------
Error on startup in 0.16.51 after downgrading from 0.17.x
-
- Inserter
- Posts: 40
- Joined: Mon Aug 06, 2018 6:06 pm
- Contact:
Re: crash on startup, linux
Hello, delete config.ini; It should be in ~/.factorio/config/config.ini
-
- Inserter
- Posts: 40
- Joined: Mon Aug 06, 2018 6:06 pm
- Contact:
Re: Error on startup in 0.16.51 after downgrading from 0.17.x
thanks this worked!
but I found one interesting anomaly, the FARL mod(3.1.0) could be loaded because of: { Failed to load mod "FARL": Mod FARL dependency (?) VehiclesEquipement not matching pattern "[?!] ModName [ModVersion specifier]".}
which in itself might be because of a version incompatibility, but all mods are disabled and thus also shouldn't cause any issues.
I don't know if this behavior has been changed in .17, but I am of the opinion this should be fixed (don't attempt to load any disabled mods, and don't crash on any reconfiguration of disabled mods)
Edit:
I renamed the mods folder ofc, so the original issue is fixed(although maybe just give a "cannot recover config data" message and reset the file to defaults on a crash? seems better than a seemingly random crash, again I dont knwo if this has been fixed)
but I found one interesting anomaly, the FARL mod(3.1.0) could be loaded because of: { Failed to load mod "FARL": Mod FARL dependency (?) VehiclesEquipement not matching pattern "[?!] ModName [ModVersion specifier]".}
which in itself might be because of a version incompatibility, but all mods are disabled and thus also shouldn't cause any issues.
I don't know if this behavior has been changed in .17, but I am of the opinion this should be fixed (don't attempt to load any disabled mods, and don't crash on any reconfiguration of disabled mods)
Edit:
I renamed the mods folder ofc, so the original issue is fixed(although maybe just give a "cannot recover config data" message and reset the file to defaults on a crash? seems better than a seemingly random crash, again I dont knwo if this has been fixed)