A crash reading the TDB

[lindsayts]

I am getting a crash in OR at a particular point in a the Adelaide Hills and SE route, the error message is...........

runactivity.exe : Error : 0 : System.IO.InvalidDataException: TDB Error, could not find junction. (tileX = 929, tileZ = 10294, UiD = 183)
at MSTS.TDBFile.GetTrJunctionNode(Int32 tileX, Int32 tileZ, Int32 UiD)
at ORTS.WorldFile..ctor(Viewer3D viewer, Int32 tileX, Int32 tileZ)
at ORTS.SceneryDrawer.LoadAt(Int32 tileX, Int32 tileZ)
at ORTS.SceneryDrawer.Load(RenderProcess renderProcess)
at ORTS.Viewer3D.Load(RenderProcess renderProcess)
at ORTS.LoaderProcess.Update()
at ORTS.LoaderProcess.LoadLoop()

If one looks in the requested world file for the Uid One finds this......

TrackObj (
UiD ( 183 )
SectionIdx ( 38052 )
Elevation ( 0 )
JNodePosn ( 929 10294 205.729 101 -881.385 )
CollideFlags ( 583 )
FileName ( A1tPnt6dBLftMnl.s )
StaticFlags ( 00200180 )
Position ( 205.729 101 -881.385 )
QDirection ( 0 0.0188257 0 0.999823 )
VDbId ( 4294967294 )
StaticDetailLevel ( 0 )
)


The file A1tPnt6dBLftMnl.s and its sd file does exist in the GLOBAL directory although the shape file is compressed

This is the entry in the TDB file......

TrackNode ( 38
TrJunctionNode ( 0 38052 1 )
UiD ( 861 10351 29 0 861 10351 -1018.45 101 57.9238 0 2.31726 0 )
TrPins ( 1 2
TrPin ( 1044 0 )
TrPin ( 28 1 )
TrPin ( 39 1 )
)
)

Anyone know what the problem is as everything appears to be there and how I can solve it, MSTS by the way works OK.
By the way the crash occurs something like 2 and half hours into the activity.

A minor comment..... god its good having all the data in text files when one can find it with some decent search tools.

Lindsay

[kraus]

The entry in the track database, junction node 38, is for a track object in world file 861 10351 with UiD of 29 and not that requested by the error message. My copy of the route does not have the requested world file or that junction in the track database.

In Route Editor go to world file 929 10294 and then the coordinates of the requested junction. You should find a track piece without the overhead track database lines. This indicates a mismatch between the world file and the track database. This mismatch can be resolved by selecting the track section and adding it to the database or deleting the track section from the world file. This issue also occured with the London and South East route described in post http://forums.makingtracks-online.co...hp?f=12&t=3988

[lindsayts]

Thank you for the reply, hmmmmmmmmmmmmmm

The tile 0929 10294 does not exist in the TDB at all, a search for the position comes up with the correct section index on tile 865 10358. This is the only individual refernce to this position apart from the following TrVectorSections.

My copy of the route is an update from version 1, the update must be a bit corrupted. Alan having done a massive amount of work between V1 and 2, the patch can not have removed all unrequired items. I am currently downloading the stand alone install and will give that a try.

Many thanks,

Lindsay

[lindsayts]

Removing the route and installing the stand alone version fixed the problem. I have called this a crash of OR I do not believe this is correct, a crash being the operating system kicking out a missbehaving program. This was OR exiting because there was no way for it to handle the situation it found itself in. OR correctly displaying an error message before exiting.

Lindsay