TRS19 Content delivery strategy causing major route development problems

Stagecoach

If that works it means that it is possible for some malicious bright spark to upload content using that KUID with totally different contents and and a higher build, It seems to me that this would stuff-up the payware route . My proposal would make that impossible as the item would no longer be accessible, and at the same time solve the problem of route payware-locked content. What i propose should take about a day to code and it only involve N3V inhouse and does not affect current content. What you suggest only applies to your route, my suggestion can be applied to all payware routes and can be applied retro-effectively by N3V.

Peter
 
Peter,

Would adding the permit listing container to the assets work? This will remove the assets from being listed in Content Manager and in Surveyor.

privileges
{
permit-listing 0
}
The switch is binary. The zero means do not list.

The onus is now on N3V and the original author to block assets from listing. This can be done simply by opening the content for edit and using a search and update program such as Search and Replace Master to insert the container within the assets as shown.

To unlock the assets, the original author, or N3V for that matter, can do the opposite with a one instead of a zero.

This will effectively prevent the asset from being used by anyone else since it's not listed anywhere. Being in a package and referenced on the fly, the asset can't be tampered with and listed by the end user.
 
Last edited:
Stagecoach

If that works it means that it is possible for some malicious bright spark to upload content using that KUID with totally different contents and and a higher build, It seems to me that this would stuff-up the payware route . My proposal would make that impossible as the item would no longer be accessible, and at the same time solve the problem of route payware-locked content. What i propose should take about a day to code and it only involve N3V inhouse and does not affect current content. What you suggest only applies to your route, my suggestion can be applied to all payware routes and can be applied retro-effectively by N3V.

Peter

The content can only be updated by the creator of the kuid not someone else. You cant just change content for your own and upload it with someone else's kuid. DLC content will become out of date as trainz gets more and more feature updates. Trainz is already going to change some things in the future that could effect content in a payware route. The creator of that content will need to update it and that is by a higher version number. That DLC content with a lower version number on the DLS will get updated at some point on the DLS and will obsolete the payware version in order for that content to keep working. We are not talking about content created for a DLC route but DLS content that is used in the route.
 
The content can only be updated by the creator of the kuid not someone else. You cant just change content for your own and upload it with someone else's kuid. DLC content will become out of date as trainz gets more and more feature updates. Trainz is already going to change some things in the future that could effect content in a payware route. The creator of that content will need to update it and that is by a higher version number. That DLC content with a lower version number on the DLS will get updated at some point on the DLS and will obsolete the payware version in order for that content to keep working. We are not talking about content created for a DLC route but DLS content that is used in the route.

Now that’s a though. I wonder how many of these authors are available to update their content to a version number equal to or higher than the DLC content. Probably vendel, rmm, tume and maybe maddy25 and shorline2. If they updated their content that would account for 11 out of the 15.

Cayden

MGvAAmO.png
 
Let me get something straight.

It is my strong impression from reading the forum posts, that the current system causes problems when a creator's content is locked by it's use in a payware route. N3V must have a valid reason for locking the content, otherwise they would not do it. In a post above, a method of overcoming this is explained, which means that something can be done that N3V has tried to prevent and and this is obviously not well known, if it was easy and well known we would not be discussing it here.

The process I suggested will securely lock content used in a payware route without affecting that same content's use in route creation. It leaves the content open for use and changes while preventing change to that content when used in a payware route. I also believe that it would provide protection when content is used that the creator would like to keep 'off the market'

I have no axe to grind so I'm outa' here.

Peter
 
Last edited:
This is getting real confusing. I have 21 assets from the Oyster Bay Compatible Edition that list as “unknown”. Five are not available on the DLS. I get that, and a couple I have no idea why they are not there. But there are 14 that are on the DLS but with lower KUID numbers. Four of these are even TRS19 compatible. But for all fourteen someone has created new copies with higher version numbers, which are not on the DLS. So these, the bulk of my missing assets are no longer available to me for TRS19 routes I might download (e.g., Oyster Bay) or routes I might create. If it were a T:ANE route I was downloading or creating all 14 would be available to me.

