Getting trains to slow before the speedsign

[REISCOOL]

On my route I have a number of places marked with invisible speed signs to mimic 'Slow Orders'. the only problem is that these slow orders are quite a bit slower than the mainline speed (Line speed is 50mph, slow orders are between 15/35mph) and when the trains hit them, they're still going at or near line speed, then quicky slow down to the slow order speed. Is there any way to get the trains to slow down before the marked point?

 

[AntonyVW]

Put a marked point further out?

 

[cascaderailroad]

Place many speedsigns, all in 5mph decreasing increments ... and too, with decreasing mph speedsigns, they are sometimes not activated until the last car pass's the speedsign.

If a train is longer than the distance between speed signs, AI can get confused.

I run 15,000 ton, mile long trains, with 6 locos head end, and 2 more locos in dynamic braking on the rear, and space my speed signs slightly longer than any 1 mile long train that I operate.

 

[JohnnyC1]

In your trainzoptions file change the -autopilotsignaldistance = to a longer distance from the default may help

John

 

[REISCOOL]

In your trainzoptions file change the -autopilotsignaldistance = to a longer distance from the default may help

John

I'm assuming that the distance here is in feet. I've set it to 1000 and the trains are starting to decelerate around 1000ft or so. Works well except on the drop to 15, but I can just set the distance further to allow for that.

 

[cascaderailroad]

Trainz measurements usually are in the Metric system ... the rest of the world uses it ... why not the US ?

 

[kamran]

in the edit session menu
activate the custom hud .this panel will show you the distance of next speed limitsign and also tells the speed limit ahead.the best custom hud is modula city custom hud

 

[JohnnyC1]

You might try adding a track mark before the speed post, tell AI to drive/navigate to the track mark, then issue another drive/navigate command after the speed sign.

John

 

[Dermmy]

The -autopilotsignaldistance suggestion is best, it allows the AI to 'see' and react to signals and other line-side 'stuff' quicker. Pretty sure default is 500 (a niggle at the back of my mind says 200) but either way that's nowhere near enough. It's a legacy thing from the original concept of Trainz as a small-scale model simulator. I experimented a fair bit with autopilotsignaldistance when I built my Clovis Sub routes which feature fast heavy trains which on default settings blew through every signal on the route! After a fair bit of trial and error I found that 1200 gives realistic results in most situations. I've used that setting in all versions from TRS04 to TS12 and found it to work pretty well...