The way DLC-contents from DLS are currently handled - sorry - sucks.
I wholeheartedly agree. :Y:
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The way DLC-contents from DLS are currently handled - sorry - sucks.
N3V are still in the process of ensuring that DLS assets up-versioned and bundled in packages are also updated to the same version on the DLS, it mostly works, occasionally something gets missed, in which case help desk or bug report should fix it or if still around the original creator can update it to match. I've done about 5 of my assets that got missed and caused missing assets and one got sorted by Zec who picked it from a thread on here.
<kuid2:60238:26108:1> shown as unknown, its "Ferrymodern" by vulcan (DLS-version)
<kuid2:143205:10001:1> Prellbock DB
<kuid2:42778:33105:1> gittermast AGD860 N ci
<kuid2:489332:34129:2> Dm-Bf-Deko Bank B
<kuid2:489332:34143:3> Dm-Bf-Sch GleisNr-s 2
<kuid2:489332:34103:3> Dm-Bf-Sch GleisNr-s
<kuid2:489332:34127:2> Dm-Bf-Deko Fahrkartenautomat
<kuid2:489332:34123:2> Dm-Bf-Deko Fahrplan 1
<kuid2:489332:34101:4> Dm-Bf-Sch Stationsschild-s-L
<kuid2:42778:33101:1> gittermast AGD860 N i
<kuid2:489332:34125:2> Dm-Bf-Deko Fahrplan 1+2
<kuid2:42778:33372:2> fahrdraht Ax6060 co
<kuid2:42778:30300:4> fahrdraht Ax6050 cc
<kuid2:42778:30301:4> fahrdraht Ax6050 ci
<kuid2:42778:33374:2> fahrdraht Ax6060 ic
<kuid2:42778:30302:4> fahrdraht Ax6050 co
<kuid2:42778:30305:4> fahrdraht Ax6050 ii
<kuid2:42778:33378:2> fahrdraht Ax6060 oc
<kuid2:42778:30306:4> fahrdraht Ax6050 io
<kuid2:42778:30307:4> fahrdraht Ax6050 iu
<kuid2:42778:30308:4> fahrdraht Ax6050 oc
<kuid2:42778:30309:4> fahrdraht Ax6050 oi
<kuid2:164988:37030:1> tenement Nr30
<kuid2:42778:30310:4> fahrdraht Ax6050 oo
<kuid2:42778:30313:4> fahrdraht Ax6050 ui
<kuid2:42778:33370:2> fahrdraht Ax6060 cc
<kuid2:42778:33371:2> fahrdraht Ax6060 ci
<kuid2:42778:3002:3> flachmast A860 c
<kuid2:42778:3001:3> flachmast A860 i
<kuid2:42778:3003:3> flachmast A860 o
<kuid2:164988:369875:1> tenement Nr6
<kuid2:42778:33107:1> gittermast AGD860 N cu
<kuid2:42778:3027:1> gittermast A860 ic
<kuid2:42778:33100:1> gittermast AGD860 N c
<kuid2:143205:10002:1> Prellbock DB
<kuid2:42778:33106:1> gittermast AGD860 N co
<kuid2:42778:33108:1> gittermast AGD860 N ic
<kuid2:42778:33102:1> gittermast AGD860 N o
<kuid2:35848:32002:1> Pilzlampe
<kuid2:121021:40901:1> station sign old L
<kuid2:74744:28012:1> Streckentelefon
<kuid2:164988:369880:1> tenement Nr7
<kuid2:164988:369965:1> tenement Nr19
<kuid2:164988:37105:1> tenement Nr36
<kuid2:343955:29001:5> VSM Hv-Vsig(1969)
<kuid2:343955:29000:5> VSM Hv-Vsig(1969-L)
<kuid:523:19723447>
<kuid:565830:100222> Rock Single
<kuid:-25:1212> Flowers_Lavender2
<kuid2:661281:85197:1> PBR Cobble Stones 2 - Seasonal
<kuid2:82412:49891001:1> TUME-Street-101
<kuid2:82412:49891006:1> TUME-Street-106
Hi All
Just to confirm.
With the introduction of the TCCP system, and more specifically TCCP2.0, the packaging is essentially in the hands of the creator of the DLC pack. The N3V team don't actually have a hand in packaging the DLC pack, which means that we also don't update assets when the DLC pack is packaged to fix errors.
For DLS content, the latest revision of the asset is used from the DLS.
The exception will be if the person submitting the package has a newer revision to a DLS asset from another source (some creators are unfortunately releasing updates to their own content elsewhere, when an earlier version is on the DLS). In this case, the newer revision will be included in the package, but may not be available from the DLS. But this would be no different to obtaining the newer revision from the source it was released through...
Hi All
Just to confirm.
The exception will be if the person submitting the package has a newer revision to a DLS asset from another source (some creators are unfortunately releasing updates to their own content elsewhere, when an earlier version is on the DLS). In this case, the newer revision will be included in the package, but may not be available from the DLS. But this would be no different to obtaining the newer revision from the source it was released through...
Regards
How does anyone know where the source was?
That, unfortunately, is no different to the current situation found in a number of DLS routes where the creator has thrown in assets from 3rd party web sites and you are left to play the game of "Hunt the asset source". I think that it should be a rule that any asset in a DLC package that is to be labelled as "packaged" must also be uploaded to the DLS, if that exact version is not already there.
An example of this is a few of the scenery assets I made for the Healesville route. They're intended specifically for that route, and weren't intended for DLS release, but they're also not assets I specifically see needing payware encryption. So they become 'packaged' instead.
Download Station' = true filter to the filters list. This will then show only assets that are available from the DLS.
Very good, the thing is though, we now know about this , but what if we don't read this thread? There are far too many instances of obscure fixes to problems that cause endless hassles to route creators that only a few know about ,and the solutions to which are not widely known because there is insufficient explanations by NV3 , there has to be an easier way to make this more obvious to the route creator without having to post pleas on the forum to end our suffering .Thank you for that. I was able to conduct a test of that solution.
I have two installs of Trainz Plus (117092 and 117540) on the same computer.
- Install 1 (117092)
- I ran the recommended filter plus Obsolete = False to eliminate obsolete packaged assets just to make the display simpler.
- Selected all the "Packaged" assets, 7076 of them.
- Right mouse clicked and selected the List Assets in New Window command
- Copied to the clipboard the contents of the Asset KUID filter line which contains the KUID codes of all 7076 assets
- Install 2 (117540)
- Pasted the clipboard list into the Asset KUID filter line
- Deleted the Installed = True filter line
Both lists displayed the same number of assets (7076). In the list for Install 2 all 7076 assets were listed as "Available for download" or "Installed from DLS".
So for the 7076 assets tested, case proven.
My observations.
Very good, the thing is though, we now know about this , but what if we don't read this thread?
As a step towards providing the information, I have amended the Trainz Wiki Page on Understanding the CM Status Labels to include a search for filtering packaged assets that are, or are not, on the DLS.
Problems can arise if the asset included in a DLC package has a higher version number (the :digit> at the end of a kuid2 number) than the "identical" copy on the DLS. This usually occurs when the DLS copy has not been updated to match the DLC copy. See How to Check the DLS Status of Packaged Assets below. If you encounter this problem in a Packaged asset, report it by the Bug Reporting Web Page or the Trainz Help Desk
Problems can arise if the asset included in a DLC package has a higher version number (the :digit> at the end of a kuid2 number) than the "identical" copy on the DLS. This usually occurs when the DLS copy has not been updated to match the DLC copy. See How to Check the DLS Status of Packaged Assets below. If you encounter this problem in a Packaged asset, report it by the Bug Reporting Web Page or the Trainz Help Desk