Incorrect Default Values of MaxTractiveForceCurves

[steamer_ctn]

http://www.elvastower.com/forums/ind...97#entry273997

Any relevant feedback in regards to this issue?

[PerryPlatypus]

I can confirm that for the recent TrainSimulations products that I have been involved in where we use MaxTractiveForceCurves, we have been leaving the speed values dimensionless and assuming m/s since that is what the manual stated. I thought that at least at some point, this was being interpreted correctly by the sim at various speeds. Maybe compare behavior with the last Stable version and see if something has been changed more recently?

[steamer_ctn]

Maybe compare behavior with the last Stable version and see if something has been changed more recently?

As far as I can see from the code, this logic has been in place since 2014.

[steamer_ctn]

http://www.elvastower.com/forums/ind...ost__p__274129


A change has been made to the latest unstable version.

Please note the comments in the above post.