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.
It's been quite a stretch since I've been(posted) here. I've been trying to fix up the trackwork on my PORT Road segment of the PRR but I keep getting errors with the tdb.
I'm pretty much convinced the problem actually lies with the tsection.dat file.
I can not get a complete tdb rebuild. I always end up with several pieces of dynamic track that are screwed up or never loaded into the tdb. So I begin to manually go through the route, replacing the dynamic track. I regularly make copies of the tdb as I correct each problem. I also regularly check the activity editor as it will show whether I have been able to fix the broken paths as I replace the dynamic track. This goes fine for a while and I've actually gotten to within one piece of track when everything goes haywire. The activity editor shows that several pieces of dynamic track have lost their connection. If I go back into the route editor I get " adjacent track pieces not loaded, can't select this track" error message, when I try to repair these glitches that have popped back up.So I try replacing the tdb with one of the copies I've made and it shows the same break points in the path when I open up the activity editor again. It does not matter which of the tdb copies I open, I get the same thing. I've stored the tdb copies in different folders, given them different names and still get corrupted tdb. It looks fine in the route editor, but if you try to create an activity you find out very certainly that there is a problem when you run the sim.All of this leads me to conclude that it is actually the tsection. dat file that is blowing up.Anybody have or suggest a possible solution to this? Thanks for any help you might offer.Bill aka Pennsyfan2
Bill,this is a pesky problem I tripped over many times myself, especially when trying to modify the N.&.J.C. which has several TDB Rebuild problems.There have been many discussions on the subject, none offering a simple workable solution ! Will be interesting to see what the response is going to be this time ! O t t o
It is extermely unlikely that your tsection.dat file is faulty unless you have been tinkering with it. Questions is though which tsection.dat is it you're talking about, there are two you know (damn Kuju naming them the same).First the one in the global folder is never changed by MSTS. Only if you change it or replace it when installing some track/road add-on is it changed. Have you done any of ths recently (within a month or two from when you first experienced your problems)?Second one is in your routes folder whatever name that has. This file is updated by MSTS when you add or change dynamic tracks and can become corrupted in some circumstances when you have changed the global tsection.dat. You should not make changes to this file as the entries are also used in the w-files in the routes world folder.You said that you went along and replaced dynamic track to fix tdb problems and then when you got the "send/don't send" you tried going back to an earlier tdb. If you have made dynamic track changes between that tdb build and the current state of your route they are out of sync. You would need to revert the whole route to get back to that stable state.If you don't have a complete backup your best bet is to continue working on getting that tdb re-build through. "adjacent track pieces not loaded, can't select this track" can be repaired. If you delete the track section next to it and do tdb rebuild you usually can select it. Another option is to go into the w-file and delete it but then you need to be pretty sure on it's location and you will still need to make a tdb rebuild. Main question though is why your problem started in the first place? What did you do to upset the dynamic tracks? I hope you did not start this route with the default MSTS installation then after a while added XTracks (or something like it) and continued building your route as if nothing had occured. Adding a track/road package to a MSTS installation that has had no such package before can make much damage to your routes being built.
OkrasaI've been strictly default installation from day one of loading MSTS I've not installed any routes requiring Xtracks or installed xtracks at any time. I have two other routes in my routes folder other than the defualts. They were both built using the standard default track package.I've not had any problems with either of those routes. The global tsection.dat file is the one loaded at install of MSTS. I've not messed with it in any way other than to open it and read to compare my route tsection in hopes of maybe finding a cause for my problem.The tdb only gets corrupted while working with dynamic tracks as I described in my original post.I'll keep working with it in hopes of finding a solution.Thanks for your input and things to consider.pennsyfan2
Your problem is most likely still in the .tdb file. I've had instances where I've had to go through 15 iterations to remove what started with a single "rogue blue pole" - that is, a blue pole indicating an end of track sitting right in the middle of a long run of supposedly connected track. Some people have seen worse problems with dynamic track, but my recent difficulties were with a route that has zero dynamic track in it, so it's a bug that doesn't discriminate. From my experience, about the only thing that will cure your ills is to repeatedly do a track database rebuild and repair what you find at the location where the rebuild locks up, until you can get completely through the rebuild without any send/don't send or lock-ups. In some cases, you may need to get into the other files (world, tile, etc.) and hack out a piece of track that's causing problems. Not much fun, and a brute-force approach, but it eventually works.Andy
