Timetable View

[chriswillis81]

Ok, so i'm not going to complicate my scenario, i'm just going to run one train for now. I'd like the scenario to start at 05:05am, so i've set it at that time. Now i've already worked out the times of my route manually as i've found that RW can be a little inaccurate with its timetable.......i.e getting to stations way too early or making it impossible to keep to time.

I've set my train to depart at 05:05am and in the timetable view i set my first passenger instruction up. It says i will arrive at my first station at 05:35am, well i know it will be about 05:30am, so i've amended the time but it goes red and does not like it.

How to you edit the timetable to show your own times and not those that have been predicted by the game?

[chriswillis81]

I've found a way round it to a degree.....

If i move the performance to 100% then the times are pretty much the same as what i worked out, but if its wrong and it says i am going to get somewhere at 05:40 and i know i'll be there at 05:42 then i can change the waiting time to 2 minutes. Only problem with that is if i arrive at 05:42 as i predict then its going to make me what 2 minutes then i'll be late.

hmmmm.......

[donny]

Play about with the performance percentage. I've often found that going over 100% helps and have even used up to 200% before. Similarly if you want to slow things down a bit, drop below 75%. Do be careful though I've occasionaly found that changing the performance % can also have an effect on train priorities.

[chriswillis81]

hmmmm well i hope that wont happen, but thanks for the advice.

[Kromaatikse]

Fiddling with the effort percentage is usually the right thing to do. It just changes the speed that the Dispatcher assumes the train will travel at, and AI trains will follow that assumption implicitly.

For whatever reason, the Dispatcher has no idea of line gradients, so you will usually find a need to use lower percentages uphill and higher percentages downhill, especially with steam traction.

[chriswillis81]

Maybe you can help me with this.

Below is a screen shot of my first train leaving the yard and running empty to Highgate Junction Plat 4. Timetable looks fine.

http://www.flickr.com/photos/64607879@N ... hotostream

But when i ran the activity, the moment the train leaves the yard and onto the mainline, it takes the wrong track and does not use the cross over to get onto the correct line. So i decided to place a waypoint in to direct the train through platform 2 of St Mary Hill. But this happened....

http://www.flickr.com/photos/64607879@N ... hotostream

I dont know why that way point should have any bearing on the times coming back down the line from Highgate Junction, it makes no sense.

[Kromaatikse]

It's hard to tell what's going on without the route in question installed.

However, if the waypoint causes the train to take slightly longer to reach the first instruction, and subsequent instructions are timetabled, then it might slightly miss the requirement for the timetable at some of those instructions.

[chriswillis81]

Thats exactly what happened, i've re-adjusted the % on each station and have the timetable pretty accurate now, thanks.

[chriswillis81]

Thats until today when i decided to run the scenario. I dont understand why if you leave the ''waiting time'' at 35 seconds, just like the default, why it does not let you leave after 35 seconds. I've made plenty of time to run this route and yet i still cant keep the train on time. I've just got to one station 70 seconds early and the counter has counted down almost 2 minutes????????? Why is it doing this?

[Kromaatikse]

What's the departure time for that instruction? If the Timetabled toggle is on, the Guard will wait until then to allow you to depart.

[chriswillis81]

What i said was i arrived 70 seconds early and it kept me there for 2 minutes. Surely with the wait time set at 35 seconds even the worst that can happen is it decides to keep me there 70 seconds so i leave on time, not 2 minutes!!!!!!, that now means i'm almost a minute late. Do that for a couple of stations and before you know it your 3 or 4 minutes behind.

[Kromaatikse]

But 70+35 = 105 seconds which is not far short of 2 minutes. Both the arrival and departure times count when the Timetable toggle is on.

[chriswillis81]

Let me put this another way. Arrival time 12:00:25 departure time 12:01:00 with a wait time set at 35 secs.

If i arrive at 12:00:25 then i would leave on time with a wait time of 35 seconds.

I actually arrived at 11:59:50 which is 70 seconds before i am due to depart.. Why would the counter count 2 minutes? if you have set it to wait for 35 seconds then the arrival time automatically adjusts to 35 seconds prior to departure, so i'm really confused as to why you would EVER sit at a station for more than 35 seconds when its set to 35 seconds.

Surely if you arrive BEFORE the arrival time then the counter should add the time from your actual arrival time, to the time set between the timetabled arrival and dparture time. So arriving 70 seconds before departure should mean a 70second wait. Or thats what i would expect. But the is railworks after all, nothing is ever as it seems

[Kromaatikse]

So you're saying that the departure time is set to 12:01:00, but the Guard refuses to close the doors before 12:01:50?

[chriswillis81]

that is correct i've had a word and he no longer works for me, but i'm worried other employees will do the same