cleaning up local data

[johnwhelan]

I have a drive that is dedicated to local data which should be in TS22_content.

However in there I have a folder called build "8obct7fb1" which contains things like packages, original etc. and I'm not sure what is important and what can be deleted.

Thoughts?

Thanks John

 

[MasterTracklayer]

Tell your Trainz to use that directory instead of its normal one and see what you have? Then export anything you want to move over to your usual directory, and re-import it after changing back to your usual tranzebase. there are various export/import methods available, mostly depending on the size and asset count of the assets you want to transfer. Packaged material is handled differently, just copying the *.tzarc files (I think that is the correct extension; don`t worry, though, they will all have the same extension and whatever it is will be correct) with Windows Explorer and rebuilding the trainzbase index.

OR

Is this the first time you have looked into your Trainz data folder? If so, DON`T TOUCH ANYTHING until you know what you are doing. Trainz manages all of that data. Anything that can be deleted safely can be deleted from inside the game. One can violate these rules only at one`s own risk, but some of the data is stuff that very experienced players can Do Stuff To for special non-standard results. For myself, I`m not up to speed on any of that particular advanced magic (except for messing with entire .../packages/ files; I can`t do anything with their contents at this time).

I`m not quite sure which response is the one you need, so I just included them both, "in case".

 

[stagecoach]

Only the backup folder and screenshots can be deleted without affecting the game. Don't delete anything else in the build folder. They will be recreated so pointless doing it.
Local = folder contains all the assets that are modified including the routes and sessions you save.
Original = folder contains all assets downloaded or updated in their original state.
If you add or change an asset from the original it will become modified and placed in the local folder. If you have a problem with that asset and revert, it will delete the modified one in the local folder and return to the original. Original folder can't be modified only updated.

 

[johnwhelan]

The top level folder is where the pointer points to.

The build folder is underneath it.

Thoughts?

Thanks John

 

[MasterTracklayer]

Hmm, in my Trainz22 settings window, it currently opens with the Local data folder setting pointing to the specific database directory. My current setting: ...\AppData\Local\N3V Games\trs22\build kf0optjq1\, where my Win10 edition of Trainz22 stores its userdata, but I also have \AppData\Local\N3V Games\trs22\build sbnlt0ba1\, where my Win7 edition of Trainz22 used to store its userdata before I overwrote the Win7 version with the Win10 version. Perhaps that setting shows only the top level directory when there is only one build directory?

 

[stagecoach]

Build folders don't get overwritten or deleted using uninstall. Every new install of a Trainz product creates its own new build folder. Trainz can only read one build folder, which should show something like the above and end at build 8obct7fb1. It's the build folder Trainz is looking for.

 

[MasterTracklayer]

I agree, stagecoach, with one minor exception:

Trainz can only read one build folder at a time. Multiple data directories can easily be maintained, switching between them as needed, with the caveat that it is not easy (possible, not particularly difficult, just not particularly easy either, for newbies especially) to transfer content between them. I understand that some content creators maintain several such directories; for example, one containing all sorts of content from all over the world, to play in, and another containing only content available from the Download Station in addition to the built-in and packaged assets that are standard, in which to work on their creations, with the intent that they will not accidentally include unavailable dependencies (which still happens occasionally anyway, despite precautions).

 

[JCitron]

I always rename my build-something folders to something that's rememberable and move them outside of the user-data folder structure. It makes managing the data so much easier. If there are any build-something folders created when first setting up a fresh install, I'll go back and delete them since they are no longer used and only eat up space.