removing a downloaded route

[martinvk]

When a route is downloaded, all of the dependencies are also downloaded except for those already install.

When a route is removed, is there an easy way to also remove dependencies that are not used by any other route? Checking each one at a time to see if there are other dependents is too tedious to do, especially if there are hundreds to check.

 

[euromodeller]

Using CM, I would find the downloaded route.
Then I would filter to the date the route was downloaded.
Then you can see which items downloaded with the route, the date and time would match.
Simply select and delete the items you don't want.

 

[martinvk]

That would work if only one route and its dependencies are downloaded. How do your filter on the installation date and time? In CM, I only get to select the date. The time is not an option.

 

[JCitron]

Change the sort order of Installed Date by clicking on the Up-down arrow.

You can also create a filter for Date Installed, and I think there is a "Today" filter there already.

 

[euromodeller]

 

[Forester1]

The original question was this:

When a route is removed, is there an easy way to also remove dependencies that are not used by any other route? Checking each one at a time to see if there are other dependents is too tedious to do, especially if there are hundreds to check.

I don't know the answer to that, does anyone else?
​

 

[JCitron]

The original question was this:

When a route is removed, is there an easy way to also remove dependencies that are not used by any other route? Checking each one at a time to see if there are other dependents is too tedious to do, especially if there are hundreds to check.

I don't know the answer to that, does anyone else?
​

We wish there was something like that. There is a fairly recent discussion on this very subject, but I can't find it.

 

[grazlash]

It would be easier if we could filter; Installed + no dependants.
cheers
Graeme

 

[martinvk]

It would be easier if we could filter; Installed + no dependants.
cheers
Graeme

Actually, it would be "Installed + no other dependents" As long as it is only dependent on the route in question and not for any other route. Then it can be deleted.

On the other hand, as long as it is on the DLS, every dependent of a specific route could be deleted, if you're prepared to download again any they were also dependent on other routes.

Another way would be if we could filter on any object that has no dependents and is not likely to be used in the future.

Boy, this database management is becoming a real PITA.

 

[pcas1986]

Actually, it would be "Installed + no other dependents" As long as it is only dependent on the route in question and not for any other route. Then it can be deleted.

On the other hand, as long as it is on the DLS, every dependent of a specific route could be deleted, if you're prepared to download again any they were also dependent on other routes.
...

Trainzutil has options for getting direct dependants or dependencies. I think by "direct" the command will not do a recursive search.

Anyway, if it were me I'd just delete the route and not worry about the dependencies. I'm sure the only dependants are the sessions and don't they get deleted with the route?

I'm playing with Trainzutil at present but for a completely different reason.

 

[martinvk]

Hmmm, Now that we have TB disks, a few extra objects are not as critical as they used to be. Mind, no reason to be sloppy but perhaps I was getting too excited. Besides, I might want to try some of those orphaned downloads.

 

[euromodeller]

The original question was this:

When a route is removed, is there an easy way to also remove dependencies that are not used by any other route? Checking each one at a time to see if there are other dependents is too tedious to do, especially if there are hundreds to check.

I don't know the answer to that, does anyone else?
​

If using my method, you delete all items downloaded with the route.
It is then a simple check in CM of the routes installed on your machine to see if they are missing any dependencies.
If any are missing then simply re-download them.
Crude method but workable.

@martin, I've found many uable assets in discarded routes

 

[Vern]

If any are missing then simply re-download them

Unless of course they are payware assets only supplied with the route and not freely available on the DLS or elsewhere.

This also harks back to earlier discussion about clear identification or separation of assets from a payware route when building your own project intended as freeware. There is often no easy means of identifying what might have come from installed payware. While the benefits of a central cache of assets on your HD is self evident (save HD space) the MSTS and DTG method of putting routes in a separate folder including all the assets makes it easier to keep segregated (for DTG you need to physically tick the Provider box in the editor to enable) or to solve Martin's OP, a clean uninstall of everything when you no longer need the route.

 

[stagecoach]

In CM select route and list dependencies. Select the + new category and select on download station = true. Select all and delete, it wont matter if other routes use any asset as you can then download any missing assets from the DLS. This will make sure you don't delete third party assets and any others not on the DLS.

 

[MountE]

Stagecoach when you get the list of dependencies you can right click on as many as you want and use dependents any that have no dependent assets could then be deleted. This would save a lot of redownloading. I also start with the sessions and saved sessions to decide what to keep or delete.

Rob

 

[stagecoach]

That is true but even then you would need to check which ones have the dependents from that smaller list. 4400 assets on my route would be a lot to go through and check your way You could just put my way into date order and just delete the newest dates.