How do I update build number for rolling stock and engines?

Od19

Member
I'm not able to place some engines and rolling stock on the tracks. Most of them are from DLS, and the other ones are my own content. I found this was due outdated build number, after checking the warnings. How do I go about updating them?
 
If you are only getting warning messages, not error messages, then they can be ignored.

In general I would never advise anyone to "solve" a problem by increasing the build number of an asset. The build number tells Trainz which compliance tests can be applied to an asset when it is loaded into Surveyor/Driver. So by increasing the build number you run the risk of applying different (and perhaps even stricter) compliance tests that the asset may completely fail, producing an error instead of a warning.

A few questions to help me understand your problem.

Do the engines and rolling stock items that you cannot place appear in the Trains (F7) object selection tool window?
Are they showing as faulty or with missing dependencies in CM? (warnings do not show as "faulty")
 
They do appear in the selection menu, they don't show any faults, I also noticed that their 3d models don't show up in "my collection"
 
In CM select one of the items of rolling stock or locos that has this problem. Right mouse click on the asset and select "List Dependencies". Does the list show any items in red which are faulty or have missing dependencies?

I have just noticed (and reported) what may be a problem with TRS22 Content Manager build 116492 in regard to showing assets that have dependency assets that are faulty. Which Trainz build are you using? This problem does not seem to occur in build 114800.

(clutching at straws here)
 
You may want to post some specific KUIDs that are having trouble, so they can be tested by others. Also, you should not have to update the build number for assets. TRS19 is full of version 1.3 assets. I have 1.3 assets like these:
<kuid:56063:150887> 3BayWoodChipHopperUnionPacific18277Empty
<kuid:56063:150892> 3BayWoodChipHopperUnionPacific18278
<kuid:-10:195> 3dtcar
<kuid:-25:211> 50ft 2door boxcar
<kuid:56063:100133> 50ft Boxcar MILWAUKEE 4242
<kuid:56063:100159> 50ft Reefer Great Northern 8888

And version 1.3 locos like these:
<kuid:-10:180> 6e1 (Installed from DLS)
<kuid:44700:9205> 30 PBR G42 Boiler Unit
<kuid:45588:583> 44T Chesapeake Harbor Belt 9
<kuid:-10:181> alco
 
Last edited:
These assets are from the DLS, they all have the same problem.
<kuid2:405066:116:1> BDW Lehigh Valley F7A #561
<kuid2:405066:117:1> BDW Lehigh Valley F7B #561
<kuid2:405066:118:1> BDW Lehigh Valley FA1 #547
<kuid2:405066:119:1> BDW Lehigh Valley SW7 #222
<kuid2:568725:1013:1> GP7 Rock Island 1267
<kuid:327871:100055> Rock Island 2-8-2
<kuid2:327871:100053:1> Rock Island 2-8-2 tender
<kuid2:344263:100138:1> Pere Marquette 1225 Berkshire
<kuid2:262137:20690:1> Pere Marquette 1225 Tender
 
In CM select one of the items of rolling stock or locos that has this problem. Right mouse click on the asset and select "List Dependencies". Does the list show any items in red which are faulty or have missing dependencies?

I have just noticed (and reported) what may be a problem with TRS22 Content Manager build 116492 in regard to showing assets that have dependency assets that are faulty. Which Trainz build are you using? This problem does not seem to occur in build 114800.

(clutching at straws here)
none of the dependencies are red, none of the decencies showed as missing, all the affected assets showed zero errors.
 
These assets are from the DLS, they all have the same problem.
<kuid2:405066:116:1> BDW Lehigh Valley F7A #561
<kuid2:405066:117:1> BDW Lehigh Valley F7B #561
<kuid2:405066:118:1> BDW Lehigh Valley FA1 #547
<kuid2:405066:119:1> BDW Lehigh Valley SW7 #222

I have just installed all of the above in Trainz Plus (114800) and TRS22 (116492). All loaded without any errors or warnings. All show in Content Asset Preview with their wheels and all can be placed onto track in Surveyor.

The only thing that I can suggest at this stage is to perform a database repair.
 
I checked the F7A and the Pere Marquette in the same versions and they looked OK. The Pere Marquette had lots of warnings for both the loco asset and dependencies. I tested it in game (TS19) and it worked although the cab view was rather weird because the default cab view was above the loco.

I've seen assets that are invisible in game due to no default mesh but this doesn't seem to be the case here. If a DB rebuild doesn't work then maybe a delete of those assets and a download again?
 
The database repair didn't resolve the problem, reinstalling assets didn't work either. I did a test and found that anything newly installed will loose it's wheels, even though there aren't any errors.

This problem is affecting my custom assets as well, here's a link with two pictures I took, to compare an older custom asset with a newer one. https://imgur.com/a/NKJI3T0
 
Last edited:
Back
Top