Help!

[landnrailroader]

In some way, a section of track became corrupted, unknown to me, in my Kingsport sub. and when I happened across it, there was about 300 meters of track where the database lines showed, but the track objects were missing. I had no problem removing the orphan database lines, and from a backup of a few weeks ago, I can make notes & reconstruct the junction which is just a #15 left turnout. But then to my horror, I found that the node number of the turnout was still showing and I have had no luck removing it with any "hack". Anybody have an idea. If I have to go back to the last good copy, I will then have to reconstruct about 30 miles of branches - not impossible, but I would rather get rid of this issue.

Jerry SERIOUS_ERROR.jpg

[landnrailroader]

Well, I just took the Bull by the horns and didn't seem to get gored. I copied the track database to my location where I save potential issues. Then I went in by Conedit and located the 1609 node. Carefully deleted it and changed the number of nodes at the top of the file to one less. Then the route seems to have opened correctly and I knew that I needed a M2 five meter piece before the #15 left points. Added that, the points, and the frog part and so far the bad node is gone and everything seems to be good. So now, I would appreciate any comments, good or bad, and I plan to check my good backup and see what pieces I need to complete the junction. The junction in question is where NS can come and go from CSX just north of Frisco, TN to exercise their trackage rights, or CSX can use the junction if detours are needed for some reason over NS.

Jerry

[kapitaen]

Actually, you don't need to correct the TrackNode counter. Remove the orphaned trackNode from the .tdb file and save it with a text editor. Then open the route in tsre with the option `loadAllWFiles = true` and save it immediately. If you now go back to the .tdb file in the text editor, it should have been rewritten. The trackNode counter should be updated, and the interrupted numbering should be restored all the way to the end.
Jan

[landnrailroader]

Thanks Jan. I have a few others like that and I had wondered how to deal with them. I have load all w files set because Having essentially finished the track, I am getting rid of the pieces that escaped deep down. Only issue with that, and it is not a problem, is that when you select an item with the error tool, and then try to delete it, it doesn't work, but if you select with the mouse it does, so?. What is interesting is if you have a small item real deep you can't see it until you use the tool to raise it up.

Jerry

[landnrailroader]

Well I got the corrupted section fixed and then I looked at other warnings and errors. There were a number of signal, soundregion and similar items which were all on world files that I had copied over from the original Kingsport route. In most cases I was able to edit the world files and eliminate the errors but in one case the world file is still compressed. I have not seen a compressed world file in a long time and I ass/u/med that TSRE decompressed but in this one case it did not. So do we have a tool now that will work on Win-11 and decompress a compressed ascii file? For newbies that see this, just back up your world file before editing it, and then sound regions are found on the .ws file with the same name as the .w file.

Jerry

[landnrailroader]

These are the last two errors. The speedpost item is apparently in the compressed world file, so until I can find something to decompress it, well ? The other is a mtrack #15 point and here is the biggy. I can select it, I can move it, I can jump to it, but if I hit delete to get rid of it, TSRE crashes to desktop. I wonder if it can be deleted from the world file it is in by a text editor, and then remove the missing node from the track database? In any case neither of these items seems to cause a problem if they are left as-is.

Jerry ERROR_LAST2.jpg

[slipperman]

Hi Jerry,
You can use my FFEDIT_Sub (file ID 87969) to uncompress/compress World Files.

Cheers,
Ged

[pwillard]

Not mentioned is the nice option of Slipperman's tool: it can handle folders all at once, not just one file at a time.

[slipperman]

Not mentioned is the nice option of Slipperman's tool: it can handle folders all at once, not just one file at a time.

Many thanks for the extra 'plug' ,Pete

Cheers,
Ged