Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Alrighty, now that I know what to do (buy both LoBN's from JR), I now want to know how I can get the JR version on my computer and get rid of the DLC version. How could I do this?
Didn't you happen to have a route up on your website that had half a dozen PAYWARE routes merged into it?
... Well, I just bought the LoBN 1 and 2, so PNW Route, here we come!
They merge really nicely. I put my connector between Eagle River and the LoBN 1 and 2 just about the middle of the LoBN2 near where the power plant branch is located but on the opposite side. There's that dead end spur that goes off into the woods there on the right and I took that and made that the line to the Eagle River. It took a bit of landscaping there, but it blends in nicely. I then continue the BN mainline up-grade out of the yard and on to the LoBN 1.
I did change the names of the towns a bit so that there's no duplicates and then setup some operating sessions. I do the manual freight and passenger drives and let the AI do the rest. My operation can last for hours, or until I decide to quit with little if any interruptions to wake up AI or untangle them. Because of the route's length, I can run prototypical length freights and they look great winding their way through the landscape.
I have my routes set up with the LoBN 1 and 2 connected at the Vernon area, where a little branch line meets the mainline. Built a wye to facilitate easy transfer of traffic to and from the Vernon area. The Eagle River route has had a bit of trouble merging (it takes forever and never gets anywhere, but I wanted to merge it from the power plant area or the dead-end spur on LoBN 2 like you said. I may try and merge another route in, like Tidewater, to serve as something like a coastal intermodal terminal in Oregon or Washington. I changed all the track to the TSM track on the DLS (it really beats the JR track on the older portions of the route), and did a run-thru before I attempted to merge in Eagle River just in case I missed any track.
For Eagle River, what's keeping it from merging in a timely fashion? LoBN 1 merged in just fine, under a minute might I add, and its much bigger. I'm getting no errors either.
If there was a way to lower the route easily, then it would be a nice addition ...
I will second that. My current project was started back in TS2004, before the existence of TransDEM and Google Earth, so I guessed the elevation and, as it later turned out, I was out by 483m. It was easier to maintain the error as I expanded the route than to go back and correct it. This continues today with further expansions and updates. Another user is building an extension to be merged with the route and has to adjust all the elevations by subtracting 483m from the actual elevations.
TransDEM can raise and lower the elevation of pre-TANE routes.
The changes to the file system introduced with TANE have broken this function but it still works for older routes as long as you change the height BEFORE making any edits in Surveyor in a newer version of the game.
TransDEM can raise and lower the elevation of pre-TANE routes.
The changes to the file system introduced with TANE have broken this function but it still works for older routes as long as you change the height BEFORE making any edits in Surveyor in a newer version of the game.
It would be nice if the ability to adjust route heights and direction too was available to us in Surveyor. The only way we can do that is to copy areas and paste them on new baseboards set to an adjusted height. The issue I see is lining things up and computer resources from copying and pasting all that data.