And sadly there is no way I can fix this.

Cayden


Hi Cayden
As I said before, we will be uploading any assets that have a previous version of the asset on the DLS. Based on my investigation of the asset ID provided earlier, the following assets do not have any versions available on the DLS:

<kuid:57230:21755> WP12 rock05
<kuid2:82412:23043:1> TUME-23043-Scrap-Metal
<kuid:661281:75013> Tree Broadleaf 02 Darker
<kuid:661281:75012> Tree Broadleaf 01 Darker
<kuid:661281:85139> PBR TS09 55 Asphalt
<kuid2:57230:21660:1> Donner P12 GreenRock10
<kuid2:122860:100323:2> (TS12) RockCliff Ground seasonal
<kuid2:565830:100115:1> (TS12) MossyRock Ground

If there are others that you didn't report previously, please post them in text format so I can easily copy/paste them and look into them as well.

As noted previously, we try to ensure that updates for DLS assets get put onto the DLS once a DLC pack has been marked as ready for release. But sometimes, especially when our team are busy, this may be missed. In this case I simply need to confirm that the asset has previous versions on the DLS, and then ask our team to upload the latest revision of the asset to the DLS to resolve this issue, however it can take a few days for this to be processed.

In this case I can confirm that the following assets have been uploaded and approved, so should be available from the DLS within the next 24-48 hours :)

<kuid2:565830:100115:1> (TS12) MossyRock Ground
<kuid2:661281:85139:1> PBR TS09 55 Asphalt
<kuid2:661281:75011:1> Tree Broadleaf 3 Lib
<kuid2:124017:27011:4> Cleaner Coal
<kuid2:77573:23001:2> Cable Splicer's Shack (Camp 45)
<kuid2:137715:23001:5> Invisible Speed-Sign
<kuid2:149987:37009:2> FMA instant grass a 30x20
<kuid2:565830:100097:2> (TS12) RockCliff Ground
<kuid2:149987:37014:2> FMA instant grass f 30x20
<kuid2:211025:20298:6> st_rmm_kust2_722_2m
<kuid2:211025:20308:4> st_rmm_kust5_628_5m
<kuid2:211025:20316:4> st_rmm_kust8_496_3m
<kuid2:211025:21006:4> st_rmm_kust19_106_2m
<kuid2:211025:21008:4> st_rmm_kust21_576_2m
<kuid2:121021:40902:2> station sign old XL
<kuid2:124017:10025:4> Steel Industry - Blast Furnace
<kuid2:661281:75012:1> Tree Broadleaf 01 Darker
<kuid2:661281:75013:1> Tree Broadleaf 02 Darker

Our team are also contacting creators of the other assets reported a few days ago to see if they will upload them to the DLS. You may also notice that some of the non DLS assets above have also been made available on the DLS :)

Regards
 
Hi Zec,

I would like to see the following TS2019 asset on the DLS: 103475:24030. ;)

Available in a full TS2019 install, but not in a 'base content' install.
 
Zec and Cayden - thank you both for your help. It will be wonderful to have these assets available for everyone to use.

Thanks
Walter
 
Zec:

Regarding the following items:

<kuid:661281:75012> Tree Broadleaf 01 Darker
<kuid:661281:75013> Tree Broadleaf 02 Darker

In my build 106618 TRS19 these items are shown as Installed, Payware but the Author is shown as Auran as shown in this screenshot:

Tree-Screenshot-1.jpg


BTW both of these items have the same author.

Given this I don't understand why they are payware and you can't have them on the DLS.

Bob
 
Zec:

Regarding the following items:

<kuid:661281:75012> Tree Broadleaf 01 Darker
<kuid:661281:75013> Tree Broadleaf 02 Darker

In my build 106618 TRS19 these items are shown as Installed, Payware but the Author is shown as Auran as shown in this screenshot:

