Friends,
I have a up to date copy of a route I am working on, safely backed up on a DVD so now I want to add another
60 miles of track to this route (Great Falls, MT to Agawam, MT).
I read where you can put an entry into the startup file of TSRE that will keep new track pieces from making a
database entry until one hits the "Z" key. Okay, what is the entry to make?
I have found that new track pieces will not lock into place on a previous piece unless that piece is in the
database. Is there a way around that, because I would like to lay a few hundred meters, like around a curve
and then adjust the entrance & exit to that curve to fit makers.
Lastly, [cntrl]Q turns off or on the entry process, and I find that "z" either turns on the yellow database line
or turns it off? How can you know if the parameter is set to enter the database, or not?
As information, I gave up trying to get MSTS to work on my upgraded machine and plan further new routes
or modifications to be done in TSRE.
J. H. Sullivan
I have a up to date copy of a route I am working on, safely backed up on a DVD so now I want to add another
60 miles of track to this route (Great Falls, MT to Agawam, MT).
I read where you can put an entry into the startup file of TSRE that will keep new track pieces from making a
database entry until one hits the "Z" key. Okay, what is the entry to make?
I have found that new track pieces will not lock into place on a previous piece unless that piece is in the
database. Is there a way around that, because I would like to lay a few hundred meters, like around a curve
and then adjust the entrance & exit to that curve to fit makers.
Lastly, [cntrl]Q turns off or on the entry process, and I find that "z" either turns on the yellow database line
or turns it off? How can you know if the parameter is set to enter the database, or not?
As information, I gave up trying to get MSTS to work on my upgraded machine and plan further new routes
or modifications to be done in TSRE.
J. H. Sullivan






Comment