[Csantucci]

DieselEngineSpeedOfMaxTractiveEffort () is not recognized by OR. Accordingly to Realmuto's manual it is "The speed (in mph) at which the locomotive produces its maximum tractive effort" , and in more detail "Can also be used to adjust power curve of electric locomotives to a constant value over the entire speed range. The proper value to use is one-half of the speed at which the electric engine develops maximum tractive effort, or one-half of MaxPower/MaxContinuousForce."
In MSTS it effectively works this way, and there are .eng files (not only of diesel locos) where this parameter is used to modify the traction curve. OR does not use ths parameter, and therefore for such locos the traction curve of MSTS can significantly differ from the one under OR.
Does it make sense to implement use of this parameter in OR?

[Coolhand101]

Csantucci, on 14 February 2016 - 02:38 AM, said:

DieselEngineSpeedOfMaxTractiveEffort () is not recognized by OR. Accordingly to Realmuto's manual it is "The speed (in mph) at which the locomotive produces its maximum tractive effort" , and in more detail "Can also be used to adjust power curve of electric locomotives to a constant value over the entire speed range. The proper value to use is one-half of the speed at which the electric engine develops maximum tractive effort, or one-half of MaxPower/MaxContinuousForce."
In MSTS it effectively works this way, and there are .eng files (not only of diesel locos) where this parameter is used to modify the traction curve. OR does not use ths parameter, and therefore for such locos the traction curve of MSTS can significantly differ from the one under OR.
Does it make sense to implement use of this parameter in OR?

I have notice OR uses it own calculations for this. Plus the OR tractive effort curves table can be used to customise this as well. What is really missing is the "Run up time to max force" parameter. It can be really unrealistic to get full power on a Diesel engine in under a second.

Thanks

[ATW]

I notice an reported before too how ORTS doesn't even read MSTS RunUpTimeToMaxForce () but I have found my solver for what the topic says an in process of creating my own custome ORTSDynamicBrakeForceCurves an ORTSMaxTractiveForceCurves representing certain units an railway software settings. For the positive side I pretty much like ORTSContinuousForceTimeFactor plays around where I can change original Max Continuous force to something smaller where I can cook my DC traction motors out needing for them to cool off based on time limits in seconds an what my ORTS Traction Force Curves are set too. I wonder if its safe to share an test with some or just wait for features to be fixed before releasing engines even though I already release stock.

One thing I wish that would come in just like MSTS is the number of powered axles count where the more there is the less slippage on high forces an the less axles with high forces the more chances of slipping. Also needs to be something where ORTS can read what animated wheels are powered as I am sure some of us are annoyed seeing none powered axles slip like for example a ES44C4 GEVO an we do not see slippage for rolling stock like freight cars unless we turn them into engines.

[Hamza97]

Pardon me... but can someone explain name what ORTSContinuousForceTimeFactor does...?? I still don't get it. Also i can't get ORTSTractivecurves to function. Will be grateful if somebody can provide me with correct format
.... :)

[ATW]

I would be glad to say ORTSContinuousForceTimeFactor is like a time limit but in seconds for if slow speeds an max effort forces to die down to minimum force depends what it is minimum an set in the MaxContinuousForce.

May I ask what you have as far as ORTSTractivecurves... like where do you have it placed?

[Hamza97]

I have it in Openrails subfolder of the trainset, with same name as .end file, but still don't get custom reactive curves.....

[ATW]

Then that's why it's not working. I put my curves an in main eng file above the description line an bellow name line.

Example where is bellow.

Combined_Control( 0 1 0.5 0.5 throttle dynamic )
DirControl ( -1 0 1 1 )
BellToggle( 0 1 0 )
Sanding ( 0 1 0 )
Horn ( 0 1 0 )
EmergencyStopToggle( 0 1 0 )
Vigilance ( 0 1 0 )
Headlights ( 0 0.25 1 0 )
BailOffButton( 0 1 0 )
)
Sound ( "..\\..\\MC.SND\\MC_EMD710\\CSXSD70ACe_cab.sms" )

