#Need help making secondary (DRM-Free) instance of Factorio, Can't figure out the Configs & Pathes

1 messages · Page 1 of 1 (latest)

unborn fox
#

Hey I am trying to create a second instance of factorio, but I am having some problems with the config & setup

DRM-free version - 1.1.110 for all my old saves
C:/ ... /Program/ Files

Steam version - 2.0.8 for all my steam saves & space age stuff
E:/ ... /Steamapps/Common/Factorio

I deleted the Config.ini file, and let the game recreate it so that it would reset the Read & Write Paths,

After attempting to open the version via steam it loaded all my mods in the C:/ folder along with my saves, obviously failed 😦 closed it. Opened the Factorio-current.log in the C:/ (It did not create one in the E:/)
Build Version Factorio 2.0.8 (build #####, win64, steam)
Program arguments E:\ ... \ steamapps \ ... \ x64
Config Path C:/ ... / Appdata/ ... /Config
Read data path E:\ ... steamapps \ ... \ Factorio
Write data path C:/ ... / Appdata/ ... /Factorio
Binaries path are all set to the E:\ ... steamapps \ ... \ Bin

When I do the same process using the C:/ version, inside the Factorio-current.log it shows all of the pathes are set correctly within the C:/ drive, and the
Build version 1.1.110 (build #####, win64, full)
Program arguments: "C:\Program Files\Factorio\bin\x64\factorio.exe"
Config path: C:/ ... /AppData/... /config/config.ini
Read data path: C:/Program Files/Factorio/data
Write data path: C:/ ... /AppData/... /Factorio [1649209/1906846MB]
Binaries path: C:/Program Files/Factorio/bin

Both the E:/ & C:/ have their own player-data.json
Starting from the instance in the C:/ the Info PlayerData.cpp shows that Local player-data is available and Cloud player-data is unavailable
Starting from the instance in the E:\ it shows the opposite that the Local player-data is unavailable and the Cloud player-data is available

I also noticed that the steam_autocloud.vdf will continuously reappear in my C:/ ... / Appdata / ... / Saves folder, even if I delete or move it, do I need to disable steam cloud saves?

Any help is appreciated.

#

I redeleted the config.ini and it changed my Write data path to my E:\ but my Config path is still stuck on the C:/ which is causing problems as both instances are sharing the Config file

unborn fox
#

`In the config-path.cfg file it says that

config-path=__PATH__system-write-data__/config
use-system-read-write-data-directories=false

In the Factorio-current.log file that;

Config path: C:/ ... /AppData/ ... /config/config.ini
Read data path: E:/SteamLibrary/steamapps/common/Factorio/data
Write data path: E:/SteamLibrary/steamapps/common/Factorio [1011831/1907714MB]

In the config.ini file intended for the C:/ ; Both instances are using this config file, but they are both getting different Read & Write locations
[path]
read-data=__PATH__system-read-data__
write-data=__PATH__system-write-data__

In the config.ini file intended for the E:/ ;
[path]
read-data=__PATH__executable__....\data
write-data=__PATH__executable__....

If I were to change the config-path.cfg file to say
config-path=PATH/config
use-system-read-write-data-directories=false`

Would this solve my problem?

willow patio
#

the portable .zip version of the game has these values:

read-data=__PATH__executable__\..\..\data
write-data=__PATH__executable__\..\..
unborn fox
#

Portable meaning steam / online versions?

willow patio
#

portable meaning the .zip version you can download from the website

unborn fox
#

Hmm, the one I downloaded from the website has the config-path=__PATH__system-write-data__/config

But this is the version that is behaving correctly :/

willow patio
#

which did you download? the installer or the .zip?

#

installer version sets the user data path to system read/write, as you are getting right now

#

so it will indeed use the same path as steam version

unborn fox
#

Oh, yeah you're right, I downlaoded the isntaller today. Had attempted the .zip last week and couldn't get them to play nice

unborn fox
willow patio
#

you could

unborn fox
#

Is there a downside to this? The 'could' is tripping me up

willow patio
#

though I don't know the interaction between changing the steam version's paths with steam cloud saves, so... take care

unborn fox
#

Ah, that may be why the steam_autocloud.vdf file keeps reappearing in my C:/ Appdata / ... / saves folder even though the read & write of the steam version does not have access to that folder