Tree-Screenshot-1.jpg


BTW both of these items have the same author.

Given this I don't understand why they are payware and you can't have them on the DLS.

Bob

Both of these are on the DLS as version 1.
 
General Goods from Base to known versions;

When developing in TANE, Routes can be directly installed into TRS19 by simply dragging the CDP file and downloading missing assets, this works fine for me. In my situation, I am unable to do so in TMR17 because of asset numbering/versioning. I would like to offer my Routes to TMR17 users on the DLC, but so far, no luck. This one asset is preventing me, General Goods. I hope my situation applies to this thread, if not, I am sorry.

TRS19
<kuid:-25:1181> Unknown Asset
<kuid:-25:1187> General Goods, Base, Auran

TMR17
<kuid:-25:1181> Unknown Asset
<kuid:-25:1187> Unknown Asset
<kuid:-25:1177> General Goods, Base, Auran

TANE
<kuid:-25:1149> General Goods, Base Obsolete, Auran
<kuid:-25:1177> General Goods, Installed from DLS Obsolete, Auran
<kuid:-25:1181> General Goods, Installed from DLS, Auran

If this is the right thread, these assets don't transfer over either to TMR17 from TANE, but do to TRS19.

<kuid2:523:1453:2> Unknown Asset <kuid2:523:1453:2> Tree AfricanOlive 03, Built-In, Auran
<kuid2:59545:100259:1> Unknown Asset <kuid2:59545:100259:1> Rock Rubble 003, Built-In, jacktheevil
<kuid2:328583:3822:2> Unknown Asset <kuid2:328583:3822:2> JVC(M)Hedgerow#2a w/trees & shrubs, Built-In, jackvis
<kuid2:1942:25005:1> Unknown Asset <kuid2:1942:25005:1> Suburban House 7, Built-In, tafweb

Thank you
 
Hi Cayden
As I said before, we will be uploading any assets that have a previous version of the asset on the DLS. Based on my investigation of the asset ID provided earlier, the following assets do not have any versions available on the DLS:

<kuid:57230:21755> WP12 rock05
<kuid2:82412:23043:1> TUME-23043-Scrap-Metal
<kuid:661281:75013> Tree Broadleaf 02 Darker
<kuid:661281:75012> Tree Broadleaf 01 Darker
<kuid:661281:85139> PBR TS09 55 Asphalt
<kuid2:57230:21660:1> Donner P12 GreenRock10
<kuid2:122860:100323:2> (TS12) RockCliff Ground seasonal
<kuid2:565830:100115:1> (TS12) MossyRock Ground

If there are others that you didn't report previously, please post them in text format so I can easily copy/paste them and look into them as well.

As noted previously, we try to ensure that updates for DLS assets get put onto the DLS once a DLC pack has been marked as ready for release. But sometimes, especially when our team are busy, this may be missed. In this case I simply need to confirm that the asset has previous versions on the DLS, and then ask our team to upload the latest revision of the asset to the DLS to resolve this issue, however it can take a few days for this to be processed.

In this case I can confirm that the following assets have been uploaded and approved, so should be available from the DLS within the next 24-48 hours :)

<kuid2:565830:100115:1> (TS12) MossyRock Ground
<kuid2:661281:85139:1> PBR TS09 55 Asphalt
<kuid2:661281:75011:1> Tree Broadleaf 3 Lib
<kuid2:124017:27011:4> Cleaner Coal
<kuid2:77573:23001:2> Cable Splicer's Shack (Camp 45)
<kuid2:137715:23001:5> Invisible Speed-Sign
<kuid2:149987:37009:2> FMA instant grass a 30x20
<kuid2:565830:100097:2> (TS12) RockCliff Ground
<kuid2:149987:37014:2> FMA instant grass f 30x20
<kuid2:211025:20298:6> st_rmm_kust2_722_2m
<kuid2:211025:20308:4> st_rmm_kust5_628_5m
<kuid2:211025:20316:4> st_rmm_kust8_496_3m
<kuid2:211025:21006:4> st_rmm_kust19_106_2m
<kuid2:211025:21008:4> st_rmm_kust21_576_2m
<kuid2:121021:40902:2> station sign old XL
<kuid2:124017:10025:4> Steel Industry - Blast Furnace
<kuid2:661281:75012:1> Tree Broadleaf 01 Darker
<kuid2:661281:75013:1> Tree Broadleaf 02 Darker

