Manage Content saids no fault, but in game it said it does.

So sometimes whenever i open up trainz. there are certain trains that for some reason had faults. then when i tried to go and check the issue if whats wrong with the train using the manage content page and look up the name of the train. but then it saids that the train is completely fine not faults no nothing.

and up until now there are trains that is STILL showing that it had faults/missing deps when i had trainz opened up. but then when checking the manage content page and checking the trains that when in game shows that is has faults/missing deps. they are completely fine. even when i restarted my laptop. certain trains are just not usable in game AT ALL even tho in manage content it shows that its fine.

when in game:


when in manage content:


i just dont know how to fix this. this must be a bug or something?

Try right clicking in content manager and go for view errors and warnings.

Cheerio John

And check the dependencies, possibly that's where there is a problem.

johnwhelan said:

Try right clicking in content manager and go for view errors and warnings.

Cheerio John

Click to expand...

weird enough. take the class 800s i have for example. i was able to use those before but then its just unusable up until the point and about the viewing of warnings and errors. it only gave me this. something about texture problems??

but then another case. the packaged MK2s.

i tried clicking on the view errors and warnings pages and for one of the MK2s listed above its just this



packaged, no errors whatsoever, even viewing on the error and warning page shows nothing for the packaged MK2s yet it showed me nothing and not useable at all when in game.

Check open for edit and revert anything in there to original.
Check dependencies and anything showing as modified revert to original.

clam1952 said:

Check open for edit and revert anything in there to original.
Check dependencies and anything showing as modified revert to original.

Click to expand...

ok so somehow. it worked for most of the models. i just tried it on the class 800s and one of the dependencies is <kuid2:60850:88000:5> MaxSpeedPermittiedSpeedIcon.

its so inconsistent of when it just suddenly erroered out for no reason. it had faults when i click the list of dependencies list. but nothing showed up when i click view warnings. shouldnt that have showed up on the warning/error page?

but then the packaged MK2s have this issue:

this didnt even get any sort of modifying, i checked view error/missing dep page, the list dep page. i cant even have that to revert to original for some reason and this was packaged in what am i suppose to do

What really helps with situations such as this is setting up a couple of new filters so that you only see specific data clearly. For this situation, I have two that are specific to faulty and missing dependencies because Trainz lumps both into the same, while technically can be correct, only confuses things because there's no way of discerning between the two quickly.

My Missing dependencies only filter is setup with:

Installed True
Missing Dependencies True.

Faulty-Only filter is setup with:

Faulty True.

There is nothing in there for missing dependencies or other unnecessary information.

If everything appears clear, then you may need to check deeper and perhaps run an Extended Database Repair (EDR).

To run and EDR, press the CTRL-key at the same time when selecting Rebuild database from the Developer menu on the Launcher.

- Once the EDR has completed, view errors and warnings.
- Select any assets that are in the window, right-click and choose View errors and warnings.

This will reset the warnings and the process will state how many errors there are. Warnings can be ignored.

- Once completed, close Content Manager and open it up again and view the errors a second time.

This will refresh the database and ensure your list is clean.

- If there are any remaining errors, then these need to be investigated.
- Right-click and use the view errors and warnings again. Expand the small caret to view the complete message.

Sometimes, missing dependencies are dependencies of dependencies which can cause all sorts of problems. This requires digging and drilling down to find the culprit.

I have exactly the same problem with assets appearing as faulty but no errors and no warnings. It messed all my route including packaged ones . my TRS22 now is impossible to use.in fact you cannot import older routes or asset without messing the whole thing.
There are no way to fix the problem and i am fighting with this issue since i purchased TRS22 two weeks ago. I decided to suppress all trs22 files and download it again for the third time but if the same problem occur i will asq refund... TRS19 was fine. I never had so many issues with a new TRS version.
I am not a computer specialist and i am probably to nuts to use this game now...

How are you importing your TS19 data to TRS22? Sounds like you are not doing it correctly.

Hello,
I import using cdp files i do routes and dependencies one by one. I don't know any other simple way.

capitol said:

Hello,
I import using cdp files i do routes and dependencies one by one. I don't know any other simple way.

Click to expand...

In TRS19 open for edit all assets that are not Base, Builtin, Payware or packaged. In TRS22 import folder and select TRS19s editing folder.
Check open for edit, anything in there after importing, revert to original as you will have overwritten a builtin asset that wasn't in TRS19.
Then run a database repair before doing anything else.
Payware DLC you download again from the Content Store.

I had the same problem with some locomotives that I downloaded. In Content Manager I clicked on the Loco giving me problems, then in the Content tab, List Dependencies, then downloaded the missing items. Turned out that most were expired, out of date, no longer used, (I forget the exact terminology) items, but once downloaded things worked fine. If I deleted those same items the problem returned. Weird.
I ended up finding similar, better locos, and deleted the aforementioned ones.

warzog said:

I had the same problem with some locomotives that I downloaded. In Content Manager I clicked on the Loco giving me problems, then in the Content tab, List Dependencies, then downloaded the missing items. Turned out that most were expired, out of date, no longer used, (I forget the exact terminology) items, but once downloaded things worked fine. If I deleted those same items the problem returned. Weird.
I ended up finding similar, better locos, and deleted the aforementioned ones.

Click to expand...

That's because the obsolete assets were still located on your hard drive and where then referenced when you removed the updates.

Trainz works this way and has since the early days.

Each asset is given a unique ID based upon a combination of your User-ID + the asset ID. This was called the Kewl User ID, or KUID system.

In the early days, assets only had KUID:xxxxx:xxxxxx... with no version. The only way to control the version was for the content creator to create a new asset and place the old KUID into an obsolete table. While this works, it's prone to errors and we've had some rather interesting results such as a factory building turning into a canal lock. All it took was a typo in the asset side of the KUID, a simple transposition of digits.

Here's a simple KUID

<kuid:511506:100309> RDG Wood Interlocking Tower - No Signs

The new method is a bit more error-proof. This is the KUID:2 system. Using KUID2:xxxxx:xxxxxx:x format. The last digit, following the last : is the version. There can be 127 versions with the last one being 126 (This is zero-inclusive). Using this format, a content-creator can update an asset, then up-version the new one by simply changing the asset-version instead of modifying the config.txt further and introducing an error.

<kuid2:132952:131602:1> SAM Elevator - Kutno, Poland

Now getting back to your issue.

In order to keep the current version, you need to delete the now obsolete assets installed. To help myself with that process, I have setup a couple of filters in Content Manager.

I first check, almost daily, for new assets.

Out of Date - No Payware.

Installed = True
Out of date = True
Payware False.

The reason for the Payware False setting is because if set to true, all payware is displayed and not the out-of-date ones!

The other filter is:

Installed = True
Obsolete = True.

This will display all the old assets that can be deleted but not any DLC or payware that was updated. Anything displayed here can be deleted.

Now with that said, there have been times when an update has broken something and removing the obsolete asset has caused an error such as a missing dependency or something to fail. The only thing you can do is delete the new version and reinstall the old one. This is done by viewing asset versions - right-click and choose view asset versions. You can then install the out-of-date version and contact the author to fix his or her update.