So I'm trying to get this train of M3s to stop at the second station along the line (Davisville.) Eventually I'd like to test loading/unloading there, but I can't even get the timetable to progress past the first instruction! It's like the objective's completion criteria seem to get met, it turns off the stop marker, but then it decides to go for a coffee break or something, instead of going "boop," and changing the text at the top, and ending the service. DTG Matt , any idea what might be going on here? Or does anyone else, for that matter? (Matt's a busy guy, after all.) I've made a quick video to show what I'm talking about, complete with captions: p.s. sorry it's all grey, My display is set to HDR at the moment. Here's the relevant section of the output log, nothing jumps out at me here:
What do you have the formation set as? Never use parked as this messes up something with the doors. Also have you got the marker set as within, you may need to add a stop marker setup on the track platform.
Is this a Player Service (you driving) and are you stopping at a platform or a "spot" on the track ? It may not help you but I found in one of my tests that, if I overshot the "spot" marker, it (the blue marker) would disappear but the game would quietly wait until I'd reversed to the correct (no longer marked) stopping position before ending the scenario.
First of all, thanks for the helpful replies! I Forgot to mention that if I set the stop instruction to have a wait of 1 second, the message at the top changes to "Wait a moment," and stays that way . Well it's a player formation, set to "stopped, running" or whatever that is called, the destination is just the platform marker. I made an attempt to set a specific location, and that didn't make the stop instruction complete either. Found the core Car Stop BP component, so now I'll be making some car stops for 2, 4, 6, and 8 car trains, since I'll be needing them anyway. The whole track scenery tile, that the station is in, is from an old save before it got trashed; some sections have two proxies (I think maybe one got put in the scenery-tile? not sure,) there are old links in the ribbon for signals I deleted and the tile generally needs some track re-laid, so I may try that first. Also maybe putting in the next signal along the route could calm it down, I'll just have to see what I have time to try this week.
Do you have the stop position set to "within" and increased the stopping margin to 1000cm? If you have "overlap" (= default): a stop instruction might or might not trigger, there seems to be a bug with it.
Can you share screenshots of the instruction in your timetable and the options set in the properties? This will help with diagnosis. Also please share a screenshot of the instruction within the timetable to see what's around it. Thanks!
Will do, but it'll have to wait until I'm back home tonight. Yesterday was all about setting up a proper Scenario Manager (didn't help.)
Here are those screenshots. It doesn't work as just the service on its' own, or in my test scenario either.
As an aside, I did set up an objective composer, even though the objective manager is set to generate objectives from the timetable, and now it does display "objective completed" at the right of the top banner and awards some action points, which I don't think it was doing before. Tomorrow I may throw in another stop instruction further down the line, just to confirm whether it's the stop instruction or end service instruction that is the stumbling block. And eventually... I'll have passenger loading to worry about. I've actually got to wrap it up for tonight though, alas.
Thanks for the info. So, looking at one of my scenarios compared to this instruction, I would advise enabling "Use Stop Marker Position" especially if you're going to be using Car Stop markers in your stations. Also, you shouldn't need "Allow Reversing" enabled if the player is not required to reverse to reach the stop. Everything else looks right. How have you set your timetable default? I'll attach mine to show. Don't worry about the version number. You also might need to make sure you have an Objective Composer blueprint and set correctly in your Scenario Definition file.
Well the plot thickens: I've set the timetable for this service to stop at Davisville Southbound Platform (which it does,) wait until the scheduled departure time at 16:53:30, which it does, and then stop at St Clair Southbound Platform, which the player is never instructed to do. I've now simulated this timetable, and the AI driver has no problem making both stops: Code: TS2Dispatcher: FNetworkPathFinder::FindPath: Succeeded TS2Dispatcher: Find path for NewService took 0.000 seconds TS2Dispatcher: Acquiring Section: -1 (0) on route -1 for signal None to signal None for service NewService TS2Dispatcher: Acquiring Section: -1 (1) on route -1 for signal None to signal None for service NewService TS2Editor: TOD: +16:47:57.950, Progress: 2.47%, Avg Frame Time: 0.28ms, Total Time: +00:00:01, Active Services: 0 TS2: Service NewService started instruction 0 at 2016.12.31-16.51.00 TS2: Creating AI for NewService... TS2: Created AI for NewService LogTS2PassengerInfoSystem: Service NewService started on marker Eglinton_Platform_West_Side. No notification will be dispatched. TS2Editor: Service Start Time = +16:51:00.050 , Current Date = 2016.12.31-00.00.00, Timetable Start Date = 2016.12.31-00.00.00 TS2Editor: Simulation start time for service NewService is later than scheduled time. TS2Dispatcher: FNetworkPathFinder::FindPath: Succeeded TS2Dispatcher: Find path for NewService took 0.000 seconds TS2Editor: TOD: +16:51:00.050, Progress: 5.00%, Avg Frame Time: 0.28ms, Total Time: +00:00:02, Active Services: 1 TS2Dispatcher: Unable to acquire initial track section (0) for NewService acquired previously by NewService TS2Dispatcher: Unable to acquire initial track section (0) for NewService acquired previously by NewService TS2Dispatcher: Requesting route 1 at signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service: NewService TS2Dispatcher: Requesting route 0 at signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service: NewService TS2Dispatcher: Acquiring Section: 0 (0) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 1 (1) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 2 (2) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 3 (3) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 4 (4) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 5 (5) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 6 (6) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 7 (7) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 8 (8) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquiring Section: 9 (9) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Acquired route 1 at signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service: NewService setting junctions TS2Dispatcher: Acquiring Section: 0 (10) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service NewService TS2Dispatcher: Acquiring Section: 1 (11) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service NewService TS2Dispatcher: Acquiring Section: 2 (12) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service NewService TS2Dispatcher: Acquired route 0 at signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service: NewService setting junctions TS2Dispatcher: Setting junction {26F4A84E-48A7-26AA-6ED0-11907B72765A} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {0709CD1F-4ADD-A828-7663-85BBA242CB0E} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {A6CCC4E5-46A9-31DA-3A7D-7F88C115B753} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {7A21AE92-4EDB-3AF4-B3C1-A590F23D627A} to state 1 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {E95C5EF0-4A86-C11F-CFDB-CE90A4EB3B9D} to state 1 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {577A1305-4138-FBAF-105E-8EB5CEC875DE} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {68C90D36-4D7B-A288-1769-2880FB4DFE9C} to state 1 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {26F4A84E-48A7-26AA-6ED0-11907B72765A} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {0709CD1F-4ADD-A828-7663-85BBA242CB0E} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {A6CCC4E5-46A9-31DA-3A7D-7F88C115B753} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {7A21AE92-4EDB-3AF4-B3C1-A590F23D627A} to state 1 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {E95C5EF0-4A86-C11F-CFDB-CE90A4EB3B9D} to state 1 for service [NewService] due to route acquisition TS2Dispatcher: Setting junction {577A1305-4138-FBAF-105E-8EB5CEC875DE} to state 0 for service [NewService] due to route acquisition TS2Dispatcher: Assigning route 1 at signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for services: NewService TS2Dispatcher: ADispatcher::AssignRouteToSignal: Signal not delayable TS2Dispatcher: Setting junction {68C90D36-4D7B-A288-1769-2880FB4DFE9C} to state 1 for service [NewService] due to route acquisition TS2Dispatcher: Assigning route 0 at signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for services: NewService TS2Dispatcher: ADispatcher::AssignRouteToSignal: Signal not delayable TS2Dispatcher: Service: NewService entered section -1 (-1) on route -1 for signal None to signal None TS2: Content issue: Master data track (/TorontoSubway1954_Gameplay/Timetable/DataTracks(old)/test_timetable_MasterDataTrack.test_timetable_MasterDataTrack) version mismatch expected 790 found 787 TS2Dispatcher: Service: NewService entered section 0 (0) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService entered section 1 (1) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} LogTS2PassengerInfoSystem: Service NewService is departing from marker Eglinton_Platform_West_Side. TS2Dispatcher: Service: NewService entered section 2 (2) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService entered section 3 (3) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService exited section -1 (-2) on route -1 for signal None to signal None TS2Dispatcher: Releasing Section: -1 (-2) on route -1 for signal None to signal None for service NewService TS2Dispatcher: Service: NewService exited section -1 (-1) on route -1 for signal None to signal None TS2Dispatcher: Releasing Section: -1 (-1) on route -1 for signal None to signal None for service NewService TS2Dispatcher: Service: NewService exited section 0 (0) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing route 1 at signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service: NewService TS2Dispatcher: Releasing Section: 0 (0) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService exited section 1 (1) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 1 (1) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService exited section 2 (2) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 2 (2) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService LogTS2PassengerInfoSystem: Service NewService is approaching marker Davisville Southbound Platform and is stopping there. TS2Dispatcher: Service: NewService entered section 4 (4) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService entered section 5 (5) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService entered section 6 (6) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService entered section 7 (7) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService exited section 3 (3) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 3 (3) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService entered section 8 (8) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService exited section 4 (4) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 4 (4) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService exited section 5 (5) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 5 (5) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService entered section 9 (9) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Service: NewService exited section 6 (6) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 6 (6) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService exited section 7 (7) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 7 (7) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService exited section 8 (8) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 8 (8) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2: Service NewService arrived at instruction 0 at 2016.12.31-16.52.32 TS2Editor: TOD: +16:53:27.900, Progress: 7.05%, Avg Frame Time: 0.34ms, Total Time: +00:00:03, Active Services: 1 TS2: Service NewService completed instruction(Go To) 0 at 2016.12.31-16.53.30 TS2: Service NewService started instruction 1 at 2016.12.31-16.53.30 TS2Dispatcher: Service: NewService entered section 0 (10) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None LogTS2PassengerInfoSystem: Service NewService is departing from marker Davisville Southbound Platform. TS2Dispatcher: Service: NewService exited section 9 (9) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} TS2Dispatcher: Releasing Section: 9 (9) on route 1 for signal {9688DF3C-4406-77DA-0E60-608B7A54E0E3} to signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} for service NewService TS2Dispatcher: Service: NewService entered section 1 (11) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None TS2Dispatcher: Service: NewService entered section 2 (12) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None TS2Dispatcher: Service: NewService exited section 0 (10) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None TS2Dispatcher: Releasing route 0 at signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service: NewService TS2Dispatcher: Releasing Section: 0 (10) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service NewService TS2Dispatcher: Service: NewService exited section 1 (11) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None TS2Dispatcher: Releasing Section: 1 (11) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service NewService LogTS2PassengerInfoSystem: Service NewService is approaching marker St_Clair_Platform_Southbound and is stopping there. TS2: Service NewService arrived at instruction 1 at 2016.12.31-16.55.17 TS2Editor: TOD: +16:55:55.750, Progress: 9.11%, Avg Frame Time: 0.34ms, Total Time: +00:00:04, Active Services: 1 TS2: Service NewService completed instruction(Go To) 1 at 2016.12.31-16.56.00 LogTS2PassengerInfoSystem: Service NewService ended on notified marker St_Clair_Platform_Southbound. Removing service from notification list. LogTS2Timetable: Removed EOTD for service NewService - vehicle 2AFDA09E45EABE222F3FEBA7804EEB0A TS2Dispatcher: Releasing Section: 2 (12) on route 0 for signal {7A4C16D5-4733-7723-5AF9-7DBACC2263C8} to signal None for service NewService TS2Editor: Timetable fully simulated finish time: +20:56:00.050 TS2Editor: Timetable simulation took 4.03 seconds TS2Editor: Service NewService completed all instructions successfully TS2Editor: Of 1 total services... TS2Editor: 1 services completed TS2Editor: 0 services were still running TS2Editor: 0 services had not started This is particularly aggravating, because it means I could have the AI run the service quite happily, it's just with me behind the controls that it puts up a fuss. I may need to try a passenger-mode run next, just to rest my nerves.
Well, passenger mode works. Thank you, AI driver! A quite relaxing trip between 3 stations. Sometimes all that is needed is a fresh perspective. I'll probably set the matter aside for now, unless anyone spots something suspicious-looking in that simulation log I didn't catch. It may be a quirk of the M3 running on a route it wasn't meant for. Or maybe something to do with the doors? Oh well....
