Bridge brick 2t Brick error faulty

[Darksteel350]

Im having trouble with this assest it keeps saying this error, the tag 'unit_mesh' is not permitted within a container of type 'bridge ', and I dont know how to fix it, if anyone does please let me know.

 

[pware]

I can see 4 versions of "Bridge 2t Bridge" - 2 are "Packaged" and 2 are "Available for download, Obsolete". All 4 are by Auran and all are Trainz build 1.3 which makes them very old assets. None of them are reporting errors.

<kuid:-25:23> Bridge 2t Brick
<kuid:-1:101159> Bridge 2t Brick
<kuid:-25:272> Bridge 2t Brick
<kuid:-1:101206> Bridge 2t Brick

So unless you can identify the exact one (or another one if it is not listed above) then there is little anyone can do.

The message "unit_mesh is not permitted in a container of type 'bridge'" means that the config.txt file for that asset has been incorrectly edited or constructed.

The easiest solution may be to replace the bridge with a different one.

 

[Darksteel350]

I can see 4 versions of "Bridge 2t Bridge" - 2 are "Packaged" and 2 are "Available for download, Obsolete". All 4 are by Auran and all are Trainz build 1.3 which makes them very old assets. None of them are reporting errors.

<kuid:-25:23> Bridge 2t Brick
<kuid:-1:101159> Bridge 2t Brick
<kuid:-25:272> Bridge 2t Brick
<kuid:-1:101206> Bridge 2t Brick

So unless you can identify the exact one (or another one if it is not listed above) then there is little anyone can do.

The message "unit_mesh is not permitted in a container of type 'bridge'" means that the config.txt file for that asset has been incorrectly edited or constructed.

The easiest solution may be to replace the bridge with a different one.

<kuid:-1:101206> Bridge 2t Brick, this is the version im having the error with.

 

[pware]

<kuid:-1:101206> Bridge 2t Brick

This has been made obsolete by <kuid:-25:23> Bridge 2t Brick which is in the DLC package "East Coast Main Line - Dundee".

I just installed the obsolete <kuid:-1:101206> version and opened up its config.txt file for editing. It does contain an error which I have emphasized in bold, red, enlarged text in the copy below. That line should not be there - it may have been correct for the version of Trainz it was created for (but unlikely) but it certainly does not belong in more modern versions such as TRS19 and later.

trackoffsets -2,2
height -8
bridgetrack 100673
bendy 0
length 19.9
istrack 1
width 19
unit_mesh
kind "bridge"
region "Germany"
kuid 101206
type "Bridges"
username "Bridge_2t_Brick"
username-de "Brücke_2t_Ziegel"
username-pl "most_2tory_ceglany"
username-fr "pont_2v_briques"
username-nl "Bridge_2t_Brick"
username-cz "Most_2k_zděný"
username-es "Puente_2v_Ladrillo"
username-it "Ponte_2t_Mattone"
asset-filename "ger_brickbridge_double"
username-hu "Bridge_2t_Brick"
username-ru "Мост_2_пути_кирпичный"

kuid-table
{
0 <kuid:-1:100673>
}

The Solution:

1. In Content Manager right click on the asset <kuid:-1:101206> Bridge 2t Brick
2. Select the options Open then Edit Config File Text. This will load the config.txt file into your text editor
3. In the text editor highlight and delete the line containing "unit_mesh"
4. Save and exit the text editor
5. Back in Content Manager right click on the asset, which will now be shown as "Open for edit", and select Submit Edits

 

[Darksteel350]

This has been made obsolete by <kuid:-25:23> Bridge 2t Brick which is in the DLC package "East Coast Main Line - Dundee".

I just installed the obsolete <kuid:-1:101206> version and opened up its config.txt file for editing. It does contain an error which I have emphasized in bold, red, enlarged text in the copy below. That line should not be there - it may have been correct for the version of Trainz it was created for (but unlikely) but it certainly does not belong in more modern versions such as TRS19 and later.


The Solution:

1. In Content Manager right click on the asset <kuid:-1:101206> Bridge 2t Brick
2. Select the options Open then Edit Config File Text. This will load the config.txt file into your text editor
3. In the text editor highlight and delete the line containing "unit_mesh"
4. Save and exit the text editor
5. Back in Content Manager right click on the asset, which will now be shown as "Open for edit", and select Submit Edits

i did that, and im having no more errors, but it still says faulty, the warnigs are saying required tag 'trackdirections' was missing and has been set to default, and required 'thumbnails' is missing. what do i do now?

 

[Darksteel350]

i did that, and im having no more errors, but it still says faulty, the warnigs are saying required tag 'trackdirections' was missing and has been set to default, and required 'thumbnails' is missing. what do i do now?

nevermind i had to rebuild database

 

[pware]

Good to see that you have solved it. For future reference you can safely ignore Warning messages but these could become error messages in future versions.

