That's odd that it won't let you change. Try this 2024.09.17-02.00.00 +0200 as that is midnight in your time zone. So right now your timetable is running from 2200 on the 16th till 1000 on the 18th. Reduce the Simulation Time Limit to 24:00 otherwise it will start simulating the second day even though you have Is Looping unchecked. Finally if your doing a timetable, the date entered is irrelevant as the player sets that when they select a service. Date is only applicable to scenarios.
Thanks now it simulates from 00:00:00 instead of 22:00:00 before I had to use an command (-starttime 00:00:00) I was wondering why
Cool. My only other advice is to go through the log after you simulate the timetable and make sure it is doing what you want.
Yes, I always check this part at first in the log file: TS2Editor: Of # total services... TS2Editor: # services completed TS2Editor: 0 services were still running TS2Editor: 0 services had not started If a service is still running or has not started, start digging deeper in the log file.
Hint: you just have to Ctrl - F for the text "es c" (without quotation marks) to find this part of the log file. Saves a bit of time on the search query
so I used the ts2.dbg.ForceTimetableStartWithIncompleteData 1 when testing an unsimulated timetable. I since put that back at 0. but whenever I use settime I still only get services that start from that exact time and later. nothing before. does anyone know what to do to fix that? I don't feel like waiting over an hour just to see what a train does ingame instead of on the 2d map.
The "forcetimetablestartwithincompletedata" instruction will only force services that were simulated at least once to be at the correct position when PIE starts. How would the editor know where a non-simulated service should be at any given point in time? So any non-simulated service will only start if its start time is later than the PIE start time AND if the editor knows the position of the formation used at the start of this service. E.g. if you add a new service that terminates at a certain location and a second service that starts at that location and didn't simulate them, then the second service will only start in PIE if the first service has run too. You can use e.g. 'slomo 4' (or more, at your own risk*) to speed up the PIE time that is not useful for you, or you can add a temporary formation at the start location of the second service if you only want to check that. The editor behaves just the same as before on my side regarding PIE functionality. (*) I've used up to slomo 20 successfully, but only if I was out of view of any service and slowed down to 4-8 before any formation in range had to move. Using a too high slomo value can result in SPAD's, derailings and other nasty stuff.
But I have now simulated my timetable. and did as matt said here (sorry for the ping). I set my time to for example when the train I want to see do stuff spawns in. that train indeed spawns in but then gets confused because the service that arrived in the station per simulation about 30 minutes earlier isn't there. and it thus tries to couple to not existing coaches. That is only half an hour wait to see what happens ingame instead of on the map. but I need to see what that 04:10 shunting move does with coaches dropped off at 23:40. (Yes I thus start simulating at 23:00) do I need to pack and make a distribution to test my services or does everyone wanting to test a late night service wait the sped up 16 hours from the start of their timetable? I honestly thought simulating would solve those issues since the game knows where trains are at then according to the playback tool, why doesn't that show in PIE then?
If the timetable didn't fully simulate successfully, then you still need to use the "forcetimetablestartwithincompletedata" command
what counts as a successful simulation then? I have one train having issues closing and opening doors and doesn't depart then (IC 945). and another which is scheduled as AI outside of the simulation parameters for now (it's a 19:00 train but I test sim 23:00 till 12:00) it fully runs the simulation. creates all data tracks. UE crashes and in the playback it looks fine. I want to reproduce what matt did there and not wait for 5 hours. putting it back to forcewithincompletedata makes if I spawn at 4:05. every train before that time. even the ones which have already cleared the map spawn in at 4:05 like the EN 463. I want to say it again. I'm not trying to test unsimulated trains. they have all been simulated already The interaction between EN 462. (EN 498 becoming EN 462) and IC 945 is what I am trying to see. I need IC 944 as well for that. they run fine in the playback. just want to see it happen in PIE without simulating it at 23:40. and speeding up the next 4 and a half hours.
"forcewithincompletedata" will still use the datatracks if they've been simulated, so in general I will also force it do so even after a full successful simulation.
It's successful if all services complete all their instructions. Search for "Total Services" in the log and you'll see if that was the case or not (and if not, why).
well I managed that. apart from the one with door opening issues trying to set door lock state to 0 from 4:30 until simulation end and one AI ICE outside of the simulation bounds all services complete fully. I wonder if it's showing door issues because I am coupling a second loco with it's front to the front of the train with the coaches. or because the coaches left at the platform have "lock doors for completion" turned off to leave the passengers able to board as the loco's run around and grab more coaches. then again that doesn't pose an issue with other services that do that.
Sometimes the "trigger door state 0" issue is caused by the platform the train is using or the instruction. Have you tried setting the door side manually in the instruction? If the one service is stuck with the door issue until end of timetable then its service doesn't fully complete.
yeah I have no clue. the loco (not two as I thought) pushes four coaches and couples to the stationary seven coaches after the rest of the previous train has locked doors and leaves the platform. moves them a bit back onto the platform so they all fit and do a quick load/unload now with door lock needed and end the player service. that one finishes fine. then it starts an AI service 2 minutes later and loads for 25 minutes and then leaves into a portal. but the doors it just succesfully opened and closed now keep getting a request to open filling my log with "Trigger door lock state 0 for service IC_945_Portal_In" for 12795 times. Failing to do so means it thus never leaves the platform. forcing either door side does not work. it complains with a note when I put it on left though. it says it's inferred to be the right side. a broken platform makes sense but completing a load/unload, ending the service. starting an AI service and failing to load/unload without moving really confuses me. all that changes technically is the traveling direction and thus the door side when it becomes AI. since the player pushes the coaches in the platform. and the AI loads it to leave the station
I have seen others describe very similar issues, what if you have your AI service drive the formation slightly forward to a new stop node and then the load/unload for 25 minutes.
Thanks for the tip. I added that specific stop marker plus leaving the doors open for the service switch as they don't need to close. to move it does closes the doors of course. moves up a little bit. and gets stuck again. I think for now I'll just remove the whole loading and let the player who shunted the loco give the service to the next driver with the doors open so it doesn't stay locked at the platform for 35 minutes. the AI will close them upon it's request to go to the portal and thus have no more issues. weird how platform 4 is broken but so be it. Edit: this worked, of 51 total services 50 services completed 0 services were still running 1 services had not started this means after figuring out a lot of weird shunting movements arguably the most difficult services are in the game and working. thanks everyone for your help and I will try your options again if I run into the same issue. I did make one service that normally doesn't stop on more than one place on the map drive to a location with no set arrival time. then with no start service time become AI into the portal. this seems in the playback to make it a non stop service. (I refuse to wait 2 hours to see in PIE if it actually is) does anyone know if this is how DTG did their playable through freight that continue as AI but stop for players? or want to tell me this is a terrible idea that I should not apply to all other trains leaving the map there. I'd love to hear some feedback on this because if it works safely I can add about 50 or so more playable services that would be AI. and I saw one of the freight services do that at that location in the DTG timetable.
If the train stops within the map and the service ends then that's a perfectly fine way to do it. Although, I'd recommend setting the new service to start at least 10-20 seconds after the end of the player service so the player can actually leave the train before it sets off.
Thanks for the tutorial and all the tips here. I'm having an issue with layers. I've added a layer for a Class 710 to my timetable and added the Goblin as a required DLC. However, when running the timetable simulation, the services on this layer do not run. No errors and no mention of them in the log other than 'service X did not start' for them all. Moving the services over to the main layer they then work fine, but obviously I guess this would cause issues for people if they didn't have the required packs. Anyone have any ideas how I might fix this?
Two thoughts. What did you name your layer? Is there a space in the name and if so you need to remove the space or replace it with a _. Second what name did you put in the Required DLC section? Is it correct and have you tried removing it and then simulated the timetable to see if it works.
Hi all, I didn't know where to put this, but I got a question regarding timetable simulation. I’m currently working on a timetable for the Bakerloo Line and encountered an issue that I can’t quite figure out. The timetable is set to run for 20 hours and 10 minutes, and I have a specific service scheduled to depart from Oxford Circus at 24:01 (00:01 the next day). However, in the simulation, the train actually departs at 24:00:43 (00:00:43). This creates a 17-second difference between the scheduled departure time and the actual simulation time, which seems to be a discrepancy I can't account for. I found an option called "completion time rounding setting", and setting it to "rounded" seemed to help initially—the train now departs at the scheduled 24:01. However, I’m still running into issues with timings later on in the simulation, particularly when the train reaches Waterloo. The timings there are still off. Could this possibly be a limitation of the editor? If anyone has encountered this issue or knows if there’s a workaround, I'd really appreciate your input.
Try setting the minimum time to e.g. 10 seconds so the service stays stationary for at least this time, no matter what time it arrives. Also take into account that the SCT is the time at which point the service will start closing the doors if 'lock doors to complete' property is set. This means the simulated completion time will always be a few seconds later Edit: avoid using the 'round' setting. If a service finishes the waiting time even a few milliseconds after the SCT, this will add a full minute before the service will continue.
I have set the minimum time to 10 seconds. I'm also aware that the train would depart 5-6 seconds after SCT, but I initially thought the "rounded" time setting was somewhat of a solution, but I guess not. The problem still persists, especially at Waterloo, where the train departs before the SCT. I suspect the issue might be related to when the service begins. The train (202 Harrow & Wealdstone to Waterloo) starts before midnight at 23:23, and everything runs smoothly until Regents Park (scheduled at 23:58:30). The issue seems to start when the train reaches Oxford Circus, where it's scheduled to depart at 24:01. It feels like the simulation starts to lose track of time or struggles to handle the transition past midnight. Interestingly, when I start a service after midnight, the train follows the SCT without any problems. This makes me wonder if the issue is linked to services that cross the midnight threshold. Has anyone had this issue? DTG Matt , can you please assist if you can?
I have multiple services crossing midnight without issues on my timetable. It's a very strange bug indeed, I've never seen services finish an instruction before the SCT. Can you show a screenshot of your timetable settings? Maybe we can spot something odd in the time setup?
Isaak - Is it okay if you can post a screenshot of your timetable settings? Perhaps I could have set something wrong, and also, does your service start before 00:00 or after, meaning for any train service? Thanks
dtg_jan - Is this a known bug or am I the only one having this issue? Simulations not obeying STC after 00:00 when service started before midnight. But having service start after Midnight, no problems obeying STC. Please any help is appreciated! Thanks
Hi jebaraanas, I am currently away from my dev pc, but I have assigned myself a todo to reply at the latest at the 20th of November. If you haven't heard from me by then, please feel free to ping me again.
I had that issue too. I learned you are supposed to keep counting. the next day or after 2300 becomes 24:00 and so on. a train starting at 23:50 and ending at 01:20 the next day will need 25:20 instead of 01:20. putting in any mark over 24h will show up in the tile as being the actual hour, but the sim will know it's after day one or 23:59 instead of before it.
I have tried both time formats. The train just doesn't comply with the STC that I've put. But I also learnt that whenever a train service begins after midnight, the train has no problem sticking to the STC, and that's even when a train finishes at Elephant & Castle at 23:56. The next service will start at 24:03; the simulation is correct all the way. It's only when service starts before midnight and finishes after midnight. I wish any DTG member could acknowledge this, but sadly not.
Good morning, unfortunately this is something out of my league, but maybe DTG Matt could take a look? All the best, Jan
That's what I opted to do for my timetable. For stops arriving before and departing after midnight, this is easy. If the train would be between two stops at midnight, I modified the timings so it is at a station stop at midnight. Then I activated a looping timetable so that the service ending at midnight seemlessly continues as the service starting after midnight.
Hi jebaraanas, I don't know if it's still relevant, but below a screenshot of my timetable settings. I am in Central European Time Zone, hence the UTC offset. The timetable looping is still off, as I'm having issues simulating when it is enabled. Therefore I am considering changing the timetable start time to 0:00.
Is there any change we can change the colour of the active trains for playback???? grey isn't the most vibrant choice , hard to see whe. You zoom out , thanks !
Yes, that's really hard to do, you would have to ensure that if a ends in a depot another diagram would start in depot and end in the station, much like the real thing, very hard to plan, good luck...or don't make it looping and just make a 28hr timetable?
I wouldn't recommend making a >24hr timetable as the game cannot differentiate services of multiple dates in the timetable selection screen. You have to make sure that a formation ends at the exact spot that it started, and in the exact same composition. It is possible, I am doing it on my MSB timetable and you don't have to tick the 'is looping' box in the timetable details for it to work. In fact: for some reason the simulation fails when this box is ticked. It only helps to detect which formations don't end their day on the correct spot when compiling the timetable, so use it for this and then untick it before simulating the timetable. Services past midnight will start anyway. Edit: also start the day at midnight and give it a duration of 24hrs.