Name ( "DBeck UP SD70ACe 8311" )
ORTSBrakePipeChargingRate ( 64 )
ORTSEngineBrakeReleaseRate ( 38 )
ORTSEngineBrakeApplicationRate ( 34 )
ORTSBrakePipeTimeFactor ( 0.008221323 )
ORTSBrakeServiceTimeFactor ( 0.19146 )
ORTSBrakeEmergencyTimeFactor ( .015 )

ORTSContinuousForceTimeFactor( 900 )
ORTSMaxTractiveForceCurves (
0 ( 0.67 0.85 2 0 )
1 (
0mph 191000lbf
7.9mph 191000lbf
9.61mph 157000lbf
13.0mph 121433.65lbf
14.0mph 112759.82lbf
15.0mph 105242.50lbf
16.0mph 98664.84lbf
17.0mph 92861.03lbf
18.0mph 87695.83lbf
20.0mph 78931.88lbf
30.0mph 52621.25lbf
40.0mph 39465.94lbf
50.0mph 31572.75lbf
60.0mph 26310.63lbf
70.0mph 22551.96lbf
71.0mph 22234.33lbf
75.0mph 0HP
)
)
ORTSDynamicBrakeForceCurves (
0 ( 0 0 50 0 )
1 (
0MPH 0lbf
2MPH 62821lbf
6MPH 105000lbf
12MPH 105000lbf
23MPH 105000lbf
50MPH 52051lbf
)
)
Description (
"The SD70ACe,

[gpz]

ORTSMaxTractiveForceCurves is defined also in function of throttle controller. So it is in fact a curve-bevy, not just one curve. Please see this for example:

ORTSMaxTractiveForceCurves (
      	0 ( 0 0 50 0 )
      0.07 (
         0 28000
         1.39 24000
         2.78 18000
         4.17 12000
         5.56 7000
         6.94 1000
      )
      0.22 (
         0 38000
         1.39 34000
         2.78 28000
         4.17 23000
         5.56 17000
         6.94 10000
         8.33 4000
	 8.89 2000
	 9.72 12000
         11.11 11000
         12.50 10000
	 13.33 9000
	 13.89 5000
	 14.72 5000
         16.67 5000
	 19.44 2000
	     
      )
      0.38 (
         0 58000
         1.39 52000
         2.78 46000
         4.17 39000
         5.56 32000
         6.94 25000
         8.33 17000
	 8.89 22000
	 9.72 21000
        11.11 20000
        12.50 19000
	13.33 13000
	13.89 13000
        16.67 12000
	19.44 10000
	    
      )
      0.67 (
         0 76000
         1.39 70000
         2.78 62000
         4.17 55000
         5.56 48000
         6.94 40000
         8.33 32000
	 8.89 30000
	 9.72 30000
        11.11 28000
        12.50 27000
	13.33 26000
	13.89 16000
        16.67 15000
	19.44 14000
	    
      )
      1.00 (
         0 97000
         1.39 90000
         2.78 82000
         4.17 74000
         5.56 65000
         6.94 55000
         8.33 47000
	 8.89 39000
	 9.72 38000
        11.11 38000
        12.50 37000
	13.33 27000
	13.89 26000
        16.67 25000
	19.44 22000
	    
      )
   )

[ATW]

I know that an use to use it but for some unit's can't handle it always if one opens the throttle too heavy getting stuck at a RPM round where no power is increased unless you throttle back down to the last stages do to slow DieselEngineMaxRPMChangeRate but there is a cure I figured out a while ago. Did I mention when using all throttle curves I don't get the use to Run Up time to max Force time delay?

The way I have it here for now overcomes ORTS weak calculation by having too much prime mover power but not enough traction power using MSTS parameter curves.

[Coolhand101]

ATW, on 15 February 2016 - 09:25 AM, said:

I would be glad to say ORTSContinuousForceTimeFactor is like a time limit but in seconds for if slow speeds an max effort forces to die down to minimum force depends what it is minimum an set in the MaxContinuousForce.

When you say in seconds, is this when the time limit is reached that the max force starts to rundown to the MaxContinuousForce setting ?

I ask this because when using the 'ORTSTractionCharacteristics' table, the max force starts to run down as soon as power is applied. ie

Max force - 100kN
MaxContinuousForce - 50kN
ORTSContinuousForceTimeFactor - 3600

So an hour at full power, the tractive effort force has fallen from 100kN to 50kN!

Thanks