- 776
- England
@MrB00 @safi hellie @leBluem @OooAhh Cantona
I also got curious about this as soon as I read that you need to change the track ini either in ..\tracks or ..\tracks\loaded this concerned me a little. I have been messing about with editing tracks lately and hiding models would be ideal to test things etc. My concern about this method is that in @safi hellie 's case, if the additions are put into the ..\tracks folder and Silverstone receives an update via CM into the loaded folder, that new file and any benefits it brings will not get used. Similar if the additions are put into ..\tracks\loaded folder, any updates will actually wipe out those additions and then the objects will be back. After scratching my head a bit, there is a simple solution. Instead of editing a "track".ini, simply create a folder in the track folder called extension and make a file called ext_config.ini. Or if that folder and file already exists just put or add the [MODEL_REPLACEMENT_#] additions in there. Now both those additions and the ../tracks/loaded will each load and future updates will still work and not affect or remove the hidden objects.
There is also a way to have the [MODEL_REPLACEMENT_#] work in both the track.ini and the ext_config.ini but you need to keep a track of which model number you are up to. For example, if the ext_config.ini has 5 models hidden which will be numbered up to [MODEL_REPLACEMENT_4] and you want to hide some more objects but this time in "track".ini, you have to continue the number scheme. This means the first model to hide in the "track".ini must now start at the 6th hidden model, which is [MODEL_REPLACEMENT_5] in this scenario.
I then had a go at removing the items @safi hellie wanted hiding and it is not so simple in Silverstone with the objects being split over separate files.
My assettocorsa\content\tracks\ks_silverstone\extension\ext_config.ini looks like this for removing one set of trucks:
[MODEL_REPLACEMENT_0]
FILE = 1.kn5
HIDE = add1_HI_4 ; test
[MODEL_REPLACEMENT_1]
FILE = 1.kn5
HIDE = add1_LOW_4 ; test
the add1_HI_4 is the clue to where the object is, in this instance the bold 1 here referes to 1.kn5.
I hope that makes more sense to you @safi hellie.
I also got curious about this as soon as I read that you need to change the track ini either in ..\tracks or ..\tracks\loaded this concerned me a little. I have been messing about with editing tracks lately and hiding models would be ideal to test things etc. My concern about this method is that in @safi hellie 's case, if the additions are put into the ..\tracks folder and Silverstone receives an update via CM into the loaded folder, that new file and any benefits it brings will not get used. Similar if the additions are put into ..\tracks\loaded folder, any updates will actually wipe out those additions and then the objects will be back. After scratching my head a bit, there is a simple solution. Instead of editing a "track".ini, simply create a folder in the track folder called extension and make a file called ext_config.ini. Or if that folder and file already exists just put or add the [MODEL_REPLACEMENT_#] additions in there. Now both those additions and the ../tracks/loaded will each load and future updates will still work and not affect or remove the hidden objects.
There is also a way to have the [MODEL_REPLACEMENT_#] work in both the track.ini and the ext_config.ini but you need to keep a track of which model number you are up to. For example, if the ext_config.ini has 5 models hidden which will be numbered up to [MODEL_REPLACEMENT_4] and you want to hide some more objects but this time in "track".ini, you have to continue the number scheme. This means the first model to hide in the "track".ini must now start at the 6th hidden model, which is [MODEL_REPLACEMENT_5] in this scenario.
I then had a go at removing the items @safi hellie wanted hiding and it is not so simple in Silverstone with the objects being split over separate files.
My assettocorsa\content\tracks\ks_silverstone\extension\ext_config.ini looks like this for removing one set of trucks:
[MODEL_REPLACEMENT_0]
FILE = 1.kn5
HIDE = add1_HI_4 ; test
[MODEL_REPLACEMENT_1]
FILE = 1.kn5
HIDE = add1_LOW_4 ; test
the add1_HI_4 is the clue to where the object is, in this instance the bold 1 here referes to 1.kn5.
I hope that makes more sense to you @safi hellie.
) but didn't think about how the track config ini gets updated within the extensions folder. I'll do a bit more messing about with this in the next few days as it's getting more interesting now I can sort of wrap my brain round these things. TBH I just wanted to see if I could remove objects as a little exercise. I've put all the gazebos and tents back in now as I don't mind a bit of track scenery
