Airedale route missing items

The problem in TS10 is the incorrect errorchecking in ContentManager. For the trackoffsets entry exactly 2 values are required by CM 3.3 instead or an unlimited list of values. This behavior is defined in the file <InstallFolder>\bin\TETData\kind.txt .
Here is a comparison of the definition for a bridge in CM 3.3 (green) compared to CM 3.7 (red):
Code:
bridge
{
   top-level 1
   icon bridge
   inherit
   {
        itrack
    base-asset
   }
   kind "Structure"
   subpossibilities
   {
        kind
        {
            kind value
            type string
            compulsory [COLOR=#00ff00]1[/COLOR]            [COLOR=#ff0000]3.4[/COLOR]
            default "bridge"
            filter "bridge"
            disabled 1
        }
        bridgetrack
        {
            kind value
            type kuidbrowser
            filter "bridge"
            compulsory [COLOR=#00ff00]1[/COLOR]            [COLOR=#ff0000]3.4[/COLOR]
            default <KUID:-3:10049>
            category "TK|SPLN"
        }
        height
        {
            kind value
            type float
            compulsory [COLOR=#00ff00]1[/COLOR]            [COLOR=#ff0000]3.4[/COLOR]
            default -8
        }        
        trackoffsets
        {
            kind value
            type [COLOR=#00ff00]vector2[/COLOR]            [COLOR=#ff0000]floatlist[/COLOR]
            compulsory [COLOR=#00ff00]1[/COLOR]            [COLOR=#ff0000]3.4[/COLOR]
            default -2.5,2.5
        }
        trackdirections
        {
            kind value
            type[COLOR=#00ff00] vector2[/COLOR]            [COLOR=#ff0000]floatlist[/COLOR]
            compulsory [COLOR=#00ff00]1[/COLOR]            3.4
            default 1,1
        }
    }
}
vector2 = exactly 2 values
floatlist = comma separated list of 1 ore more values

compulsory 1 = required (for trainz-build 2.9 or higher)
compulsory 3.4 = required for trainz-build 3.4 or higher

Peter
 
Last edited:
I can't pretend to understand all that programmer's poetry. My apologies for this because it's hard to view it all on an iPhone screen.

Are you saying the asset has been built incorrectly for the trainz-build number it has been given (2.9) or that TS2010 has a bug in its error checking such that it incorrectly says the asset is faulty?
 
He's saying that TS2010 has a bug in it's error checking, although I had the same problems as you in TS2009, so I think it was built incorrectly for the build number 3.3 (Content Manager), which imposes exactly 2 values. Whereas other versions of Content Manager allow a list of as many entries as are required (except possibly 2.9, which would mean it is an incorrect build for the version). I followed his advice to swap the Initiator and Terminator *.im filenames in the mesh table, so Initiator becomes the end*.im and the terminator becomes the start*.im, to solve missing pier ends, and changed the build to 2.8, and this allows the full 4 entries in track offsets (-6,-2,2,6) and just 1 entry (0) in track directions.

This seems to have fixed it in TS2009, let me know if it works in TS2010, if you would be so kind. As both are 3.3, I think it should. Otherwise, changing the bridge to another would seem to be your only option. Had I known, I would have used a different bridge from the beginning. Don't you just love it when "improvements" bugger things up!
 
Last edited:
OK, that I understand. Thanks Ken. If the bridges, as downloaded, are treated as faulty by TS2010/CM3.3, personally I don't see much point in keeping them alive on my system by "artificial resuscitation", i.e. by a local, private fix.
 
I understand your point, however, once fixed it isn't a bad piece of kit. As I said, I would have used a different bridge had I known at the time.

Hindsight would be a wonderful gift.
 
An after-thought: has anyone bothered to contact the author of the Friargate bridges (Kemplen) and tell him about the problems with his latest build-2.9 versions? It could be that he (or maybe someone else under that joke called the 'DLS repair program') has issued them without actually checking them in all appropriate versions of the game.
 
The problem isn't the bridge, it's the error checking of some version of the ContentManager, forceing limits which don't exist. You could fix this behavior by editing the file kind.txt (make a backup) and change vector2 to floatlist at the locations marked in the posting above. The same changes could be needed for some other kinds (like tunnels).

Peter
 
Back
Top