Railworks America

Hi Guys,
Forgive me if this is a simple question that has been asked before, unfortunately, 'time' is a word I cannot search for on the forums making it a challenge to get anywhere.

I have created a scenario that starts at 10:30 am, its almost 2 and a half hours long so it should end around 1 pm.
The timetable view is generating all the estimated times for destinations correctly.
However, when I play the scenario, the time that is shown on the HUD never changes - it stays at 10:30 am which has me at a bit of a loss - this is my first proper foray into Scenario making!

(If I stay parked, the ETA to the first destination does increase every second, so the clock is working...)

Thanks in advance,

Ah, typical. Make a post then find the solution.
There was an error in the Time Of Day blueprints, Time Scale was set to 0 instead of 1....

did you add a task then tell it to hide from the player because that will cause it

if you mean time to destination doesn't change,
it happens if there's additional hidden waypoints between current train position and last not hidden destination (the time will change, when you will cross last hidden waypoint)

savv_nz wrote:Hi Guys,

I have created a scenario that starts at 10:30 am, its almost 2 and a half hours long so it should end around 1 pm.
The timetable view is generating all the estimated times for destinations correctly.
However, when I play the scenario, the time that is shown on the HUD never changes - it stays at 10:30 am which has me at a bit of a loss - this is my first proper foray into Scenario making!

(If I stay parked, the ETA to the first destination does increase every second, so the clock is working...)
,

The first 'ETA' time will be the time to reach/complete your first 'objective' on your task list. This is usually a 'stop at' or 'go via' task. If you don't complete that objective (a checkmark will appear next to it in the task list in game) then the ETA won't change or update to the next ETA.

My reference was to the actual time in the Simulator, it never progressed.
Turns out it was the Time of Day blueprints at fault, time scaling was set to 0 instead of 1.