Elvas Tower: Serious TDB inconsistency created by TSRE - Elvas Tower

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Serious TDB inconsistency created by TSRE

#1 User is offline   roeter 

  • Vice President
  • Group: Status: Elite Member
  • Posts: 2,106
  • Joined: 25-October 11
  • Gender:Male
  • Country:

Posted 08 September 2017 - 08:32 AM

A serious inconsistency in the tdb data is created by TSRE when a section of track is removed while signals are placed on that section.

If a section of track is removed while a signal (marker) is still placed on that section, the SignalItem entries for those signals are cleared (substituted by an EmptyItem), but the references in the world file for these signals is left unchanged.
Therefor there is then an inconsistency between the world files and the tdb because there is a signal entry with a reference to a tdb entry which no longer exists.
But that's only the start of things.
Suppose the user hasn't noticed this (there is no warning or whatever), continues to edit and places new signals. These new signals will now use those tdb entries which were cleared earlier - so there now are different signals, perhaps in different world files, referring to the same tdb entry.
Clearly, one set of these signals - those on the section of track which was removed at the start of things - are now 'dead', and sooner or later the user will notice this. The user will then go back to the editor, select the signals and remove them. But in doing so, TSRE will clear the referenced tdb entries - but these are now used by other signals, so these other signal now loose their tdb entries and these are now 'dead'.
It is clear that this problem can spread like wildfire through the .tdb, and the user could end up having to replace dozens of signals before it is rooted out.

It is possible similar problems may occur when removing sections of track which still have other items with tdb entries linked to them, e.g. level crossings or speedposts, but I have not tested this.

Something should be done to prevent this rather serious problem, either blocking the removal of a track section which still has tdb-related items linked to it, or these items must also be removed when the track is removed.

Regards,
Rob Roeterdink

#2 User is offline   Goku 

  • Superintendant
  • Group: Status: Elite Member
  • Posts: 1,734
  • Joined: 12-December 13
  • Gender:Male
  • Simulator:my own
  • Country:

Posted 08 September 2017 - 10:06 AM

Quote

Something should be done to prevent this rather serious problem, either blocking the removal of a track section which still has tdb-related items linked to it, or these items must also be removed when the track is removed.

Now you can enable "track items" in view menu, so you can see if track has any track items before removing it.
Better solution will be done in the future.

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users