Train derails when uncoupling at slow speeds

Finglefumbers? Been there, done that. Sometimes it barely affects your messages, sometimes it renders your messages unintelligible, but the worst is when it transforms your message into something that makes perfect sense, just not what you intended to communicate. Sometimes it is a serious situation, sometimes hilarious. Gravity-assist classification yards can`t function correctly with either type of derailment.

For your original question, as amended, I have the same answer, unamended, but not the same comment. I`m afraid that I can`t really help you there. Some questions to help clarify the situation, though:
  • Does this always happen when you try to couple?
  • Under what conditions does this happen?
  • Can you produce two different situations, one where it always derails and one where it never derails?
 
I had the same issue with the lumber yard session for Legacy of the BN route when TRS22 retail was first released and N3V confirmed it was a bug. I did find a work around, I saved the session as my own ID and the coupling worked. I thought that the consist waiting to be coupled may already have been derailed as part of the install process for the package but it did not show up until it was coupled to the rest of the train.
 
I am building my own route making changes as I run a train, I save the route at the end of each session. It doesn't always derail when I couple. If fact running on my iMac it doesn't happen just on my ACER running on Windows 11.
I am still in the process of adding cars during a session so maybe that is my problem?
Is there a debug feature that might help?
Thanks for everyone's input
 
Ok. The issue is intermittent, happening only on one piece of hardware, and the route is of your own creation.

Because this is your own route already, it seems unlikely that @DennR`s solution is going to help any.

Since the conditions under which it happens vary, there isn`t much we can learn there.

Works find on one machine, never happening, but not on another, where it happens sometimes but not always. An estimate of how frequently it happens, as a percentage, might help, or not.

The fact that it is only one piece of hardware that this happens on suggests a solution that makes no sense on the surface but has apparently helped several other people: Triple-check that you have all the latest drivers for all your devices. Weird failures that seem to have no connection to your device drivers have been known to vanish with a driver update. Worth a try, and is generally considered to be a good idea on general principles. Even if it doesn`t help with your coupling issues, it`ll probably help your hardware run more smoothly anyway.
 
The gotcha is ones a PC and the other a Mac, so that's two different builds of the game engine executable. And that sounds like a bug.
 
And that sounds like a bug.
Hmm, that`s what I thought.
The gotcha is ones a PC and the other a Mac, so that's two different builds of the game engine executable.
Yup, but that`s not something that "we" can do anything about. Checking the drivers is, and even if it doesn`t help with this issue, it`s still a good idea. At this point, I don`t know what else to suggest. Do you?
 
Nope.

Keeping ones drivers up to date is just generally good practice. And, touch wood, not the harrowing crap shoot it used to be many years ago.
 
I would agree - it was usually a freighting process unwinding the so-called update. It still scares me, but after two recent ones it seems to now work as advertised.
 
@boleyd, are you talking about driver updates or updates to our favorite application? On the other hand, I don`t suppose that it matters much, save that driver issues can make a bigger mess when things go wrong.
 
I've had this issue off and on, but mostly self-inflicted, or at least I attributed the problem to being self-inflicted due to having freight cars too close to the end of the track bumper/buffer. The AI drivers will push the cars a bit hard and knock the freight off the end of the track. I've gone down to 3 mph (4.8 kph) without any issues in both TRS19 and TRS22.

Could it be those particular freight cars? This has been an issue in the past with some working better than others. Try swapping out what you are using for something else and see what happens.

The other issue I have found is coupling on a switch where the bogey, (truck) sits neither here nor there on the right tracks and ends up jumping.
 
Thanks for all your responses they have been most helpful. I have updated all drivers and other updates as well and TrainZ seems to be running smoothly. As to the coupling issue, I just ran a session and restricted my coupling to 1-2 mph and had no issues. This is a learning curve for me as I am a newbie. Thanks again for your support and assistance. I know that I will have to call on you again to bale me out.
 
You are very welcome. Was it the updated drivers that did the trick?

I hope that this does not offend you, but I`m getting an amusing mind-picture at the mention that you might need us to bale you out. Instead of dipping the water out of your problem (bail), you want us to tie you up like a bale of hay? Lest you think that this is a criticism of your no doubt accidental word choice, you should see what my posts look like before I go back and edit out the errors. I appear to be a very creative speller. My spell checker flags a lot of my words. Unfortunately, sometimes my spellings are so creative that the spell checker can`t figure out which word I have misspelled, only that I have misspelled it. Sometimes I have to try half-a-dozen different spellings before the spell-checker finally figures out what I`m trying to spell. Add to this a sticky keyboard, and I routinely get missing or doubled letters, or suddenly find myself typing into the wrong part of the message buffer, or not even typing into the buffer at all. Can you imagine what happens when the browser attempts to interpret your typing as a series of keyboard-shortcut commands? Almost anything, it seems.

Just to be clear: Not laughing at you for having made a mistake, laughing with you at the mistake. Feel free to laugh with me at my own mis-steaks; sometimes mine are real doozies. Speaking of mis-steaks, is that what you call it when you burn the beef at the grill?
 
I always do a 5 second delay before de-coupling. Allows for a complete stop. Keeps a target coupler in-place atop a trackmark for future couple-to instructions.
 
You are very welcome. Was it the updated drivers that did the trick?

I hope that this does not offend you, but I`m getting an amusing mind-picture at the mention that you might need us to bale you out. Instead of dipping the water out of your problem (bail), you want us to tie you up like a bale of hay? Lest you think that this is a criticism of your no doubt accidental word choice, you should see what my posts look like before I go back and edit out the errors. I appear to be a very creative speller. My spell checker flags a lot of my words. Unfortunately, sometimes my spellings are so creative that the spell checker can`t figure out which word I have misspelled, only that I have misspelled it. Sometimes I have to try half-a-dozen different spellings before the spell-checker finally figures out what I`m trying to spell. Add to this a sticky keyboard, and I routinely get missing or doubled letters, or suddenly find myself typing into the wrong part of the message buffer, or not even typing into the buffer at all. Can you imagine what happens when the browser attempts to interpret your typing as a series of keyboard-shortcut commands? Almost anything, it seems.

Just to be clear: Not laughing at you for having made a mistake, laughing with you at the mistake. Feel free to laugh with me at my own mis-steaks; sometimes mine are real doozies. Speaking of mis-steaks, is that what you call it when you burn the beef at the grill?
Automatic Speel chekers and completers love to mangle word choices. His bale vs. bail is probably one of those.
 
Back
Top