Problem with re-coupling cars

[dgreg44]

Can anyone suggest what might be the problem here? I finally got around to making my first route and have been been enjoying the sessions for it in TANE.

But last night something odd has happened... I have a train with a string of Reefers and have a switcher engine come up behind it to take off the caboose to remove it to another train.
The switcher is unable to couple with the caboose (when I enter decoupling mode the coupler is grayed out and just gives a beep when clicked on). I've tried having the train back into the switcher but it doesn't matter, there's still no connection made. To make matters worse I tried decoupling other cars and coupling them to the switcher as a seperate string of cars. Now they too won't couple or re-couple to the initial train they were connected to or to each other. It's very frustrating. Can anyone have any suggestions what might be wrong or is this some kind of bug? Thanks in advance.

 

[davesnow]

I had that same problem. I think I even started a thread about it, but I don't think there's a solution. It's a T:ANE bug I think.

 

[JCitron]

I had that same problem. I think I even started a thread about it, but I don't think there's a solution. It's a T:ANE bug I think.

It's a confirmed bug in T:ANE SP1 HF4. I think it's mentioned as repaired in the list of bugs squashed.

 

[mikeaust]

It is possible to make the coupling by using the loco flyout at the side of the screen.
Cheers,
Mike

 

[llebrez]

Is confusing as to when and why it happens, and if you want to make a bug report, obviously you have to be able to reproduce the issue, and following Murphy's law, it wont happen. I notice that the way around this is to erase the loco and "make" a new one using the consist tab. That new one will couple and you can continue.

 

[JCitron]

Is confusing as to when and why it happens, and if you want to make a bug report, obviously you have to be able to reproduce the issue, and following Murphy's law, it wont happen. I notice that the way around this is to erase the loco and "make" a new one using the consist tab. That new one will couple and you can continue.

Murphy has a very large law book because this happens with a lot of things. Being a beta tester is quite frustrating because I've tested, tested, and verified, and tested things again and again before uploading a report only to be told that the problem can't be replicated!

 

[RHKluckhohn]

If in Windows, save your work, exit the program and restart the computer.

Then watch something entirely different go wrong.

:B~)

 

[WildWillyWacko]

I'm assuming you didn't make the mistake I did, but, I wanted the "Physics Rule" in my session mainly to increase traction under sanding and have more car sway and didn't adjust the cuppler breakage parameter and in testing some other function I was not coming in at a slow enough speed and the cuppler kept breaking and then not re-connecting. It took me a while to realize what I did cause the strain indicator is not shown on the HUD by default.

Wild Willy the Wacko

 

[JCitron]

I'm assuming you didn't make the mistake I did, but, I wanted the "Physics Rule" in my session mainly to increase traction under sanding and have more car sway and didn't adjust the cuppler breakage parameter and in testing some other function I was not coming in at a slow enough speed and the cuppler kept breaking and then not re-connecting. It took me a while to realize what I did cause the strain indicator is not shown on the HUD by default.

Wild Willy the Wacko

I've done things like this not just in Trainz and then spend hours trying to figure out why a program is crashing, or a system isn't working properly.