Bug ?

[ka959]

If you have a train with a driver, and are driving another loco yourself, and wanted to back up to, and couple to, this other loco, to begin a double-header run, and once you've coupled to the train loco, then the whole simulation just crashes to the Desktop.

This is what usually happens to me. It's OK if the other train doesn't have a driver though, and you can couple to another driverless loco on it's train, and take the train as though you're on a banking engine without trouble. Has this crash happened to any of you, when you try coupling to a train with a driver ? SHOULD is happen, or do you think you should be able to swap between locos on a double-headed train, if you wanted to view the lead engine from the cab of the trailing engine, just out of interest ?

Regards...

Jim McDermott

[AndiS]

There was at least one thread on "banking an AI train". If you search for the word banking, you will find several statements.

In general, the official position is that AI trains cannot shunt, which seems to include that a consist with a working AI engine cannot couple anywhere, without crashing in some form or the other. (Generally not crashing to desktop, but "only" crashing the train, even at minimal speed.)

Most likely you found the solution anyway (removing the driver), but you certainly find interesting bits in other people's reports.

[CaptScarlet]

I just did a quick test in a test "standard" scenario I play with and I uncoupled my engine and moved it along the track, added a new engine to the old consist and added a driver ( and no instructions ). I saved the changes and started the scenario, reversed back to the consist, coupled with no problem and continued the scenario as before. The only thing I could think of is if you used a timetabled scenario marker perhaps or did that train have some driver instructions added but completed?

John

Correction - I tried both a timetabled scenario and coupling to a Ai train after it had finished it's instruction and no CTD .