Chris_Booth wrote:

Here are screen Shots of trains with incorrect wagons (this cant be dont in TTDPatch)

Attachments

• Chris Booth Transport, 1st Aug 2012.png (42.79 KiB)
• Chris Booth Transport, 2nd Aug 2012.png (42.80 KiB)
• Chris Booth Transport, 23rd Jul 2012.png (41.25 KiB)
• Chris Booth Transport, 29th Jul 2012.png (42.33 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/3146#comment6536

Ammler wrote:

Well, I wasn't able to reproduce it with the patch, doesn't mean it isn't possible. The easiest might be just not allow moving engines around, that might be what the patch does.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3146#comment6537

frosch wrote:

So the problem is when a engine (E) is at second position in a free wagon chain.

My first thought was to let OTTD try to attach the remaining wagons to E, and to move them to a free row if not.
But when there are more engines in the chain you might have to split it into multiple parts and still check the train-limit.

As that sounds quite complicated, maybe indeed forbid moving the front wagon when the second vehicle is an engine.

Edit: Oh, the problem also exists when ctrl-dragging the engine to a new row. In that case every wagon can be checked.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3146#comment6539

frosch wrote:

Testcase attached. Three ways to create an invalid train:

1. Ctrl-drag the dualheaded engine from first row to a new row.
2. Ctrl-drag the dualheaded engine from second row to a new row. (maybe caused by same code as 1, maybe not)
3. Drag the first wagon in the third row to new row.

Attachments

• fs3146testcase.sav (18.99 KiB)

This comment was imported from FlySpray: https://bugs.openttd.org/task/3146#comment6722

Rubidium closed the ticket.

Reason for closing: Fixed

In r18742

This comment was imported from FlySpray: https://bugs.openttd.org/task/3146