Problem with terrain height

[bwfeldsee]

I've built a couple of routes and am fairly certain that the datum mark for zero height when I started the first board was 0.00 (the same as the built-in routes that come with Trainz).

Each route is about 20 miles in length. I finished them, designed some sessions and so on and had a good play. At that stage I bought a new computwer and reinstalled Trainz plus my routes - all still OK and sessions running well.

Then I decided to extend one of my routes and found to my horror that zero height is now shown as 100.00. So, when I added a new board and clicked on "get height" it gave me 100.00. If I then clicked on "apply height" I then got a mountain.

Please can some kind person explain what has happened and how I get out of it. The built-in routes are still showing 0.00 correctly - the error only applies to the two routes I built.

Thanks in anticipation.

Alan

 

[sniper297]

Open the route for edit in explorer, check the config.txt - look for a datablock something like;

world-origin
{
latitude 42,28,1
longitude 88,2.00043,-1
altitude 100
}

If it's there, change the 100 to 0, see if that fixes it. If it's not there, try adding one with the altitude set to 0.

 

[bwfeldsee]

Perfect. Thanks, Sniper. I'd brought that little problem on through my own fault. Quite late on whilst writing the sessions I had added a trig station to fix the latitude and longitude so daylight would come and go more accurately. During this process the altitude got changed on both routes. All is well again now!

Alan

 

[sniper297]

Yeah, I actually did it on purpose for the first Chicago Metro, setting it at a location I knew to be 640 feet MSL thinking I might want the correct altitude for some reason. After that everything was kinda all over the place, some tools used the ground as a base zero, others used sea level, rather than trying to figure out which used what or when and when not to compensate, I just reset to zero and motored on.

 

[Dralex]

I had the same problem recently. When I used 'get height' I got an unreasonably high value. When I use that value to use the height I also got a mountain. I wanted to reproduce this problem with a new route, and it didn't show. Then it hit me that the route I am working on has a world origin, but the fresh one has none. So I checked the world origin and found that I had set the height value to the height at the location where I placed it. So my height values were way off; get height gave wrong values but get vertex height (from the track tools, F4) gave me the correct value. Problem solved by setting the height of the world origin to zero, which updates the world origin value in the config.txt. (As Dermmy told me, every route has a world origin, which defaults to the values of the region, with a height of zero.)
So: Don't mess with the height of the world origin (except making sure that it is set to 0)!

Dralex