I am trying to create my first scenario, very simple. I set the start time for the service at 07:000,both in the ScenarioDefinition and in the RouteTimetable. But, the simulation starts at 05:00 so two hours early. What am I doing wrong here? The scenario should run at IOW version 1. Also wondering about the last digits in the time format: 2019.10.10-07.00.00 +0200 What does this mean? Is this an offset? I think it has the same value everywhere.
Also, there is a bug which means scenarios may not start at right time. There is a cmd you can do to sort time at runtime and put the scenario start time.
Make sure when you have a date and time field, if the contents has something like +0200 or +0100 at the end of it, the game will take the time you have typed and add or subtract hours on it. It will use the timezone your computer is in, which for me is +0200 from UTC as I am in The Netherlands. So my scenario starts at 8am, so I have to set it to 10:00. However, where a time field does not have a +0100 or +0200, then you put in the scenario time, so having a train start at 08:02 in my 08:00 scenario. To access the console in the game, press the ` (backtick) key and type the command Jasonic mentioned, obviously having the date and time to the date and time you need. Updated 02/10/2023 - Corrected key to press from tilda to backtick
Thanks, I had such a feeling. I think in most case you like to use the local time of the route and not your own timezone. The tilde is not working properly. I use a US keyboard layout as l Dutch people do and this works for UK keyboards only. At some point I will ask to improve that.
Actually I was mistaken, I think it's the Backtick ` key. I was using my MacBook Pro to stream from my PC as I was away. Try the backtick, the key above TAB.
Thanks for your help. I am afraid I was mistaken like you. The tilde is just above the backtick. I will do some checking and probably report it.
Failing that go into your settings for the editor and look at the keymapping. You'll find the key it's mapped to in there hopefully. I've not looked myself but have a look
If you enter the desired route time followed by "+0000", it will correctly convert it to your local time for the display so you don't have to work that out in your head
something that may help you as well which I've come to knowledge of recently. To have your scenario start correctly ensure it's the Scenario definition set to play in editor and not the timetable. Doing this the scenario should start along with what you've set it up to do and it should start at the time you've put into the scenario definition obvs ensure you take the + into consideration when setting the scenario start time.
Yes I have seen that as well and it it is very helpful. It looks you need to do that every time befor eyou satrt a scenario. Teh TimetableRouteObject has the same function attached, but that seems not to work.