Github files & extension > config > tracks OR extension > config > tracks > loaded

[Billy Pilgrim]

Hi
What's the difference between the two folders found: extension > config > tracks and extension > config > tracks > loaded?

Also, how do these folders become full of these files? Is Content Manager doing that automatically?

On a couple of occasions I have downloaded files from Github and installed them myself (e.g. to fix the psychedelic verges on Nordschliefe) and it improved things. How would I know if I should find the files on Github and nstall them myself? Or do I just leave things to be done automatically?

Any advice would be much appreciated.

 

[Johnr777]

Hi
What's the difference between the two folders found: extension > config > tracks and extension > config > tracks > loaded?

Also, how do these folders become full of these files? Is Content Manager doing that automatically?

On a couple of occasions I have downloaded files from Github and installed them myself (e.g. to fix the psychedelic verges on Nordschliefe) and it improved things. How would I know if I should find the files on Github and nstall them myself? Or do I just leave things to be done automatically?

Any advice would be much appreciated.

Github is where CM pulls those files from. I find it confusing myself, since there's a third location to add to the mix, which is inside the track folder itself, "content\tracks\trackname\extension\ext_config.ini" This one would have the most priority and wont auto-update. That one location is handy for modders wanting to include a config file themselves without the risk of another "user made" file already in existence...

To try and answer your question, one way to check is to delete them all, from both locations, and see where CM puts them, OR disable the auto download and grab the files as needed

 

[Billy Pilgrim]

Github is where CM pulls those files from. I find it confusing myself, since there's a third location to add to the mix, which is inside the track folder itself, "content\tracks\trackname\extension\ext_config.ini" This one would have the most priority and wont auto-update. That one location is handy for modders wanting to include a config file themselves without the risk of another "user made" file already in existence...

To try and answer your question, one way to check is to delete them all, from both locations, and see where CM puts them, OR disable the auto download and grab the files as needed

Thanks a lot for your answer and shedding some light on how to work this out. I'll have a go at deleting some tracks' files and see what happens - whether, and where, CM updates them.

 

[Jempy]

As you posted the same kind of question in an other thread ... I made an answer there that might help you.

All I know about it is this \loaded folder will create itself when loading in game a track ( with its config ) for the 1st time.... and it will contain 1 by 1 the tracks you launch for the 1st time.

When I downloaded the full file "acc-extension-config-master.zip" all track configs were in config\tracks and there was no "loaded" folder.

So CSP needs them in loaded ... and it seems that tracks are loading quicker once they are in this folder.

Just 1 problem: once a track is already in the "loaded" folder, update this track in the "track" folder will not be enough to let the new version appear in game.
That's why it's better to install the new versions in "loaded" when downloading them manually ..... and much better and easier to use the update track by track in CM/Settings/Custom Shader Patch/track configs ( with a right click on the orange "older" mention ) that will update it automatically in the "loaded" folder.

For confirmation of the last sentence: I just retested it in CM and the file dates for this track were modified in the "loaded' folder while they were not changed in the "tracks" folder.

 

[Billy Pilgrim]

As you posted the same kind of question in an other thread ... I made an answer there that might help you.

Thanks a lot!
Great explanation - I understand perfectly