So I did some analysis of the build version of all the assets I have...

[ek.skirl]

A newer asset version will automatically obsolete the old one installed when the new asset is downloaded.

That's clear, but was not the question:

• Would Trainz exchange in installed route/sessions installed assets automaticaly by newer asset versions, if newer exist on download station?
• Would Trainz exchange while route/session download there in installed assets automaticaly by newer asset versions, if newer exist on download station?

 

[JCitron]

That's clear, but was not the question:

• Would Trainz exchange in installed route/sessions installed assets automaticaly by newer asset versions, if newer exist on download station?
• Would Trainz exchange while route/session download there in installed assets automaticaly by newer asset versions, if newer exist on download station?

Item 1. No unless you download an update.
Item 2. Yes, if you download a route without the asset, then it'll pick up the latest.

Keep this in mind. If you have the asset installed and you purchase a DLC route, there's a possibility that the same asset will then be updated and your currently installed version will now be obsolete.

 

[ek.skirl]

if you download a route without the asset,

Thats logical too.
But Q2 ask about if the route/session on DLS has installed an older version of an asset, but a newer version of this asset exists on DLS:
a) newer asset isn't local installed and
b) newer asset is local installed.
Download the rout/session and install it local. What asset version the downloaded route/session uses if I run it? Older or newer asset version?

 

[JCitron]

Thats logical too.
But Q2 ask about if the route/session has installed an older version on DLS but a newer version of the asset older installed on it exists on DLS: a) newer isn't local installed and b) newer is local installed.

You'll still receive the latest version of the asset even if the route specifies the old one because the old version of the asset has been obsoleted on the DLS.

The only time you run into a problem is when the new version of the asset is installed but the old one is unknown. This occurs with DLC being installed and then installing a route from disk, such as from a backup, or from a third-party website. The old route is still looking for the old asset because Content Manager can't find the new version for some reason. This is a quirky bug that N3V has been looking into but it's very difficult to pin down. I worked with the QA Team on this one for a bit.

 

[ek.skirl]

@JCitron Firstly a sorry for posting text accidentally to fast and secondly for staying so hardly.

You'll still receive the latest version of the asset even if the route specifies the old one because the old version of the asset has been obsoleted on the DLS.

If so, there shouldn't be any obsolete assets downloaded from DLS to me, or could, if not Base or Build-in?

Picture Thread 180250 #45
The principle process of obsoleting is clear to me, but handling in route/sessions, if the older asset is installed yet, isn't.
And what is the difference between to "be obsolete" and "existing newer version"? Both of them exist.

 

[JCitron]

@JCitron Firstly a sorry for posting text accidentally to fast and secondly for staying so hardly.

If so, there shouldn't be any obsolete assets downloaded from DLS to me, or could, if not Base or Build-in?

Picture Thread 180250 #45
The principle process of obsoleting is clear to me, but handling in route/sessions, if the older asset is installed yet, isn't.
And what is the difference between to "be obsolete" and "existing newer version"? Both of them exist.

You are interpreting this incorrectly. This means that you had these installed from the DLS and now they are obsolete due to these assets being updated either by installing DLC which is all inclusive, or you installed the update yourself.

You can delete these obsolete assets with no harm done because these obsolete versions are no longer being referenced and are only taking up disk space.

 

[ek.skirl]

You can delete these obsolete assets with no harm done because these obsolete versions are no longer being referenced and are only taking up disk space.

I'm reflecting still about the different meanings of "obsolete" and "newer version abvilable". Is it possible that "obsolete" means there is no dependant on that asset installed yet and "newer version abvilable" tells what iot says and indicates that this asset is a dependency of an installed asset?

 

[stagecoach]

Asset ~train sim v2~ is installed. Asset shows newer version available. This means ~train sim v3~ is on the DLS and ready for downloading or it has been found in a DLC package which you can't download as an individual asset.
Obsolete means that you downloaded ~train sim v3~ and ~train sim v2~ is no longer being used but is still installed. Trainz only reads the latest version v3.
If you download a route with ~train sim v3~ on it and you only have ~train sim v2~ installed it will show as a missing dependency.
If you download a route with ~train sim v1~ on it and you only have ~train sim v2~ installed it will use the newer version v2.

 

[ek.skirl]

@stagecoach Thank you for that clearifacation to me.

found in a DLC package

This is what one big hole is filling. So its possible that the newer version is only packaged but not stand alone.
And obsolete means really that there is no reason to hold it installed because it is nowhere used localy.
Thank you.