2D Interpolator not working correctly

[Joseph Realmuto]

The problem in a nutshell is that once Open Rails uses the 2D Interpolator to parse data from an engine file it doesn't return to the file to continue reading other parameters. For example, if I place custom tractive effort or dynamic brake parameters anywhere but right at the end of an engine file, everything after those parameters doesn't get parsed. If I place both TE and DB parameters at the end of the engine file everything works fine except that I can't have both TE and DB parameters. Whichever one I put first is read and used, but the second one isn't.

[Matej Pacha (matej-pacha)]

I know about this feature since I'm using 2D interpolator and custom tractive effort curves. I don't remember, who is the author, but maybe I will have some time to solve it. Anyway, this is not a high priority issue.

[Joseph Realmuto (jtr1962)]

See the attached .eng file. Note the custom TE and DB parameters placed at the end of the file. In this case, only the TE parameters work. DB is working based on the MSTS parameters earlier in the .eng file instead of the ORTSDynamicBrakeForceCurves at the end.

[Joseph Realmuto (jtr1962)]

Matej,

Thank you for the quick response. I'm glad you've also been aware of this issue. It has existed for quite some time, perhaps even from the time the 2D Interpolator was added.

[disc (disc86543)]

For me it seems, if i write ORTSDynamicBrakeForceCurves first, then ORTSMaxTractiveForceCurves, both works. But if i swap these, so ORTSMaxTractiveForceCurves is the first, then ORTSDynamicBrakeForceCurves is ignored.

[Carlo Santucci (carlosanit1)]

Fixed in x.3180.