Cleaning up old content in DLS

[LIneAxe]

Hi , well I do have alot of older experimental versions of a route and maps . I would like to request DLS remove some of them from their ONLINE Database. Does anyone know where or How I can do this?

 

[johnwhelan]

Hi , well I do have alot of older experimental versions of a route and maps . I would like to request DLS remove some of them from their ONLINE Database. Does anyone know where or How I can do this?

Basically give up now. You can drop in an updated kuid with something else but that I think is against n3V's rules for the DLS.

Cheerio John

 

[cascaderailroad]

If you mess with peoples routes, and were to disable / delete their original stuff, they would be very angry that someone stole their stuff, and made serious variations to it.

Making radical changes to someone elses stuff would be like "Copying" the Mona Lisa, and burning the original, and fixing her face on your "Stolen" copy, so that is your rendition of beauty, and taking credit for the original asset, that someone worked very hard on.

 

[LIneAxe]

Ok that does make sense , However I do have some of my own content that I would like them to remove .. I like that idea of replacing an Asset with another...Basicly I want to get rid of all the old experimental stuff so it's easier for someone to find the new and working Version. Really , I feel guilty leaving that stuff in their database. Thanks for your quick response.. I am diddling with hooking up an Arduino to a Raspberry Pi next , so I think that my Route and it's Sessions are Finally done .
You can check it all out if you like ...

Dugout 3.7 Version 0 will be ready to Download this weekend. It's very quick to download and fun to play

 

[cascaderailroad]

I don't know much about updating assets, but you CAN NOT remove your own old assets, nor anyone else's assets from the DLS ... as when you uploaded them to the DLS, you signed a electronic virtual agreement, and your assets became property of N3V ... I understand that you can update your original assets with a new Kuid numeral, or something like that ... which almost over rides your original asset.

People are always updating a lower 1.3, 1.5, 2.4, 2.6 trainz-build asset, and making it a 09, 10, 12 trainz-build numeral ... which disables the asset in a really low trainz-build like 04, 06 ... and this is totally rude and wrong to alter OPS (OtherPeoplesStuff) and is tiresome to have to continually / repeatedly keep backdating updated assets ... just because someone wants to run a 1.3 asset in TS12 multiplayer ... they take it upon themselves to alter the original asset, and they take the original asset away from 04, 06, 09, 10 users.

If you really want to make something ... Go make it yourself ... from scratch ... and do not use, abuse, or alter, OPS (other peoples stuff).

I would really absolutely love it if someone would take my (cascaderailroad) TRS2006 Paintshed TGV's, and make them use animated bogies

 

[oknotsen]

I do have alot of older experimental versions of a route and maps . I would like to request DLS remove some of them from their ONLINE Database. Does anyone know where or How I can do this?

Replace them by a newer version of your content.

So far, I had the same feeling a few times myself. "It looked okay at the time, I can do slightly better now".

If you upload the new asset with the same KUID or a KUID2 version of that kuid, it will make the previous version obsolete AND people who have the asset will have it automatically show up in their "update" list.
Alternatively, you can upload a new asset with a different KUID and add the kuid of the old asset it should replace in the "obsolete table" of the asset. Works the same way.

Note:
You can only obsolete your own assets.

Good luck updating and erasing tracks back to the time you were a beginner

 

[LIneAxe]

Great answers .. Thanks guys.... Oh ,and cascader ... I am making my own 3d world from scratch using XNA code , have been coding for many years I do tend to import alot of models and sound effects and so on ,as I seem to be spending much more time writing code in one project or another...