Railworks America

Greetings all...

I'm trying to create a custom scenario for the NEC starting at Trenton and ending in Phila. I had earlier problems finding and using DLC in the scenario editor but OldProf was able to extricate my cranium from my butt and now I can find DLC and place it.
Now, every time I try to create a scenario set at a specific time, the editor (as I'm adding stops) has a totally different time in place for the stop.

Example - I have a train scheduled to leave Trenton at 08:17 and the first stop at Levittown should be 08:25 but instead, the time that the editor creates is 12:00 for the first stop. When I try to edit that time, it turns red and I'm screwed.

Any suggestions??

Jeff

jetfixer170 wrote:Greetings all...

I'm trying to create a custom scenario for the NEC starting at Trenton and ending in Phila. I had earlier problems finding and using DLC in the scenario editor but OldProf was able to extricate my cranium from my butt and now I can find DLC and place it.
Now, every time I try to create a scenario set at a specific time, the editor (as I'm adding stops) has a totally different time in place for the stop.

Example - I have a train scheduled to leave Trenton at 08:17 and the first stop at Levittown should be 08:25 but instead, the time that the editor creates is 12:00 for the first stop. When I try to edit that time, it turns red and I'm screwed.

Any suggestions??

Jeff

First of all, why should the stop you mention take place at 08:25? Are you looking at a timetable, do you just know the route, or something else?

Hey Tom...

Yes, I'm looking at current SEPTA timetables for the Trenton line (specifically train # 9700).

I'm going through the normal steps when first creating a scenario (name, starting point and what type of scenario - choosing standard)
When I hit the little red and white clock symbol after placing the assets and creating the driver icon, it shows my departure time as 0817. Its only when I start to populate the editor with scheduled stops (the very first one, in fact) that the scheduled time changes from 0825 (again, scheduled at Levittown) to 12:00.

This happens when I choose timetabled scenario too...

Jeff

Perhaps you've just encountered the difference between reality and simulation? I'm not a fan of passenger scenarios, but I have occasionally tried them and have learned that Career passenger scenarios provided with DLC routes typically feature unattainable arrival times at stations. That is, viewing the player train's instructions in the editor turns up a lot of those red clocks you're writing about. Since I have Career scoring turned off, impossible arrival times would not affect me, but I have seen numerous posts here by players who complain that DLC Career scenarios force player-drivers into extremepy unrealistic driving practices.

When you see unachievable times, do you also see that dreaded red circle with a white X in it that indicates that the scenario will fail to load? If not, try playing your scenario as far as that first stop and see what happens. If so, I imagine that you'll just have to accept the minimum driving times ... wait a minute ... there's one other thing you might try. In the Pick Up Passengers instruction's properties box, there should be a small box with a percentage in it, typically preset to 75%. This is related to the percentage of he speed limit that the editor assumes you are using: for example, if the speed limit is 20 mph and that percentage number is 75%, the editor presumes that the player (or an AI driver) will move at 15 mph. Try setting that percentage higher and see if the arrival time shortens.

You really need advice from folks who write passenger scenarios, however. Good fortune!

Make sure the scenario start time for the player train is set to the same time as the start time in the scenario marker or a little after.

Using your time frames ...

The scenario start time should be ~8:15 with the passenger pickup command set to 8:17 manually (and the alarm clock checked). From there, you'll probably have to tweak the drive percentages and click/unclick the alarm boxes to force the times to recalculate to get a close representation of what you're trying for.

did you ever get this working proper? and if so what was the issue?