Lamplighter, on 22 November 2020 - 11:13 PM, said:
When I replaced the ORTSTractionCharacteristics parameter with the ORTSMaxTractiveForceCurves parameter with the same values, everything was fine.
Internally within the code, the same parameter is set by each of the above tables. There has been a small variation to one (ORTSMaxTractiveForceCurves) that seems to allow negative tractive efforts to be entered.
I personally believe that the ORTSMaxTractiveForceCurves tables are the correct parameter to use, and that the other set of tables (ORTSTractionCharacteristics) was added in preparation for a feature that didn't proceed, and ideally should be removed.
Both these tables should use the same parameters, ie m/s and N.
Lamplighter, on 22 November 2020 - 11:13 PM, said:
So I don't understand why it doesn't work in the stable version 1.3.1.
Things that work in newer code versions don't always work the same in older versions, as changes may have been made.