Going too fast around curves and snapping brake hoses...

[NoClue48]

I am totally perplexed...

[EDIT] I am running Open Rails...

Just about any scenario I've encountered in MSTS has resulted in a warning (and subsequent, end of mission) that I was going too fast around a curve; have snapped a brake hose; and need to stop to repair it and restart the run.

Initially, I was encountering this early on in a run--often having never or just barely left the yard. But, I started to pay more attention to the initial phases of my runs and kept my speeds well below the posted speed limits and was careful at switch transitions and crossing diamonds; as I know the gaps in the tracks can be rough on the undercarriage--I walked my share of railroad tracks as a kid and am still amazed at how wide they can be.

As a case in point, I was recently pulling 40 or 50 well cars and entered a curve fully 20 mph below the posted speed limit. My train traversed the curve for fully the first 1/3 to 1/2 the length of the train and then it happened. End of run.

Is there a tutorial on driving trains that covers proper slowing for curves that cause these issues? How do I recognize that the upcoming curve will snap my brake hose? I have searched and searched for a tutorial or something describing what's happening to me to no avail.

Any and all help is appreciated!

[NorthernWarrior]

Which routes?

The original default routes are plagued with issues like this, I even had it happen when visiting MS prior to release of the game in 2001, when I derailed on the Settle & Carlisle well under the posted speed limit. Obviously got swept under the carpet! Unfortunately, it is quite random so even slowing down further doesn't necessarily prevent the bug occurring.

[NoClue48]

Which routes?

The original default routes are plagued with issues like this, I even had it happen when visiting MS prior to release of the game in 2001, when I derailed on the Settle & Carlisle well under the posted speed limit. Obviously got swept under the carpet! Unfortunately, it is quite random so even slowing down further doesn't necessarily prevent the bug occurring.

Thank you for response... I just now see that I failed to mention that I'm running Open Rails and I don't know if this is a fault with the routes or Open Rails. I apologize for the oversight...

I have had it happen on nearly every route I try to drive--original and add-on. The only time I've ever completed a run is when I run an activity and use the autopilot. Autopilot is all well and good, but what's the sense? Run it once and you've seen the layout and the scenery of the activity.

I'd prefer to load up a locomotive and consist and set out to explore. Take one or the other switch and see where a spur leads to... truly explore the work of whomever created the layout.

The route I alluded to in my original post was the Marias Pass 5. I was trying to keep the speed at about 30 mph or lower throughout the trip and the issue arose at about 30% into the end-to-end run. As I said, fully 30%-40% of the train had already negotiated the curve when it occurred.

[baldwin]

Go to Options/Simulation and remove the tick from Curve dependent Speed limits. That will stop the breaking air hoses.

[NoClue48]

Go to Options/Simulation and remove the tick from Curve dependent Speed limits. That will stop the breaking air hoses.

Oh! That totally makes sense. Thank you and will do!

[R. Steele]

Thank you for response... I just now see that I failed to mention that I'm running Open Rails and I don't know if this is a fault with the routes or Open Rails. Autopilot is all well and good, but what's the sense? Run it once and you've seen the layout and the scenery of the activity...

Autopilot was implemented to give activity creators a means to test activities, not as a cruise control device. It really does save a lot of time in testing activities.

[NoClue48]

Autopilot was implemented to give activity creators a means to test activities, not as a cruise control device. It really does save a lot of time in testing activities.

Thank you for the info... I suspected as much and wasn't relying on it; just reporting what I had to do in order to finish, there for awhile.

And my apologies for not starting the thread in the right forum...