Track won't lay at proper grade since update!

autodctr

Active member
122411 Choosing a 1.7 gradient for laying track, doesn't work! The track simply lays on the current ground height. This is in Surveyor 1. Any ideas?
 
So, I exited Trainz completely and restarted. Went to lay track at 1.7 gradient, and it worked! For the first section. Went to lay second section, got booted out! Went back in, same thing again......first section good, second section boots me all way out.
 
Did an extended data base rebuild. Back into surveyor. I can now lay more that 2 pieces of track without getting booted, but it will not lay at my selected gradient. So, by choosing Apply Gradient, I can then click on up to three pieces of track, one at a time, and get it to work that way. But no more than 3 at a time........clicking on the 4th one causes track to go WAY up in the sky: gradient over 20! Only way to do the Apply Gradient thing is to do 2 or 3, fill in the ground under the track, and then add 3 more sections, apply gradient, fill in the ground....etc. This sucks.
 
Now it has gotten worse! I can only lay one section of track and then I have to hit the Apply Gradient to make it happen. HOWEVER, if the ground isn't high enough at the end of the new section, the gradient gets applied to the previous section! The new section will go to the ground and the last section will go high: way high. This is getting very frustrating! What used to take a minute to do now takes 10 minutes! And no one has any idea?

This Win11 ONLY handles Trainz 22. Nothing else is ever run off of this Win install. Everything else runs from Linux which is on a separate hard drive. This is a Ryzen 9 7900, 32g RAM, and an RTX 3080: I should not be having this kinda problem! When 2019 crashed twice and had to be reinstalled twice on my last machine, this machine was purchased JUST for running TRS22. It is updated continuously and all drivers are the latest and greatest.
 
How are you setting the track gradient? The track segment or multiple track segments must be selected (highlighted) before the grade value is applied.

See https://online.ts2009.com/mediaWiki...ls#.C2.A0Free_Move:_Set_Spline_Gradient.C2.A0 for setting the gradient with the placement tool

PS: To confirm I just tested it in build 122411 and it does work.
PPS: Sorry I misread your posts. But I just tried again in Surveyor 1 (Surveyor Classic) and it still works.
 
Last edited:
What I have always done since back in TRS17, was to pick a gradient and start laying track. No matter how many sections of track I laid, it just kept going up (or down). For instance, I once made a layout by starting where I wanted the track to start going up a mountain. Picked 1.5 gradient and started laying track. Every piece continued onward and upward until I finally stopped it at about 2,500 meters. There were probably 80 - 100 track sections. Now, that same process gives me nothing: the track spline is placed at the ground level whether that be 0, 150 meters, or whatever.

I will read what the link you sent, but again, the way that I have done it for the past 5 years no longer works since the update a couple days ago.
 
Just checked that link....I never did it that way before. Again, I would lay track and when I got to the place where I wanted it to start going up or down, I would put a positive or negative gradient in the box and every piece laid after that went up or down by the gradient chosen.
 
I am so close to deleting this off of my machine!! WHY can I no longer lay track the way that I have been doing it since I started with this 5 years ago??? All I want to do is add one single piece of track and get it to go up at the desired gradient and I can't! Been trying for 1/2 hour now and it simply will not work. What worked in 17, 19 and 22 up until the update will no longer work. In fact, NOTHING works when trying to get a gradient! NOTHING! I bought this to have something to play with when I retired, but there is no fun anymore.....just aggravation.
 
Just tried that link again. Nothing. No matter whether I enter a positive or negative number for gradient, and no matter whether I click on a section of track or a spline, it pushes it down under the ground! Does the same thing on roads, too. Just to try it, I placed 3 sections of road on flat ground. Tried the positive and negative, tried section and spline: every time it pushed it into the ground.
 
What I have always done since back in TRS17, ....
But we are in TRS22+ and using S2.0 which is a new way of doing things.
Just tried it and here is what I found.
Set the Grade in the Tools Options to some value.
Placed a new segment of track. As I stretched it out, the grade was being applied. If I joined it to another piece of track, it would join and the end would adopt the elevation of the track it attached to.
If there was no track to attach to, it would clamp to the local ground elevation. The mini Map confirms that during the placing of the track, before the end was released, the new track had the Grade set in the tools Options.

Later if I applied the grade to one or more track segments, they would adjust and adopt the grade I set in the Tools Options.

Don't know if this is a bug or a feature but BETA versions are like that. While it does take an extra step, being able to apply the Grade and other options to multiple segments at the same time does save time in the long run.
 
Last edited:
Previously, since I started with 17, if I were going along laying track on the ground.......and then put a gradient of say 1.5 in the box.......when I added a new piece of track to what was already laid, the new piece started at zero but then rose at the 1.5 gradient. If I stopped that piece and then added another to the end of it, it also increased in height by the 1.5 gradient. If I then changed the gradient to 3.0 (which I know is too steep), and again added on to the track that I was working on, that piece would now climb at the 3.0 setting. That is how it has worked since 17.

But now, I cannot by anyway that I have tried, get a new piece of track added at ANY gradient! The end of the new piece just goes to the ground level at that point.
 
From what I see as the current behaviour, the gradient is now applied after the track is placed and not during. So the end result is the same, just the method to get there is a bit different.
 
I could always apply it as the track was being laid. But now, no matter what method I use, I cannot apply a gradient: it goes to ground. If I click on the end of the track either with a positive or negative gradient, the spline BEFORE the end one changes and the ens stays the same. If I click in the spline before the end, it moves the previous spline. There is nothing that I do to move the end spline: it remains on the ground.
 
Using the + tool lay your track. Now select the fine adjustment tool. Click on the first section of track. Use the shift key and click on other sections you want to change. Add the % to the grade selection tool. Now click on the three linked dots at the bottom of the grade and select Apply grade. The track will increase the % you set. The three dots must always be at the bottom of the grade for the selected section. If you use a -% then the three dots will be at the top of the grade.
If you lay a track section later on and want to add a grade to it just select that section and the three dots at the connection point with the older track. It will grade from that point which is always fixed at that height.
 
might not be obvious but the symbols in the circles at each end of the selected track are what were referred to as the three dots.
track selected.JPG
 
OK....I see the dots on your pic. But I have never used Surveyor 2. What I am talking about worked fine in Surveyor 1 from 2017 all the way up to the update a couple days ago. Why doesn't it work now?

To be honest, I have looked at Sur 2 a few times, but I just don't understand it. And honestly, I really don't care to understand it. Surveyor 1 has worked just fine for me for 6 years. And I would like it to continue working for me. Why did it change? Was it meant to be changed or did some bug enter into the code? If it was meant to be changed, WHY?
 
Back
Top