[Stijn D.C.]

Hello,



MaxVelocity is a MSTS token on .eng & .wag files for maximum referencespeed of material.

But what Openrails do, if you reach this speed, is lower the tractionforce. :-(

So i wonna ask on the developteam for look to that, that MaxVelocity parameter is just for referencespeed of material that is only usefull for Train Control Systems, derailmarge...


I suggest to make new lowercasetoken "ORTSTractionMaxVelocity" for keep that lowering of traction until heading locomotive reach that speed, for trains where it exists.


So a .eng file without ORTSTractionMaxVelocity (XXkmh) on it, can be drive much speed as it can ( or TCS allows ) , like record trains...


If ORTSTractionMaxVelocity (XXkmh) is used on .eng file, than headinglocomotive not will gonna reach this speed in case tractionforce.


OpenRails must just use MaxVeloCity for the mechanical part only in my opinian.


If someone of the developteam can fix this, it gonne be also possible that a train with this on .eng

MaxVelocity ( 320kmh )
ORTSTractionMaxVelocity (270kmh)

The leadinglocomotive bring tractionforce down on 270kmh

I know that this is a strange thumbnail, it can be:

MaxVelocity ( 320kmh )
ORTSTractionMaxVelocity (400kmh)

or

MaxVelocity ( 320kmh )
ORTSTractionMaxVelocity (325kmh)


Too like example.


Important is that Openrails not bring traction down on MaxVelocityspeed and stay give full tractionforce after/above that value.


In advance thanks, Greetz,