Standard/Timetable scenarios

[Nippur]

Hello, what is the difference between standard and timetable scenarios?

[Phase3]

Standard you do not get points deducted or failure for being late, timetabled you usually do!

[BeenTrain]

In the context of making scenario's Timetabled scenario's are old.
Don't use them because you can not upload them to the Workshop. With Standard you can achieve the same using timed stops.

[Purno]

Originally posted by Phase3:

Standard you do not get points deducted or failure for being late, timetabled you usually do!

Incorrect. It's career scenarios that use scoring. Timetables are a method of rewarding points for objectives in career scenarios, but there are career scenarios (although rare) which start with 1000 points right from the start and do not use a timetable. Standard scenarios can also use a timetable, but no points are awarded.

The "Timetabled scenario" type is old and should not be used.

[benjoy]

My experience: only with "Timetabled" you can change from one to the other set train (Lok) during the game, whereby each train (Lok) can get their own tasks.
(Google Translate)

[Phase3]

Purno
It is not incorrect !!!! Some timetabled scenarios gave a "X" if you were late stopping at a station. Not all but some. They could have been converted career scenarios I suppose! They are still available today and still show up in RW_Tools (occasionally). AP publish some timetabled scenarios.

[Purno]

If you're late on a Standard scenario with a timetabled objective, the objective will not be completed.

I don't have experience with Timetabled scenarios as they are not used anymore. They cannot be uploaded to the workshop, so I'd recommend people to stay away from making them. No clue what advantage they have over Standard or Career scenarios.

[JohnnyR]

There is no reason to "not use" Timetabled scenarios despite their being redundant, unless you want to upload them to the Workshop. I am sure the majority of users don't want or need to do that. Out of habit, I use them all the time - there is nothing evil about them.

The "tick" for completion of the scenario is depenent on not running late in both types of scenario, if (and only if) the scenario maker has specified the need to be on time at one or more stops.

I am pretty sure Benjoy has given the main (only?) difference between the two types in the post above.

There have been a few minor changes to how Timetabled scenarios work since the introduction of Career scenarios - they no longer assess your timekeeping on a timed passing time, and no longer show a red cross if you have failed to complete correctly. As far as I know these changes affect both Timetabled and Standard scenarios.

[electronx]

Just so clarify the discussions above...
A scenario being timetabled can mean two things:

a) Objectives being timed. In career, you get a penalty for being late, in standard you will fail the objective after a leeway.

b) A scenario type (eTimetableScenarioClass), as opposed to eStandardScenarioClass or eCareerScenarioClass. Timetabled scenarios are in between standard and free roam scenarios in that you can switch to designated trains, or you may start as a railfan and have to activate your train once it appears. (Early TS scenarios simulate quite a lot of the network, Oxford-Paddington particularly obvious at that.) Many such scenarios are simply standards in disguise - in that case, you can safely convert them by overriding the scenario class. One such example is the Merchant Venturer on Bristol-Exeter.

Matt Peddlesden has a little tutorial where he only says the above and generally regards them a failed experiment, legacy feature, sort of. To be avoided.

Note - another difference is that timetabled scenarios do not show up in the Play menu. Might be able to play them from Build without overriding.

[Phase3]

Electronx
Timetabled scenarios can be converted to "standard" using RW_Tools and still retaining the timetable effects but can now be seen in the "play" menu.

[electronx]

I did so manually and it worked just fine :)
As per MP suggested

[JohnnyR]

Originally posted by electronx:

Note - another difference is that timetabled scenarios do not show up in the Play menu. Might be able to play them from Build without overriding.

That's not true. They don't show if you don't designalte a player loco (there is a certain logic to that if you think about it). Otherwise they will appear listed as Stabndard scenarios.

[electronx]

Originally posted by E Vilfart:

Originally posted by electronx:

Note - another difference is that timetabled scenarios do not show up in the Play menu. Might be able to play them from Build without overriding.

That's not true. They don't show if you don't designalte a player loco (there is a certain logic to that if you think about it). Otherwise they will appear listed as Stabndard scenarios.

Does the following scenario show up for you? It does have a player train, but it didn't show up until I changed the scenario class:

Routes\888f94a0-027c-4991-ab4f-08ad1dd5072f
Scenarios\403d64a9-db11-43ed-9e0a-67da140d97b6\ScenarioProperties.xml

The player train:

<DisplayName>The Merchant Venturer</DisplayName>
<sDriverFrontEndDetails d:id="215106432">
<ServiceName>1C04 07:30 Paddington - Penzance</ServiceName>
<LocoName>High Speed Train FGW Blue</LocoName>
<StartLocation>Bristol Temple Meads 12</StartLocation>
<PlayerDriver d:type="bool">1</PlayerDriver>
</sDriverFrontEndDetails>

Bristol-Exeter (2011) scenario supplied with the route.

[JohnnyR]

Yes it does here.

It is shown under Standard scenarios, Bristol to Exeter, High Speed Train FGW Blue, The Merchant Venturer.

Curious if you don't see it. Speak to Just Trains perhaps?