#[✓2.3.15] Detach loco (after reverse) stops working in multiplayer

22 messages · Page 1 of 1 (latest)

uneven wedge
#

Game version: 2.3.13 stable, 2.3.14 unstable
OS: Linux

Steps to reproduce:

  1. Play one of the attached saves (preferably in mp)
  2. Note regional trains in Frankfurt Hbf sidings stuck with pending shunting commands
  3. Redo the shunting command queue in stabling sensors as follows:
    drive to shunting group, reverse, detach loco, use stubs and bypass track to reattach loco at western end, wait until 5-6 min before next leg, go to platform
  4. Manually redo the stuck trains' queues so they continue the aforementioned pattern
  5. Watch several subsequent trains execute shunting correctly, until they start getting stuck again

Wrong behavior:
A while after having set a correct shunting queue for stabling regional trains, they stop executing the "detach loco" command, and get stuck. The command is popped from queue, but the loco remains attached, and the train stops doing anything. This happens consistently every mp session.

Expected behavior:
Regional trains detach locos and perform shunting correctly, unattended

Map: Frankfurt am Main

Saves attached

May be related to #1281927266091274336 message

Screenshot_from_2025-03-23_22-15-08.png 📎 Outfrost20250322-1.zip
vapid pantherBOT
floral mural
#

@uneven wedge I see them sitting there but I can not explain why they did not detach their locos. Maybe the logs would be helpful

#

However, I was able to identify a different problem causing this command never being cleared from the queue

image.png
# 
FIX: Attach Loco Command failed when loco was internally loaded before train it was detached from
BUILD: 2.3.15
#

And that brings me an idea how the problem you described could happen

#

Maybe you accidentally grabbed this signal & dropped it back

image.png
#

Due to multiplayer nature it is actually bulldozed & rebuilt & the references are not preserved.

#

What is indicated by the invalid symbol on all sensors that use it in their shunting commands

image.png
#

Namely, the Detach Loco Command refers to the signal as DetachTowards

#

In this state, the trains receive the commands but the command is not executed correctly

#

After saving & loading, all seems to be ok (signal is correctly dereferenced after load) but the failed trains keep sitting there as a memento of the dark hour the game just underwent

uneven wedge
#

I don't believe we've touched any of those signals in build mode for the last several sessions

#

we can see if it happens again and get the logs

#

Though on a side note, I do believe the behaviour of these commands and the reasons why I might need to redo a shunting queue should be a little bit more intuitive (as a player, if I see the track and signal exactly as it was before, I assume the commands will work, until I'm explicitly told otherwise)

#

Maybe a shunting command could hold onto info on where a signal was and which way it was facing when the queue was created, so that if the reference is invalidated, it can check the remembered map grid cell for a replacement signal?

floral mural
#

I rather redo it to work the same in single and multiplayer

#

Needed for #1353491786919575653 anyway

uneven wedge
vapid pantherBOT
floral mural
#

@uneven wedge found & fixed thank to your multiplayer log - despite not being a multiplayer-related issue.

I re-set the train to the exact position & speed as you had just before it happened - and it happened for me as well, but only when game was running at normal speed.

FIX: Train did not detach loco occasionally due to wrong stopped state evaluation
BUILD: 2.3.15
#

[✓2.3.15] Detach loco (after reverse) stops working in multiplayer