Trainz in its very early days was extremely lax (or even sloppy) with its enforcement of the rules for building assets. Mistakes such as typing errors and incorrect "tags" in config.txt files (such as the "unit_mesh" in the bridge asset) would be ignored or at the minimum tolerated. As the graphics and features in Trainz improved these "errors" started to cause problems so the rules and their enforcement have been progressively tightened with each new release of Trainz.

 

[rwk]

Is that why assets that had warnings or even no warnings in older versions of Trainz but have errors in newer versions is because 12, TANE, 19, 22, etc. have more strict checking? Trainz 2010 had a compatibility mode that would allow older assets to work without errors but that feature was omitted from 12 and up. Some errors are easy to fix like deleting something from the config or using the pev tool to fix texture errors, if the textures are not encrypted, but some errors are difficult or impossible to fix like the incompatible speed trees and pofig trees in TANE and up.

 

[pware]

Is that why assets that had warnings or even no warnings in older versions of Trainz but have errors in newer versions is because 12, TANE, 19, 22, etc. have more strict checking?

Basically yes. That plus new features that were introduced in those versions required new config.txt settings and data formats that did not previously exist. Hence new assets are not be backwardly compatible with older Trainz versions and some older assets may struggle to work (or not work at all) in newer Trainz versions. The build number assigned to an asset tells Trainz which compliance tests to apply to the asset. For example, all assets with a build number of 5.1 will only work in Trainz+/TRS22 and later, build number 5.2 requires the SP1 version of Trainz+/TRS22 and later, 5.3 requires Trainz+/TRS22 SP2, etc.

The use of LOD (level of detail) data in assets provides an interesting case. This relatively recent addition is currently optional in assets but may eventually (one hopes) become mandatory in a future release. This will not mean that all old assets will have to have LOD added as the build number for those assets will probably be used to determine if LOD is required or not. LOD data significantly reduces the processing needed to display an asset in a scene particularly when a highly detailed (a high poly count) asset is further away from the camera point of view. The SpeedTrees replacement, Plant Factory which is currently in beta testing form, has LOD automatically built-in in the form of "imposters". These convert the 3D trees to flat 2D forms that always face the camera when the tree is at a set minimum distance from the camera and therefore takes up far less processing time.

Some errors are easy to fix .... but some errors are difficult or impossible to fix

Fixing some errors requires a detailed knowledge of scripting. Some can only be fixed by the original creator of the asset who has the Blender/3D Max files.

Errors in assets is, in part, the price that is paid when asset creation is open to all and not to just a select few "experts". Both have their advantages and disadvantages.

 

[rwk]

Ok, so we have a mess. We have assets that will only work in newer builds and old assets that refuse to work in newer builds. So I can't use that TRS19 and up only steam locomotive and older speed trees and pofig trees in the same Trainz version. A route that only works properly in 12 or TANE I can't use any 2019 and up only assets in it. Then you have sites that vanish, along with the downloads which results in a futile hunt for missing unknown kuids in routes which no longer exist on the web unless Wayback Archive has working links.

 

[pware]

That is all part of the fun and adventure of using Trainz.

My Prime Directive is never use assets that are not on the DLS or built-in. That way I never have to play the "Hunt the missing asset game" nor does anyone who installs one of my routes and sessions.

 

[pware]

The Freeware Announcement forum has threads that announce new freeware routes that are available on the DLS and occasionally elsewhere. While I decline to install any routes with external assets (and that is my view, others will have different and equally valid views) I do like those announcements that tell you which assets are not on the DLS and where you can find them but this does not eliminate the possibility, as @rwk mentioned above, of these external sources vanishing overnight.

I have only ever been caught out once when a DLS asset I included in a route vanished from the DLS. It turned out to be a copyright violation by the creator who modified and uploaded an asset from another creator without their permission. I had to scramble to find a replacement and then upload an updated version of the route.

A route that only works properly in 12 or TANE I can't use any 2019 and up only assets in it.

A route created in TANE has a very high chance of working perfectly in TRS19 and, once converted, can then use TRS19 assets. A route created in TRS19 will almost certainly work perfectly in TRS22 and can have TRS22 assets added. There might be the odd asset that cannot be "up-versioned" but you should have no problem in finding suitable replacements.

Going the other direction is more problematical. If you have TANE installed (maximum asset build number is 4.5 for TANE SP2/SP3) then Content Manager will reject installing any asset with a build number of 4.6 (TRS19) and above. One risky trick sometimes used is to edit the asset-build number in the config.txt file of the asset to a lower value but this means that Trainz will run different compliance tests on that asset and it most likely will fail, but sometimes you can get lucky. But what happens if you use that "down-versioned"asset in a route that you upload to the DLS? TANE users who install your route will not get the down-versioned copy, which is only installed on your computer, but will get from the DLS an asset that will be listed as "incompatible" or similar.