Atomic Systems

Hi . I am experiencing a issue with the station stop times , im not sure if anyone else has. In the scenario editor i put down that the service will stop at station x at xx:01 and then leave at xx:02 so that is a waiting time of one minute. When running the scenario I am often finding that the train is waiting in the station for a lot longer then a minute. Does anyone know why this is?

Thanks for any help
Paul

Are you arriving early?

sometimes early and sometimes late but its always the same station where it is spent loading to long

I have previously encountered this issue and was unable to get to the bottom of it or recreate it with any consistency. My guess is that it was related to AI traffic crossing the player path, which has been known to cause problems, but it is no more than a guess

Now I've got a problem I can't seem to figure out. I'm creating a TimeTabled scenario, but when selecting a station stop, and clicking the timetabled button, a time get's set for arrival and departure. The problem is that the doors always closes before the departure time. Even when arriving a bit early, the doors are open for about 30seconds, even though I scheduled a 2minute stop. On some stations, that have crossing trains over the player path, the door stays open till about 30 seconds before the signal clears, even though I should be standing for another 3 minutes.... I can nevr get the door to stay open until departure time, and thus causing me to run 5 - 10 minutes too early.... Is anybody else having this issue, and is there a way to combat it...?

NB## I am in TimeTabled Scenario, and do click on the little face icon for Timetabled....

ckmemphis wrote:Now I've got a problem I can't seem to figure out. I'm creating a TimeTabled scenario, but when selecting a station stop, and clicking the timetabled button, a time get's set for arrival and departure. The problem is that the doors always closes before the departure time. Even when arriving a bit early, the doors are open for about 30seconds, even though I scheduled a 2minute stop. On some stations, that have crossing trains over the player path, the door stays open till about 30 seconds before the signal clears, even though I should be standing for another 3 minutes.... I can nevr get the door to stay open until departure time, and thus causing me to run 5 - 10 minutes too early.... Is anybody else having this issue, and is there a way to combat it...?

NB## I am in TimeTabled Scenario, and do click on the little face icon for Timetabled....

Have you checked and accounted for, the difference between Sim time and displayed time. They get out of synch after a while. typically 3-4 minutes for a normal scenario. You can compare the estimated time on the F4 display with the clock, when you are close to a destination. ( stop at, pick up passengers and the like )

Peter

Can you tell me more about the time difference please? Is this what causes the incorrect station stopping times? and how would one overcome this to make sure the station stop times are correct?

regards
Paul

The simulation doesn't seem to use the time displayed. After a while of driving, you'll for instance see time displayed as 10:04:30 on the F4 display, if you, at this time is close to a scenario point, like a "go via", you might see the projected time as 10:07, even though, you are seconds from triggering the point in the scenario. This shows, you are between 2 and 3 minutes out of synch. You will also see this at a timed passenger pick up, You will get clear to proceed ahead of time. If you keep track of this time difference, as you progress through a scenario, You can make it work as intended, in the above example, you should aim to arrive 3 minutes early, for instance.

I'll notice this more on some routes, than others, but this can also be down to the typical type of scenario on various routes.

I don't have a solution, I just take it into account, when dealing with timed events in a scenario.

Does it make sense, It's hard to explain, when english isn't your native tongue..

Peter

The problem makes still no fun. I have this issues at several timetable scenarios which i have created and want to rework for RW 3. The showing arrival time next to the timetabled stopping time at F4 show the right time (i measure the time with a real clock). But the displaying time (bigger numbers) proceeds slower than the real time. After 25 km i have a difference of 2 minutes (simulation /real time). It's hard to build a correct timetable scenario with this problem. You can use the trick and change the arrival/departing time, but the user will still confused cause it's not the same like the displaying big time at F4. So i also can't clear out the scheduled timetable at the instructions. The fps were really good while driving (25~35fps), so this should not be the problem.