Our team are also contacting creators of the other assets reported a few days ago to see if they will upload them to the DLS. You may also notice that some of the non DLS assets above have also been made available on the DLS :)

Regards

Thanks Zak.

I have downloaded the updated assets. I am now left with three still missing:

<kuid2:124017:20118:3>
<kuid2:124017:20118:2> Corrugated Fence Maddy25

<kuid2:425700:100027:1>
<kuid:425700:100027> CL Fence Wood – 04 clam1952

<kuid2:425700:101355:1>
<kuid:425700:101355> CL Fence 05 clam1952

All three are on the DLS. As listed in the second line above they all have lower kuid numbers on the DLS.

Cayden
 
Both of these are on the DLS as version 1.

Thanks for pointing that out to me. I had not seen that n3vpolsen had uploaded new versions on 6 August 2020. This will make things easier for me now that they are finally available on the DLS. Many of my routes use those two items.

Bob
 
The two CL Fences, mine, are now on the DLS, had a PM from Rob requesting permission to upload, I would have done it myself if I'd seen this thread. Not sure why they were updated or who by! neither was Rob other than they were 3.1 and now 3.5. For info if anything else of mine has the same problem a pm to me and I can just upload an update to cover.
 
The two CL Fences, mine, are now on the DLS, had a PM from Rob requesting permission to upload, I would have done it myself if I'd seen this thread. Not sure why they were updated or who by! neither was Rob other than they were 3.1 and now 3.5. For info if anything else of mine has the same problem a pm to me and I can just upload an update to cover.

Thanks Malc. I have them now.

Cayden
 
Faulty assets

Hi Zak,

Thanks for uploading the “unknown” assets to the DLS. I now have all of them installed.

