Gameplay Timetable Sim - Stop Manual Couple

Discussion in 'PC Editor Discussion' started by Perks390, Jun 27, 2024.

  1. Perks390

    Perks390 Well-Known Member

    Joined:
    Dec 8, 2016
    Messages:
    344
    Likes Received:
    406
    I've got a loco runaround in my Niddertalbahn Modern timetable but in the simulation the service gets stuck on:
    LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +23:55:09.800, [TargetSpeedCondition] Stop Manual Couple, [Service] Stockheim Sidings Loco Run-Around, [Location] Lat: 50.32803, Lon: 9.00956, [CurrentVelocity] -0.00m/s, [OtherRailVehicle] RVM_HBK_DB_785pza_C_1, [OtherFormation] Stockheim Sidings Loco Run-Around_Uncpl0

    The loco uncouples fine, and will enter the track to recouple without issue but then it won't actually couple to it. It isn't a major issue as it's the final instruction in the service and there are no following services but it would be nice to get it working correctly.

    Has anyone had a similar error in the log and found the issue?
     
  2. mkraehe#6051

    mkraehe#6051 Well-Known Member

    Joined:
    Sep 14, 2022
    Messages:
    854
    Likes Received:
    1,881
    Are there any other lines about scripts being called (and failing) around the one that you've quoted?
     
  3. Perks390

    Perks390 Well-Known Member

    Joined:
    Dec 8, 2016
    Messages:
    344
    Likes Received:
    406
    This is the full set of text:
    LogTSWAI: AI has been stopped for 120.102730s
    LogTSWAI: TS2AIController::LogTargetConditionStatus: [TOD] +18:38:54.000, [TargetSpeedCondition] Stop Manual Couple, [Service] Stockheim Sidings Loco Run-Around, [Location] Lat: 50.32803, Lon: 9.00956, [CurrentVelocity] -0.00m/s, [OtherRailVehicle] RVM_HBK_DB_785pza_C_1, [OtherFormation] Stockheim Sidings Loco Run-Around_Uncpl0
    TS2Dispatcher: No active route requests for service Stockheim Sidings Loco Run-Around

    And this is how it's set up in the editor:
    TT.PNG
     
  4. Isaak

    Isaak Well-Known Member

    Joined:
    Aug 5, 2019
    Messages:
    341
    Likes Received:
    392
    Coupling/uncoupling can sometimes be a bit buggy. You might want to experiment with adding a 'wait' instruction before and/or after the coupling instruction (this is a load/unload instruction where you untick both load and unload) or add a 'goto' instruction (with call on dependency) into the coupling block. I've had the exact same (copied) instruction malfunctioning where another instruction worked. It seems coupling and uncoupling is a type of instruction that is very fragile and prone to some kind of bug. I didn't find one solution that fixed all errors yet, but deleting a malfunctioning instruction and replacing it with a new one sometimes worked.
     
    • Like Like x 1

Share This Page