Track Database Errors, more complex?

Ok, i'm familiar with the track database error, the typical one you get when track has become mis-aligned or something. That's the error message that says "adjacent track piece not loaded. Can't select track piece"However, in the past to solve this, i've run it through the route editor and used the re-build track database option which has fixed this error in the past, however now whenever i try and run it through and re-build the database i get an error which says;
"Track database error: 'remove_end_end one non-vector, one vector." This of course then crashed the route editor, which doesn't complete the track database re-build.I even think i've found the offending piece of track, but i can't remove it manually as everytime i click on it it says "adjacent track piece not loaded. Can't select track piece"Does anyone know what's going on and how to fix it?Thanks,
James.

"Well, you know boys, a nuclear reactor is a lot like a women. You just have to read the manual and press the right buttons." Homer Simpson

Alert | IP

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

RE: Track Database Errors, more complex?, calr, Jan-05-04, 11:09 AM, (1) RE: Track Database Errors, more complex?, driver89, Jan-05-04, 11:23 AM, (2) RE: Track Database Errors, more complex?, lenglel, Jan-05-04, 12:05 PM, (3) RE: Track Database Errors, more complex?, Coonskin, Jan-05-04, 12:54 PM, (4) RE: Track Database Errors, more complex?, DRGWK36, Jan-05-04, 07:01 PM, (7) RE: Track Database Errors, more complex?, MRRextreme, Jan-05-04, 01:54 PM, (5) RE: Track Database Errors, more complex?, enocell, Jan-05-04, 02:42 PM, (6) RE: Track Database Errors, more complex?, lirc201, Jan-05-04, 07:12 PM, (8) RE: Track Database Errors, more complex?, Coonskin, Jan-05-04, 08:43 PM, (9) RE: Track Database Errors, more complex?, driver89, Jan-06-04, 00:20 AM, (10)

Conferences | Topics | Previous Topic | Next Topic

Try to select and remove the track sections on both ends of the bad section. Save and exit RE. Go back in and see if you can select the bad section. If you can, delete it, save, and exit. If you can't, exit and do a TDB rebuild. Go back into RE and see if you can remove the bad section (if it is still there). Save, and exit RE. Now go back in and replace all removed sections.Cal Rasmussen
Beaverton, OR
(My email is in my profile)Columbia Gorge Route (Phase 1-- Finished, Preparing Beta Test)

Alert | IP

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

Hi Cal,
Thanks for the quick response, but i tried that too, but it didn't work. Now i have a section of about 1200m of track with nothing on either end, and i can't delete it. This one's really got me stumped, it's like this track just doesn't want to leave.James.

"Well, you know boys, a nuclear reactor is a lot like a women. You just have to read the manual and press the right buttons." Homer Simpson

Alert | IP

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

Sounds like you may need to edit the affected .w
file in wordpad to remove the offending pieces.
Luckily, RE gives the coordinates of the current
world tile as it's doing the rebuild, so you can
figure out the file name when it stops.
Lloyd

Alert | IP

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

Been there. Done that. Go here:http://www.train-sim.com/dcforum/DCForumID6/11164.htmlAndre Ming
THE Big Cheese and Great Poobah of V Scale CreationsVisit V Scale Creations Forum at: http://www.3DTrains.com

Alert | IP

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

>Been there. Done that. Ah, but did you get the T-shirt? Andy

Alert | IP

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

1)Open the route editor for the route and go to the desired track piece that is a problem.2)Place a random object like a tree near the offending track piece so that the world file ".w" gets updated.3)Note the "X" and "Y" location of the camera on the object tile, not latitude and longitude. 4)Close the route editor.5)Open the world file that has been most recently updated.6)Seach for the track object with the closest "X" and "Y" values noted in the route editor.7)Type the following before the track object: Skip(8)Type the following after the track object: )9)Close the world file.10)Return to the route editor and the track object should be gone11)Delete the random object used for place marking.12)Regenerate the track database, if desired. I prefer using the "Skip" command since that allows the original information in the file to be preserved.

Alert | IP

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

Changing the start tile may help as well (or it may do things worse, if possible). On the NJC route, this made things worse and TDB rebuild didn't work during ~3 final months. But with Buffalo route, the first tile worked until I added one piece to a certain tile. Then it started to crash (just a single piece caused that, no matter if it was connected or not), so I started to find another start tile. For some reason(?) the 3rd tile I tested was a working one and I change the start tile back to it every time I want to rebuild the tdb (I do that after every major track change, just to be sure).

Alert | IP

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

I have encountered 2 different errors when working on my route. The blue pole and the "Track database error: 'remove_end_end one non-vector, one vector." After searching the forums and reading posts I found some information that was really really useful. The route editor does not like certain track sections crossing tile boundaries.First off read the link posted by Coonskin, it contains some very important steps.You will most likely have problems with A1-250m straight, and A1-500m straight sections.If you get the "Track database error: 'remove_end_end one non-vector, one vector" error make sure to write down the Latitude, and Longitude. Then go back into RE and check to see if the error is on a piece of track that crosses a tile boundary. Delete the track pieces around the bad section and then do a "Trackdatabase Rebuild."Once the "track rebuild" finishes go back into RE, delete the track section that was causing problems, save and exit RE. Make a backup. Go back into RE and replace the track sections. What I have found that fixes the problem is to place a A1-100m (50s work as well) straight section across the tile boundary. When placing the 100m track across the tile boundary make sure to include at least 25-30m on each side of the boundary. RE seems to be sensitive if enough of the track is not over the tile boundary.This method has worked for me on both blue poles and the "Track database error: 'remove_end_end one non-vector, one vector."

Brian LaVelle
Cincinnati Terminal Route
http://belcommunications.net/msts

Alert | IP

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

Apparently, RE is somewhat sensitive to various things... and if all interact with one another in a precise convergence, then it will produce a quantum flux in the outer nebulous zone. From the FWIW department...There are two kinds of route builders:1. Those that have had tdb errors.2. Those that are going to.Andre Ming
THE Big Cheese and Great Poobah of V Scale CreationsVisit V Scale Creations Forum at: http://www.3DTrains.com

Alert | IP

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

Thanks all for the help, and indeed i got it solved, though not without some effort. Brian's suggestion of marking down the tile where the error occured was the right one. Sadly his post showed up shortly after i'd found this out, but thanks anyway. What had been throwing me was that the non-vector error was happening almost on the other side of the route to the area where i was working. So anyway after ripping up the track and relaying it I was able to rebuild the database. Thanks to everyone. James.

"Well, you know boys, a nuclear reactor is a lot like a women. You just have to read the manual and press the right buttons." Homer Simpson

Alert | IP

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