Trial & Error With My Assets

[Dinorius_Redundicus]

Tom,

I don't actually have an interest in the loco's (or any loco's for that matter), and I don't think I can unscramble what you'll need to do to with interiors etc.

However, it seems to me that you could benefit a lot by learning how to use CM to analyse assets and uncover the causes of their faults. Rather than guess what the unknown/missing asset in the loco’s is, this is how I approached it using the "A" loco as an example. Spoiler alert; it turned out to be a hornsound, not part of an Interior.

Read on if you want to follow the analysis. First up, select the loco;

Then right-click on it and, from the menu that pops up, choose "List Dependencies Recursively". This brings up a list of the loco's direct dependencies, plus any sub-dependencies of those. There were 11 dependencies listed in total, including the mysterious "unknown".

The “unknown” <kuid2:569535:100237:1> must be the missing asset since if you check the assets in that list, none of them depend on the unknown kuid. That means it must be a direct reference of the loco config.

So let’s inspect the config and see where that direct reference is. Here is a view of the config.txt in AssetX, with the reference to <kuid2:569535:100237:1> highlighted in yellow. The tag indicates the unknown is a hornsound;

We still don't know where to find that hornsound, but we do know its kuid, its author's trainz nickname, and the fact that davesnow, the creator of the original loco, found it somewhere other than the DLS. You could possibly quiz him about where to get it.

Here endeth the lesson, but I hope you can see that CM and a bit of analytical thinking go a long way when it comes to sorting out what is wrong with Trainz assets.

 

[Railroader1970]

Tom,

I don't actually have an interest in the loco's (or any loco's for that matter), and I don't think I can unscramble what you'll need to do to with interiors etc.

However, it seems to me that you could benefit a lot by learning how to use CM to analyse assets and uncover the causes of their faults. Rather than guess what the unknown/missing asset in the loco’s is, this is how I approached it using the "A" loco as an example. Spoiler alert; it turned out to be a hornsound, not part of an Interior.

Read on if you want to follow the analysis. First up, select the loco;

Then right-click on it and, from the menu that pops up, choose "List Dependencies Recursively". This brings up a list of the loco's direct dependencies, plus any sub-dependencies of those. There were 11 dependencies listed in total, including the mysterious "unknown".

The “unknown” <kuid2:569535:100237:1> must be the missing asset since if you check the assets in that list, none of them depend on the unknown kuid. That means it must be a direct reference of the loco config.

So let’s inspect the config and see where that direct reference is. Here is a view of the config.txt in AssetX, with the reference to <kuid2:569535:100237:1> highlighted in yellow. The tag indicates the unknown is a hornsound;

We still don't know where to find that hornsound, but we do know its kuid, its author's trainz nickname, and the fact that davesnow, the creator of the original loco, found it somewhere other than the DLS. You could possibly quiz him about where to get it.

Here endeth the lesson, but I hope you can see that CM and a bit of analytical thinking goes a long way when it comes to sorting out what is wrong with Trainz assets.

Thanks for these schematics. I still use TS12 and the numbers check out there. However, when I get TRS19 or TRS22, then I'll re-read what you typed and see how it goes.

 

[Dinorius_Redundicus]

I'm pretty sure you can use TS12's Content Manager to do the same things. Error- and dependency-checks have been in CM for quite a while.

 

[oknotsen]

I tried to obtain all of your assets listed in Oknotsen's post to see if they were faulty in TANE. I could only find these 2 on the DLS;

The other 18 were likely "hidden" after upload and put on the CRG list. A common reason for that is the build being below 3.5.
So up the build to 3.5. If that doesn't result in any errors; lucky you, easy fix. If it does, those are your errors to fix.

 

[Railroader1970]

The other 18 were likely "hidden" after upload and put on the CRG list. A common reason for that is the build being below 3.5.
So up the build to 3.5. If that doesn't result in any errors; lucky you, easy fix. If it does, those are your errors to fix.

Copy that, I'm on it. Thanks for the info.