How to find unknown Jointed Rail assets

[rwk]

How do you find missing Jointed Rail assets when Google can't find them? These are in a DLS route. Also, who is s301? There are a few assets by him that turn up no hits on Google as well. I don't have access to the kuid index anymore. These DLS routes leave you on your own to find the source of unknowns.

<kuid:506034:9572> Wearsprada
<kuid:175455:101510> 22alpha

 

[Forester1]

Sadly, even JR assets get packaged.
<kuid:175455:101510> JR Wastecor 90ft Railroad Scale packaged in <kuid2:92924:100080:16> Coal Country
<kuid:506034:9572> JR USA road short dotted line L-7m packaged in <kuid:495739:100076> Legacy of the Burlington Northern v3 Multiplayer, <kuid2:506034:100013:2> Legacy of the Burlington Northern v2

 

[HPL]

• <kuid:506034:9572> is also in the dependency pack if you buy the route from JR.

• <kuid:175455:101510> is also available in:

— NARM's "GILA Railway" (in GILA Release Route Deps.cdp)
— Jointed Rail's "Coal Country" v1 (in Dependencies.cdp) and v2 (in Coal_Country_2.0_nonDLS.cdp)
— Jointed Rail's "Military Mega Pack " (in Route Dependencies.cdp)

 

[rwk]

I hate when freeware routes use assets that are only available in payware packages. There are a bunch of DLS routes that do this. I see a lot of unknown Roys Trainz assets (houses?) that are only available in his payware Canada routes by N3V and assets by tume which are probably payware.

 

[Forester1]

I understand, but I think it is more a problem of assets that should probably be DLS getting packaged up into payware routes. It seems odd to me that every blade of grass, piece of road, or telephone pole used in a payware route must automatically be termed "Packaged" or "Packaged Payware" just because it happened to be included in a payware route. To me, only the map itself plus maybe any major unique assets the creator wants to protect should be termed packaged, and the rest returned to DLS.

 

[HPL]

Sometimes dependencies of payxare routes are freely downloadable.

 

[rwk]

Not if they are off the DLS and not on any third party site and only included with a payware route by N3V, or Jointed Rail, etc. Then you must buy the payware route in order to get the missing assets for the freeware route. A lot of route creators don't tell you where non-DLS assets come from so you are left in the dark trying to find them and you wind up here asking where to get them because Google turns up no match and the kuid index is done.

 

[Forester1]

Yes, that is the reason the Missing KUIDs thread is up to 242 pages, and sadly, a lot of those requests remain unanswered as the locations are lost in obscurity. And of course, some sites are no longer with us.
Jointed Rail though, I would think would have the option of separating out some of their assets and offering them with their freeware, if they chose to.

 

[wreeder]

DLC products are required to include all assets as part of the download. I assume this is for ease of installing DLC addons. Sadly, it causes problems if people use those assets on a route they upload to the DLS. It is an imperfect system.

 

[Forester1]

I get what you are saying @wreeder, but for someone like JR, they could ALSO provide some of the assets separately. And it seems so could N3V for that matter. The problem seems to be that their classification system is exclusive in that once an asset is "packaged" it cannot also be "Available for download" for others not purchasing the entire DLC package. I also wonder if that is why I am seeing so many "upversioned" assets that are not available anywhere. They are for new mobile apps or maybe XBox, but then people are using them on routes and the rest of us are sitting with older versions wondering where these upversions might exist. The best we can do is "upversion" the version we have, which I am hesitant to do for multiple assets.

 

[wreeder]

Yep, that is why packaged assets are upversioned. If the DLC attempts to install an asset that is already installed then it would be lefted open for edit. Another confusing situation for newbies. So the official fix is to increase the version number by one and include it. Another short sighted fix.

 

[Forester1]

Short sighted indeed. Thanks for the explanation, but the answer definitely creates its own problems.

 

[wreeder]

Yep, classic spaghetti code programming logic.