Zuu wrote:

Also, it might be wise to not clean the refit order when applying the transfer order regardless if the load order is changed or not.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4953#comment10684

Rubidium wrote:

If you force unloading (unload or transfer) with articulated vehicles then this order will cause the same cargo to be reloaded under certain circumstances.

E.g. a two part articulated vehicle, front part 100% loaded, tail part 50% loaded. Upon unloading cargo is unloaded at a steady rate, so when the tail part reached 50% the front part is 50% loaded. Then the tail thinks about refitting, but it can't because it isn't empty. It will then happily continue the (full) loading order. At a moment the front part reached 0% loaded, but the tail part is already 50% loaded so it won't be able to refit there either. In the end all the unloaded cargo will be loaded back into the vehicle.

So I'd actually propose disallowing loading or unloading when refitting at a station as that can give unwanted side effects, such as not refitting at all.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4953#comment10689

Zuu wrote:

I had though that it would work something like this:

1. Start unload/transfer
2. Wait until no wagon / articulated part is unloading/transfering anymore
3. Stop unload/transfer [if that is needed so that no part decide to start unloading later because station acceptance changing]
4. Refit
5. Start loading
6. Wait for loading to stop
7. Departure

However, from your explanation, I see that my idea of how my order was executed is wrong. To not have the problems that you clearly shown, either the availability of a refit order need to trigger a special (slower) unload/load process where unload and load is separated like above, or a restriction is added like you have proposed to not allow orders with load/unload and refit at the same order.

This comment was imported from FlySpray: https://bugs.openttd.org/task/4953#comment11975

andythenorth closed the ticket.

Reason for closing: Won't implement

I discussed this with Zuu, and he's happy with it being closed as part of Flyspray clean up.

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