Status = Modified

[SteveTr]

I have an asset (ie., BNSF ES44C4) where the Status=Modified when browsing in Content Manager. I must have been exploring the locomotive's config file as I always copy the original as a "****_org.txt" file in case I screw something up. When an asset has not been messed with, it displays the Status as its origin such as Packaged, Built-in, Installed from DLS, etc.

How can I identify the original status (origin) once a mod has been performed?

Thanks.

 

[Forester1]

Is there any chance the asset was downloaded from a third party site? When you import those they get the status of "modified" for some reason. You can also try "Revert to original", and then you should be back where you started.

 

[SteveTr]

Is there any chance the asset was downloaded from a third party site? When you import those they get the status of "modified" for some reason. You can also try "Revert to original", and then you should be back where you started.

I believe the asset (loco) was included in a Route that I purchased however I am not certain. I went back into the config file and reverted back to the original Config and it still shows up as Modified. As you suggested, performed a Rever to Original and that did not make a difference, still showing up as modified. I guess if I really want to keep up with this stuff, I need to document my changes but that seems like a real hassle.

Thanks for your response.

 

[JCitron]

I believe the asset (loco) was included in a Route that I purchased however I am not certain. I went back into the config file and reverted back to the original Config and it still shows up as Modified. As you suggested, performed a Rever to Original and that did not make a difference, still showing up as modified. I guess if I really want to keep up with this stuff, I need to document my changes but that seems like a real hassle.

Thanks for your response.

What route is this?

 

[SteveTr]

What route is this?

Update, I found where I did purchase the asset from JointedRails. I reinstalled the DLC and it had a number of "Open for Edit" files. I can only presume that updating the open files moved the status from "Packaged, Payware" to Modified. Having said that, I guess my original question is not relevant.

 

[JCitron]

Update, I found where I did purchase the asset from JointedRails. I reinstalled the DLC and it had a number of "Open for Edit" files. I can only presume that updating the open files moved the status from "Packaged, Payware" to Modified. Having said that, I guess my original question is not relevant.

That explains it. Your question was very relevant. Many people ask this all the time and this is very helpful.

Whenever there are assets installed from third-party sites such as Jointed Rail that are already installed, you need to revert those to original because they are the same version that is already installed. With built-in and DLC assets, this is more important because things can become messed up.

As always, there are exceptions, as you can imagine if there's an update to the same asset and the asset hasn't been up versioned.

In Trainz, all assets are assigned a user-asset ID called a KUID. The latest iteration is KUID:2:USER_ID:ASSET_ID:Version_number.

If the asset is updated, the version number will be incremented and the original will be obsoleted.

 

[SteveTr]

Update, I found where I did purchase the asset from JointedRails. I reinstalled the DLC and it had a number of "Open for Edit" files. I can only presume that updating the open files moved the status from "Packaged, Payware" to Modified. Having said that, I guess my original question is not relevant.

The route I thought it may have come with was Midwestern Rails. The online description does not list out the detail of assets that comes with the route.

 

[JCitron]

The route I thought it may have come with was Midwestern Rails. The online description does not list out the detail of assets that comes with the route.

You can find out though.

In Content Manager, search for Midwestern Rails. This is a DLC route from N3V and will show as packaged if you have the status Packaged, Payware.

Right-click on the name and choose List Dependencies. A new window will open up showing the route dependencies. In order to see the session dependencies you need to do the same for the various sessions. You can select them all and a single window will open up showing the dependencies of all the selected sessions.

 

[TSwenson]

As JCitron said the version number on the end of the KUID should tell you what the "newest" one is... provided the creator did everything correctly... although the creators and NV3 do seem to be doing a better job in that regard.
Listing the dependencies on a route/session should tell you what it has, conversely you can select the asset and use "list dependent" and get what it is used in (on YOUR installation only). Sometimes you need to restart if you have had CM open for a good long while (weeks).

 

[SteveTr]

Great feedback. Thanks everyone.

It for sure was not included in Midwestern Rails. I will search the rest of the routes I have and just for grins