Train-Sim.Com
MSTS Route Design

Track database rebuild failure

Notice to all visitors and members of the Train-Sim.Com message forums:
If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.

Previous Topic | Next Topic

Printer-friendly copy Email this topic to a friend

Reading Topic #11932

Member since Jun-9-03 · 36 posts

The RF&P track database won't rebuild even on the backup that I saved to CD a month ago. At that point, I thought I had all the track laid and did a successful rebuild and saved it to CD. Then I realized I had left out some terminal tracks, so I added those (just a few straight tracks and bumpers) and the rebuild failed. So I copied the backup files off the CD and tried the rebuild and it failed this time too, with the very files that had worked before the backup.So I went around clicking on all the recent trackage and found some pieces that will cause the Route Editor to crash if I try to select them. I scoured the forum for answers and tried everything (I think): editing the world files, using the skip command, deleting the track database and then using the Route Editor to delete the sections as objects. I even tried deleting one world file and its associated tiles that contained nothing but a few track sections (and depopulating that tile in the Route Geometry Extractor). All of these methods got rid of the track but not the vectors, and because the rebuild still fails, the vectors won't go away and the questionable track can't be replaced.So I restored the backup from the CD again (the database still won't rebuild) and drove a train over every piece of track that had caused trouble in Route Editor, expecting the program to crash at any moment. But it drove over all the track with no problems!So my question is this: Is there something I haven't tried that would lead to a successful track database rebuild? If not, dare I finish the scenery, add signals and mileposts and car spawners, and call it finished? Or is something likely to go fatally wrong when I start adding green pyramid things to the track?Or should I stop deleting all the spam that is offering to sell me drugs? I'm ready to join train simulators anonymous.Thanks for any ideas anybody has.Steve Dunham

Steve Dunham
Spotsylvania, VA
Literalman@aol.com
www.stevedunham.50megs.com

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 4968 posts

RE: track database rebuild failure

LAST EDITED ON May-15-04 AT 07:04 PM (EDT)

There is no simple answer to your problem, other than saying that when building Routes, frequent back-ups must be taken every time a TDB Re-build works and you can go back into the Route in the RE without getting "Send, do not send..." ! Sounds like you gone too far getting yourself into a muddle, which would be more difficult so sort than starting again ?O t t o

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Member since Jun-9-03 · 36 posts

RE: track database rebuild failure

Into a muddle, yes. I'd been doing rebuilds often ever since I learned about them, which was sometime last year. And I deleted the backup files of the track database and so on before attempting the rebuild. I should have mentioned that.

Steve Dunham
Spotsylvania, VA
Literalman@aol.com
www.stevedunham.50megs.com

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 4968 posts

RE: track database rebuild failure

Steve,what I do before doing a Route Re-Build is I take copies of the TDB and RDB before Deleting the originals, which is a requirement prior to doing a Re-Build. If something goes wrong with the Re-build I have at least the backed-up copies of them to try and sort things out, before resorting to other back-ups.But as I also take frequent Back-Ups of the Route during it's development stages, sometimes every hour, depending on how much work I have done, there is always a fall-back to a good version. The more often this is done, the less work will have to re-done, rolling back the Route.O t t o

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 897 posts

RE: track database rebuild failure

First, make sure that the files off the CD are not read only. They will be unless you have changed the properties (or they came out of a zip file stored on the CD.David Beach.Palouse & LewistonTrack database rebuild failure – image 1


Standardized \global\tsection.dat file now at build00023.

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Member since Jun-9-03 · 36 posts

RE: track database rebuild failure

Thanks. I still have the supposedly good tdb on the CD. When copying the files back onto the hard drive, I changed the properties of the tdb and other files in the main route folder (but not world, shapes, tiles, etc.) so they were no longer read only. Maybe I should try it with the properties changed on all the files.If I had it to do over, I would have made interim backups. But everything went pretty smoothly (in terms of tdb rebuild, anyway) for over a year, until a few months ago. I was using one rewritable CD for backup. Maybe once a week, I would do a track database rebuild, drive trains over the new sections, and then back up the latest version.If I ever do another route, I will make and keep interim versions. But maybe someone will mercifully tie me to the tracks first.

Steve Dunham
Spotsylvania, VA
Literalman@aol.com
www.stevedunham.50megs.com

Alert | IP


[ Home | MSTS Forum | MSTS FAQ | File Library ] Copyright © 2004 by Nels Anderson. All Rights Reserved.

Restored from the Train-Sim.Com archive, captured June 17, 2004. About this archive.