Hello trainzers,
Trainz is my way of travelling. It is a wonderful product also because it allows the user to make and add his/her own creations. Still there is an ongoing annoyance for me.
After all these years of Trainz, we still have the non-prototypical slowdown way before the location of a yellow signal. Even way before a yellow/green signal if it uses a standard signal state.
Yes I know that for some very heavy trains, that may be realistic.
On the other hand, if a slowdown is purposely imposed by the route creator, i.e. there is a speedboard signal on the line, the train only starts slowing down when it is quite close to the speedboard and needs an emergency type of deceleration to avoid speeding (which nonetheless it often does by 1 km/h...)
From time to time we read on the forum about placing additional invisible signals to avoid the slowdown. That affects the AI, however, and may have a negative effect in complicated trackwork.
Why o why has this behaviour never been adjusted in the base code (or made into an option)? I find it annoying, the more so because it unnecessary lengthens AI-driven rides. (I prefer riding trains over driving trains, which is a personal preference indeed.)
Maybe Tony Hilliam or one of the programmers involved can comment on this? I would appreciate that. My opinion may be unjustified after all. Thanks
Regards
Paul
Trainz is my way of travelling. It is a wonderful product also because it allows the user to make and add his/her own creations. Still there is an ongoing annoyance for me.
After all these years of Trainz, we still have the non-prototypical slowdown way before the location of a yellow signal. Even way before a yellow/green signal if it uses a standard signal state.
Yes I know that for some very heavy trains, that may be realistic.
On the other hand, if a slowdown is purposely imposed by the route creator, i.e. there is a speedboard signal on the line, the train only starts slowing down when it is quite close to the speedboard and needs an emergency type of deceleration to avoid speeding (which nonetheless it often does by 1 km/h...)
From time to time we read on the forum about placing additional invisible signals to avoid the slowdown. That affects the AI, however, and may have a negative effect in complicated trackwork.
Why o why has this behaviour never been adjusted in the base code (or made into an option)? I find it annoying, the more so because it unnecessary lengthens AI-driven rides. (I prefer riding trains over driving trains, which is a personal preference indeed.)
Maybe Tony Hilliam or one of the programmers involved can comment on this? I would appreciate that. My opinion may be unjustified after all. Thanks
Regards
Paul