The updates introduce some issues that are easily resolved but it takes a bit of set up and prepping first.
Some of your missing dependencies could very well be related to missing built-in (packaged content). At the Launcher, click on the Content Store button. Download and install any package that is available for you to install. If there are a lot of content packages, only download a few at a time, otherwise the software will lock up.
Once that's complete, you need to set up Content Manager so that all the columns are shown.
Right-click on one of the columns and you will see the missing columns. Click on one to add it and repeatedly right-click and add the others one at a time. You can then rearrange the columns how you want and resize them much like you do in a spreadsheet.
I set up the columns like this:
Type - Status - Name - Build Version - Author Username - Asset ID - File Size - Modification Date - Installation Date - Upload Date
By showing all the columns, this will help you later on as you search for data.
Create some filters:
Out of Date and not packaged:
Installed - True
Out of date - True
Packaged - False
To set up a filter, click on the small arrow next to Install and then click the plus sign (+) located on the right to add other filters to the query.
Scroll the list and add Out of date and set that to True.
Add in Packaged the same way. Save the custom filter. I call mine Out of Date and not packaged.
Clicking on this will show any assets that are available for updating that are not built-in or packaged. Today, in TRS22 built-in assets are packaged for the most part.
With out-of-date assets shown, right-click on them and choose download to bring down the update.
Any updated assets that are downloaded will become obsolete currently installed assets, and obsolete assets can be deleted because that means that updates have been downloaded.
The faulty filter is confusing because it's all inclusive. To make things easier, create two filters from this - Faulty Only and Missing Dependencies Only.
Switch the to the Faulty Assets filter and let it run. Depending upon how much content you have installed, this can take a while to populate the screen if it does. Don't panic if anything is shown.
Where Faulty is at the top, click on the small arrow.
Remove each of the lines below by clicking on the minus sign (-) next to missing dependencies on the right and on faulty dependencies. If there are any ANDs or ORs, remove those too.
Save this as Faulty Only.
Load up the all-inclusive Faulty filter again and remove everything except for Missing Dependencies and save that as Missing Dependencies Only.
Dealing with Missing Dependencies.
When routes are installed, they don't include any dependencies. Routes located on the DLS will download their dependencies automatically. If a route or session has been downloaded from a third-party site or was created locally and installed from a cdp, the assets need to be installed or downloaded manually.
Right-click on your route and choose download.
This might take a bit of time depending upon the size of the route and the number of dependencies. If you are lucky, everything came from the DLS and that will remove your dependency issue.
Dealing with Faulty assets, more importantly dealing with Faulty assets AFTER a DBR/EDBR.
Change to the Faulty - only filter you just created. The query may take a bit to run. Once the query has finished and the screen is populated...
Click on one of the assets.
Press CTRL+A to select them all.
Right-click and choose View Errors and Warnings.
The process will run and will show errors and warnings, and hopefully zero errors and a bunch of warnings. Sometimes, the screen doesn't clear and you need to change to another filter then repeat the Faulty-only to refresh the screen. Hopefully this will clear the screen.
With this version, there are some Russian and Ukranian assets, sessions, and routes that are faulty due to assets that can't be updated due to authors being unavailable for the obvious reason. All total, there's about 18 assets and these can be ignored.
We recommend you check for additional content package updates if there are any available. These are over and above what you have downloaded from the Content Store and are those assets that are updates to those in the packages and are placed on the DLS.
Click on your Out-of-date and not Packaged filter.
Click on the arrow next to Installed to expand the query parameters.
Next to packaged, change the false to True.
Nearly everything here has updates except for the following. A couple of Russian vehicles, some people, and the above-mentioned Russian or Ukranian routes, any trains from the store, and any routes.
Highlight anything else and right-click on it.
Choose List asset versions.
This will open a new window showing the version.
Click on the asset with Available for Download, new version available, shown in the status.
This will update the asset or assets if you clicked on more than one, and you can close the asset-versions window. The obsolete assets though, can't be removed because they're packaged.
Hope this helps.
