Factorio Forums

I'm not sure if this is considered a bug, but it seems a bit of a strange choice if it was intentional.
Not sure if this is already reported either, so apologies in advance.

If you have a train and one or more cargo wagons are connected in front of the train, it has a tenancy to invert the controls of going left and right. So right would be left and left would be right. But forwards and backwards are still how they should be. But this bug (from quickly testing it out) is a bit strange of how it's generated. From messing around with it, it only seems to happen when the train is connected by going up to the cargo wagons and connecting it as rolling stock instead of manually placing the train down. If the train was manually placed down, it seems to work regularly.

I apologies for not having any footage or screen shots, but showing screen shots of something like this seems a bit pointless as you can't see what I'm doing to cause it to happen. (pressing keyboard buttons). But if you try it out yourself, it'll probably apply to you too. If it doesn't, let me know.

I can confirm this for 12.30, it seems to have something to do with the previous direction of the cargo wagon.

To reproduce:

1. Have a north-south rail line
2. Have a junction in the northern part of the rail line with the directions: N, NW, NE
3. Place a locomotive heading south in the southern part of the rail line
4. Place a cargo wagon on the tail of the locomotive
5. Replace the locomotive with a locomotive heading north (the wagon is now on the nose of the locomotive)
6. Enter the locomotive
7. Drive north while steering left, the train will go the right way in the junction

Greetings Loewchen

I originally thought that applied only to the end of the wagon, but I seems to happen most of the time regardless of the direction of the wagon. But its probably due to the previous state of direction the train was before it was reconnected and wasn't updated.

Thanks for the report,

Can confirm this happens following the steps leowchan provided (thank you )

Hello, I had to go quite deep to understand what is going on, and the related changes were way too dangerous to make it to the 0.12 branch.

The problem is fixed, but only for 0.13