[Matej Pacha]

In this topic, I'd like to introduce a new version of how traction forces can be defined, introduced in X.2099. The older way is to use ORTSMaxTractiveForceCurves definition in the ENG file. Unfortunately, there are some issues about it and it is hard to read the definition itself. Maybe we should leave it behind.
I'm working with real world traction characteristics and it is much more easier to have it all in one table, easy to read, easy to import/export from/to a spreadsheet (e.g. Excel).
The basic idea of Interpolator2D class is kept, the difference is in its definition. It should look like:

Engine (
	ORTSTractionCharacteristics (	numOfRows	numOfColumns
		Throttle (	0	someMoreValues	1.00	)
		Table (														
			0km/h	0.00kN	someMoreValues	100.00kN
			...	...	...		...									
			160km/h	0.00kN	someMoreValues	50.00kN											
		)
	)
)

You can also use custom units as km/h, mph, N, kN, lb, lbf, ...

If you agree and find this way of definition useful, I will mark the ORTSMaxTractiveForceCurves obsolete. In attachment you'll find an example of traction characteristics that can be used as a template for content creators.

Excel table:
 ORTSTractionCharacteristics.zip (53.12K)
Number of downloads: 708 - revision uploaded

Plain text result:
 ORTSTractionCharacteristics.txt (16.39K)
Number of downloads: 680

Important note: this new type of definition can be used wherever you want within the Engine () block of the ENG file. The older ORTSMaxTractiveForceCurves causes parsing errors if the definition is not placed at the end of the file.

[ATW]

Looks nice, will change some of my ORTSMaxTractiveForceCurves which liked and try this out. Good we can use MPH instead of MS for a change.

[Matej Pacha]

Well, finally I'm revising my conclusions - the original ORTSMaxTractiveForceCurves should be kept because sometimes the calculation requires, that the independent variable would be current / force, what leads to the set of speed values is not the same for all the throttle tables. I'm going to try some changes to the Interpolator2D, maybe to inherit a new class dedicated for traction characteristics to introduce units to it...

[ATW]

Sounds like a good idea to keep but with slight changes and good readings, and the thing that would be helpful is for the speed reading of MS and Newtons to be default if no speed units are placed after numbers.

BTW. you got a PM Matej.

[jtr1962]

Do these changes also apply to the dynamic brake curves?

[Matej Pacha]

jtr1962, on 16 March 2014 - 04:59 PM, said:

Do these changes also apply to the dynamic brake curves?

Not yet, but it will be an option, same as with the traction characteristics - just insert the one that better fits your description.