class 43 interior

RobWed

Active member
I have <kuid:-25:32> listed as an obsolete asset. A look at its dependents shows seven trains I downloaded from the DLS. Listing asset versions of the obsolete dependency gives me three assets each with different author IDs but all named Auran. Two are obsolete. Should I be updating the config file of these 7 trains to reference the non-obsolete instance?

I should add that these seven trains are all the most recent available on the DLS
 
I have these two in TRS2019:
<kuid:-25:1123> class43 interior
<kuid:-25:1173> class43 interior both are version 1.3. Listing asset versions does not give me anything newer. My TRS22 is rebuilding the database so I can't check it, but I think it fair to say that if it is listed as obsolete it has already been replaced by one of the newer versions, or it would say "Newer Version Available", so you should be fine to delete the obsolete version.
 
I have these two in TRS2019:
<kuid:-25:1123> class43 interior
<kuid:-25:1173> class43 interior both are version 1.3. Listing asset versions does not give me anything newer. My TRS22 is rebuilding the database so I can't check it, but I think it fair to say that if it is listed as obsolete it has already been replaced by one of the newer versions, or it would say "Newer Version Available", so you should be fine to delete the obsolete version.
This is the same for me and mine is marked as payware in TRS-Plus.
 
I should have given the other two asset numbers...
<kuid:-25:1173>
<kuid:-1:101168>, listed as obsolete.

I guess it just means the update was given to someone else at Auran each time rather than the person who previously made it.

I suspect the payware will be one or other of the ECML mainline DLCs as one of the train authors says they are dependencies.
 
Which raises another question from me...
When an underlying asset is updated does this flow through automatically to any assets that utilise it or is it up to the author of the utilising asset to do an update?

If it is the latter, as I suspect, can the utilising asset still work with an obsolete dependency?
 
Which raises another question from me...
When an underlying asset is updated does this flow through automatically to any assets that utilise it or is it up to the author of the utilising asset to do an update?

If it is the latter, as I suspect, can the utilising asset still work with an obsolete dependency?
Technically, the assets should use the replacement superseding asset automatically. There have been some issues off and on when this happens.

This explains the kuid system in detail:

 
Back
Top