Fix or delete these?
- Thread starter autodctr
- Start date
You can delete them from CM. I have these versions, which show as packaged, but show no dependents, so not sure how packaged. They are sessions for Niddertalban - TRS2019
<kuid2:212731:780008:4> 3DZUG DRG Class 05 - S1501
<kuid2:212731:780009:3> 3DZUG DRG Class 05 - S1502
<kuid2:212731:780008:4> 3DZUG DRG Class 05 - S1501
<kuid2:212731:780009:3> 3DZUG DRG Class 05 - S1502
This is because they are packaged.
There have been a lot of packaged asset updates. The best way to get them is to set up a filter in Content Manager.
Installed - true
Packaged - true
Out of date - true
You'll see anything that has updates.
Highlight the assets and choose Show asset versions which will open a new window.
Right-click on the assets and they will download.
There are some that can't be updated. Some old Russian automobiles due the author being banned, some Neoclei people, and a piece of Russian track. In addition to these regular assets, are payware trains and consists, and routes, which need to be done through the Content Store.
Are there any versions to download?
blueodessey
Well-known member
It works perfectly, 122 Assets needed updating, 5 would not update, since CM said location unknown. However in the abstract, 122 upgrade with just 3 problem children, one can easily live with that.
And I saved a new Filter with your name on it.. Thank you John.
Thank you. I use this every time I use Trainz to ensure I keep everything up-to-date. Setting packaged to false, and you can see all the DLS assets that have updates available.It works perfectly, 122 Assets needed updating, 5 would not update, since CM said location unknown. However in the abstract, 122 upgrade with just 3 problem children, one can easily live with that.
And I saved a new Filter with your name on it.. Thank you John.
With my name on it. LOL!
None.
Choose View asset versions. Sorry, I typed the wrong word and just realized that now.
Have you tried a database repair? That may fix that problem as well. I've seen where even though updates were installed that assets still showed faulty. Running a DBR cleared that up. This was a long time ago and I didn't think of that before since it's been a while.
It is a right-click menu item, so select the assets, right-click and select "List Asset Versions"
Yes. The 6 errors are most likely related to the packages you've installed and the error is related to precaching of packaged assets whose version is newer than the one referenced on the server. This error can be ignored. The warnings are related to the inability to precache obsolete assets and other things such as meshes that aren't 500 polygons or smaller. Again, nothing to worry about.
I recommend checking faulty assets. If you see any faulty assets, right-click and view errors and warnings. This is a normal process we've established ages ago after an EDBR. You may have to exit that view in Content Manager and view it again to refresh the database.