On Resuming Saved Activities, Locomotive Power is Throttled Back Momentarily!!??

[meeshu]

This is in regard to Open Rails version 1.4.

On resuming saved activities, I've noticed player locomotive(s) initially throttle back for a few seconds and then throttle back up again to the previous throttle setting!?

Why are the locomotives doing this on resuming activities?

[IndianRailways1601]

This is in regard to Open Rails version 1.4.

On resuming saved activities, I've noticed player locomotive(s) initially throttle back for a few seconds and then throttle back up again to the previous throttle setting!?

Why are the locomotives doing this on resuming activities?

I've noticed this too. I guess it's some sort of glitch, but I'll wait for someone more experienced to clarify.

[niknak]

Yes I've experienced this on the MG version for a while now. Its only momentary so doesn't really seem to affect the game.

[SlackAction]

Getting the same thing after updating to 1.4.

Generally not a big deal, but if you saved in a high throttle/low speed scenario while climbing a grade, it could present some problems.

[R. Steele]

If I remember correctly there was some trouble with excessive wheelslip when resuming an activity -- especially for the higher throttle settings -- so this method of resuming power was implemented. ( I could be wrong )

[PerryPlatypus]

If I remember correctly there was some trouble with excessive wheelslip when resuming an activity -- especially for the higher throttle settings -- so this method of resuming power was implemented. ( I could be wrong )

I believe you're correct, Gerry.

And I have encountered plenty of issues resuming activities while grinding up a mountain grade where I suddenly stall out... most frustrating is when the sudden speed loss actually drops you down to a speed where, once the throttle loads back up, you get wheelslip or broken couplers that wouldn't have otherwise happened at the speed being maintained prior to the save game resumption. (yet another example of creating new problems by "solving" another)

I had *hoped* the solution to the wheelslip issue would be that upon resuming a save, the sim would basically "ignore" wheelslip issues for the first 5-10 seconds of simulation after resuming a save, since it seems to take about that long for the sim to get "firing on all cylinders" and have everything stabilize in the physics calculation department.

Somewhat related to this issue is that the advanced adhesion model continues to be tied heavily to frame rates, which causes major issues for users on slower computers that get less than about 20-25 FPS... This is a frustrating thing to mitigate when you may have only momentary situations of lower framerates due to passing through a brief "high density" area of scenery, or having an AI train passing by... Really hoping the advanced adhesion model can some day be adjusted to tie to "real time" rather than the number of frame updates... (sorry for the rant )

[derekmorton]

>Somewhat related to this issue is that the advanced adhesion model continues to be tied heavily to frame rates

Not tied heavily, is IS coded to only update on the refresh rate. It needs is own clock to work from.

[geepster775]

Not only with restores, but entering activities anew where the train is supposed to already be in motion, the same sounds of throttle down/throttle up happens. It involves sounds only. No actual throttle movement.

[CSRX]

I've noticed this, and it's a bit frustrating when you are already struggling up a mountain pass. Dropping the throttle down to idle and back up quickly helps, but shouldn't be the fix.

[R. Steele]

I've noticed this, and it's a bit frustrating when you are already struggling up a mountain pass. Dropping the throttle down to idle and back up quickly helps, but shouldn't be the fix.

Yup, it sure is -- Shawn, ...try this

When you resume from a save, the sim is paused...don't start immediately --- wait for the fps to come up to the proper level...I can run everything at 60fps...so I wait for it to settle at around 60fps, ---- then hit the escape key.

[meeshu]

This throttling back of locomotives may be related to this thread.

Just ran another test train going up a hill at full throttle. Saved the activity. Then resumed the activity after waiting about 15 seconds for the frame rate to get settled before pressing the ESC key to actually resume the activity.

The locomotives actually throttled back (not just the sound of locomotives throttling back) with the train speed dropping fast while throttling back! But a few seconds later the locomotives throttled back up to maximum and the train managed to pick up speed before any stall occurring.

For very marginal situations where activities are resumed for trains running at full locomotive power up hills and at very low speeds (close to stall), I suspect those trains are more likely to stall because the locomotive power can't be brought up fast enough to prevent stalls.

Further testing is in order I believe to check that out for certain.

[CSRX]

This throttling back of locomotives may be related to this thread.

Just ran another test train going up a hill at full throttle. Saved the activity. Then resumed the activity after waiting about 15 seconds for the frame rate to get settled before pressing the ESC key to actually resume the activity.

The locomotives actually throttled back (not just the sound of locomotives throttling back) with the train speed dropping fast while throttling back! But a few seconds later the locomotives throttled back up to maximum and the train managed to pick up speed before any stall occurring.

For very marginal situations where activities are resumed for trains running at full locomotive power up hills and at very low speeds (close to stall), I suspect those trains are more likely to stall because the locomotive power can't be brought up fast enough to prevent stalls.

Further testing is in order I believe to check that out for certain.

It seems like this happens to some, but not all, which is why I have stopped trying to ask about it. If it doesn't happen to them (Folks helping with ORTS), then it simply gets ignore.

[derekmorton]

The code was put in to stop uncontrolled wheelslip on resume.
It happens to all, some are not noticing.
The programmer needs to revisit the code.

[creeddude98]

The code was put in to stop uncontrolled wheelslip on resume.
It happens to all, some are not noticing.
The programmer needs to revisit the code.

I just got the notice to update to version 1.5 a few days ago and the problem still exists. Is there any user level workaround to prevent this from happening?

[meeshu]

Even after all this time, I'm still getting the issue of Locomotives throttling back (automatically) despite manual throttle setting still set at 100%.

Presently running version 1.5.1 of Open Rails. Running test modern freight trains on Europe 2 (Innsbruck to St. Anton) along the steep portion of the route where the ruling grade is around 2.6%.

Test train with two locomotives and 33 well cars (3/4 of train with double stacks, the remaining well cars are empty), climbing the grade at around 30 mph.

Saved the activity while climbing the grade. On resuming the activity, the train speed starts to drop off quickly with apparent automatic throttling back of the locomotives despite the throttle set at full power (100%) and the locomotives sound as though they are still running at full power! According to the Track Monitor, Projected speed drops quickly to zero, with the actual train speed dropping off fairly quickly also.

On activity resumption, train close to stalling, but after maybe 5 seconds or so the respective speeds start to pick up again as it appears (full) power is automatically re-applied.

Really, this is unrealistic. There shouldn't be any change of train performance on resuming activities.

The Open Rails team really have to sort out this issue, so that there will be no automatic (apparent) throttling back of locomotive power on activity resumption.