Once again, fed up with TS2013, another big problem that I have yet to

[glenn68]

When you get a chance,PM me.

Glenn

[wackyhuman]

Note that 'timetabled' scenarios are NOT supported. Standard scenarios with a time table in it are. The functionality for timetabled scenarios is defunct and will be removed at a certain point in time. RSC strongly suggest not to use them.

Also note that when you create your own sidings/stops/destinations in TS2013, you have to create the siding, save your scenario, exit the scenario, go back into the scenario and it should work. In most cases that will resolve the 'electrification errors'.

[imnew]

Note that 'timetabled' scenarios are NOT supported. Standard scenarios with a time table in it are. The functionality for timetabled scenarios is defunct and will be removed at a certain point in time. RSC strongly suggest not to use them.

Also note that when you create your own sidings/stops/destinations in TS2013, you have to create the siding, save your scenario, exit the scenario, go back into the scenario and it should work. In most cases that will resolve the 'electrification errors'.

Just had to step in here and say thanks for this information.

[glenn68]

Note that 'timetabled' scenarios are NOT supported. Standard scenarios with a time table in it are. The functionality for timetabled scenarios is defunct and will be removed at a certain point in time. RSC strongly suggest not to use them.

Also note that when you create your own sidings/stops/destinations in TS2013, you have to create the siding, save your scenario, exit the scenario, go back into the scenario and it should work. In most cases that will resolve the 'electrification errors'.

Just had to step in here and say thanks for this information.

I agree totally.

Glenn

[wackyhuman]

According to 'Doc', you can actually use free roam scenarios much the same as 'Timetabled' scenarios, as you can have AI's running a timetable. Have not tried it, but have seen some free-roam scenarios with scheduled AI's, so I suspect he is right (as always )

[PapaXpress]

Would this be of any help?
http://thegradecrossing.blogspot.com/20 ... art-1.html

[PapaXpress]

Glad to here it. Micaelcorleone taught me a lot with just those two posts.

[OldProf]

Just want to note that both J.B. Friedland and I created successful Timetabled scenarios for TS 2012 and earlier versions. The advantage is that the player can drive more than one engine and the scenario can begin with the player waiting for his engine to arrive. Frankly, I haven't yet tried running one of those scenarios in TS 2013, but will put it on my "a round tuit" list; I don't see why they shouldn't run, even though not officially supported by RSC.

[wackyhuman]

They will work Tom, about 25% of the official RSC scenarios are still timetabled scenarios, RSC just advises against using them due to not being supported. And you can do the same (even better according to Doc) in a free-roam scenario.

[Machinist]

According to 'Doc', you can actually use free roam scenarios much the same as 'Timetabled' scenarios, as you can have AI's running a timetable. Have not tried it, but have seen some free-roam scenarios with scheduled AI's, so I suspect he is right (as always )

Frank, thank you for the nice words and just a small clarification... For RSC a "Timetabled" scenario is an especific kind of Standart scenario in which one, or more, or even all instructions to stop (for example, or to drop cars off etc.) at a certain location are assigned as "timetabled", i.e. if the instruction is not accomplished at the assigned time the scenario will fail at the end. Standard or Freeroam scenarios can use, or not, the timetable feature; if they use at least one instruction as timetabled RSC calls them "Timetabled" scenario, otherwise they are simply called Standard or Freeroam scenarios.

What I already did (for example the Show Case scenarios in the ES44 and SD70 10-engine packs by me and Krellnut) is a freeroam scenario using AI trains, but none of the instructions are "timetabled". The advantage of a freeroam scenario with AI trains versus a Standard scenario with no Player train is that in the freroam you have the control of every switch (in the Standard don't), other than that they work in the same way: you can jump forth and back any train close to your current train, at any time, taking its control.

I guess that due to the new Quick Drive feature RSC has changed the AI dispatcher behaviour at some point, once the timetabled instruction is likely not fully compatible with the Quick Drive way of auto-create scenarios. So which RSC is no long supporting is a scenario (Standard or Freeroam) with the timetable feature (there is a box to check for this purpose) within the instruction in the timetable screen. Confusing, eh?

Cheers,
Doc.