There are, however, some other assets that I am also having difficulty with. They are listed as “Faulty”. I have tried a data base repair and that did not work. I also tried Piere’s suggestion (https://forums.auran.com/trainz/sho...ster-Bay-Railroad/page10&highlight=Oyster+Bay Post #137) but that did not work. Oddly enough, exporting the asset as a .cdp file to the desktop, deleting the file from the data base and reimporting fixed all of them. But, on quitting TRS19 and reopening the program the following were again listed as faulty:

<kuid2:151900:100211:2> Lever invisible

<kuid:370528:1164> n railman 2

<kuid2:82412:885182723:1> Road-Wheel-4mx4m-101-201-A-TS12
<kuid2:82412:885182709:2> Road-Wheel-4mx4m-104-TS12

<kuid2:124017:10055:2> Steel-Coil Handling Crane

<kuid2:82412:23041:1> TUME-23041-Scrap-Metal
<kuid2:82412:23032:1> TUME-23032-Beams
<kuid2:82412:23042:1> TUME-23042-Scrap-Metal

<kuid2:82412:23001:1> TUME-23001-Crates

<kuid2:82412:6095304:1> TUME-304-Street-Lamp-WP-9m
<kuid2:82412:6095305:1> TUME-305-Street-Lamp-WP-8m
<kuid2:82412:6095307:1> TUME-307-Street-Lamp-WP-7m

Strange that they are okay until I close the program then revert to faulty.

Cayden
 
Hi Zak,

I have all of the assets listed in the above post (Post #176) in T:ANE. They are listed as payware that it would appear that I own, as they are not listed as faulty and work fine.

I have tried saving them from T:ANE and importing them into TRS19 but they come up a faulty.

Cayden
 
The two CL Fences, mine, are now on the DLS, had a PM from Rob requesting permission to upload, I would have done it myself if I'd seen this thread. Not sure why they were updated or who by! neither was Rob other than they were 3.1 and now 3.5. For info if anything else of mine has the same problem a pm to me and I can just upload an update to cover.


I have a horrible suspicion that unofficial modifications to existing assets by the person creating the DLC is a prime reason why so many assets are now "Unknown/Missing". I suspect that if an asset shows an error/warning or is marked as being for an obsolete version of Trainz, there is a great temptation to simply go in and "correct" the problem with the asset and include this new version in the DLC without any reference to the original creator. Are there any checks made in the DLC upload process to check that any assets used that are not at the same version level as on the DLS are authorized by the original creator? Malc's statement appears to suggest that no checks are made.

If I tried to upload an unauthorized, updated version of an asset the DLS, I would expect it to be rejected. Why therefore is it apparently permissible to do this in a DLC product? It appears that it is OK to sell pirated versions of assets via the DLC.

Mike
 
I have a horrible suspicion that unofficial modifications to existing assets by the person creating the DLC is a prime reason why so many assets are now "Unknown/Missing". I suspect that if an asset shows an error/warning or is marked as being for an obsolete version of Trainz, there is a great temptation to simply go in and "correct" the problem with the asset and include this new version in the DLC without any reference to the original creator. Are there any checks made in the DLC upload process to check that any assets used that are not at the same version level as on the DLS are authorized by the original creator? Malc's statement appears to suggest that no checks are made.

If I tried to upload an unauthorized, updated version of an asset the DLS, I would expect it to be rejected. Why therefore is it apparently permissible to do this in a DLC product? It appears that it is OK to sell pirated versions of assets via the DLC.

Mike

That may be the case. For example, <kuid2:82412:6095305:1> in my T:ANE is trainz-build 3.2, which would not be compatible with TRS19. Yet, whamm0's Oyster Bay - Compatible Edition route is a TRS19 route and uses this (and the others below) as a compatible asset with the same kuid number, i.e., <kuid2:82412:6095305:1>. I didn't think that was possible.

I have the above assets (Post 176) in T:ANE. They appear as dependencies of <kuid2:82412:104611:9> Milwaukee Road Avery-Drexel, a built-in route and <kuid2:82412:104711:7> Season Town Northern RR, payware route I apparently installed some time ago. 13 of the 15 assets are dependencies of <kuid2:82412:104611:9> Milwaukee Road Avery-Drexel, a built-in route.
In T:ANE all are trainz-build 3.2. They shouldn't be compatible with TRS19 but according to whamm0 they are.

<kuid2:82412:6095305:1> TUME-305-Street-Lamp-WP-8m
<kuid2:82412:104711:7> Season Town Northern RR (Installed)

<kuid2:82412:22013:1> TUME-22013-Lamp-No-Pole-65
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel (Built-in)

<kuid2:82412:23001:1> TUME-23001-Crates
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:6095304:1> TUME-304-Street-Lamp-WP-9m
<kuid2:82412:104711:7> Season Town Northern RR

<kuid2:82412:23005:1> TUME-23005-Crates
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23007:1> TUME-23007-Crates
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:6095307:1> TUME-307-Street-Lamp-WP-7m
<kuid2:82412:104711:7> Season Town Northern RR

<kuid2:82412:23008:1> TUME-23008-Crates
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23041:1> TUME-23041-Scrap-Metal
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23032:1> TUME-23032-Beams
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23009:1> TUME-23009-Crates
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23042:1> TUME-23042-Scrap-Metal
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23044:1> TUME-23044-Scrap-Metal
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:23004:1> TUME-23004-Crates
<kuid2:82412:104711:7> Season Town Northern RR
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

<kuid2:82412:6098304:1> TS12-8304-Wood-Pole
<kuid2:82412:104611:9> Milwaukee Road Avery-Drexel

Cayden
 
Back
Top