Installed from DLS, obsolete

G.M.

Well-known member
I thought to help someone at the TANE forum part
and downloaded <kuid:46410:100103> RER B v2-02, an old route from the downloadstation
I just wanted the route actually, but it automaticly started dowloading 300 items
179 of these are "Installed from DLS, obsolete"
already put them in a .CDP RERobsolete and removed


Questions:
-why did it not only downloaded the pure route asset only?
-why does it download 179 assets that have "newer" here installed (not meaning better)
-is there no thought about bandwidth?


Think there is a basic flaw in this system, must I be the PITA again?
btw I love old routes :-)
 
Hi G.M. I assume it downloads the dependencies as they are listed in the config.txt and doesn't check for obsolescence until it gets to CM. An improvement would be nice. Just doing nothing, there have been so many recent asset updates that right after downloading over 100 "newer available" assets, I now find myself with over 300 "newer available" assets! Yes, talk about bandwidth! And so many of these assets seem to be getting updated only a day or two after the initial uploads, so maybe new Q&A is needed before the initial uploads are allowed?
 
How I hope/wish it would work:
-You select a route/session from the DLS
-it only downloads those files. it installs them in CM
-CM checks what is installed and needed (not from the config)
-a CM screen pops up with the needed dependencies remaining
-the user selects which of those he/she wants to download
keeps it clean and no bandwidth waste


I can't decide how others want to share,
what I do here is at least have one other user test my assets before any release
sometimes stuff is in alfa or beta for a considerable time.
No one is in a hurry, most of us are old guys anyway :-)
 
Downloading with the content manager has always downloaded the dependencies. For maps and sessions I use the ftp download from the DLS website (white pages). After installatio, I could download the dependencies. Another possible procedure for downloading is using 'download this version', and stopping the download, when the map has been downloaded.

Peter
 
yup good workaround Peter, but again its a workaround, so in most cases people download too much unneeded
 
The content managers of TRS2006 to TS12 allowed better control of the downloads. The dependencies were automatically added to the list of downloads, and could be removed. I really miss that feature.

Peter
 
When you select Download this version the route or session is always the first item to download. After that the dependencies are downloaded using the kuids stated in the principal asset config file (the route or session in this case).

I nearly always download route and sessions in this way and watch the download window. As soon as the first asset has been installed I know I can stop the download and then proceed to load the dependencies using CM as usual. I then select groups of assets that are essential to the route, such as track and track objects and download them, ignoring buildings, flora, vehicles etc. Having gained an appreciation of the route I can then decide whether to discard it or continue downloading.

Yes, it is a workaround but does the job until such time as N3V decides to make a change.

Trevor
 
Maybe they could ask you if you want, the whole thing or just the route or session you picked. Seems to me that would be the easiest thing to do.
 
In TANE upwards, so long as you haven't downloaded anything else on the same day, dependencies downloaded for a route are listed under today, if the route is junk the now unwanted downloaded dependencies can be deleted from the today tab.
 
Always have a CM window with "today" open when downloading and always download in very small batches
give yourself a pressie a day is more fun and appreciate it more that way
Also, I repair stuff at once, like 1:100 from DLS is "broken" (average here)


the purpose of this thread ofc. is, we should not (be forced to) download unneeded items
it seems all free but in the end it is not.
 
If you select one of those 'obsolete' assets and View Asset Versions, you will likely see the newer version as v127 and 'Unknown.' This is a previously reported issue that arose after some server-end changes. The suggested fix is to perform an Extended Database Rebuild.

John
 
Back
Top