Request Stops in Activities

As some of you know; I had been looking at creating activities where you may/may not have to stop at a request stop.

Initially my thoughts were to use a combination of speed & location events to trigger the stop messages etc; however UKTS user "Borthstation" has suggested that I could also use timed events to do this.

Having thought a little about this; I think this should work - you setup a location event that is unactivated at a point. If you pass it before x minutes have passed; then you do not have to stop - if you pass it after then you do (with a pop-up advising you of the need to stop). In fact you could also do it the other way around so that in some cases you may get a message saying that

There are passengers wishing to board at...

or you may get

You have been advised that passengers wish to alight at...

I think this should work; however I suspect that the required logic to get MSTS to work may be quite complicated.

I may be back with more questions about events of the timed variety if there is anybody with an indepth knowledge out there!

Hi There,

What If

If you timed the action event to display soon after the departure time from the last station last station,

so

if you are on time or early you are way off down the line already.

The longer the distance between the last station and the request halt, the easier it will be to do.

How can you stop the message displaying if you are on time?

Mick

I wrestled with this very concept a couple of months back when penning an activity down the Windermere branch.... I just couldn't get things to work, so I settled for a (very) brief stop at each request station of just a few seconds.

Good luck in getting it sussed.. I'd be keen to learn the outcome

Cheers
T
(PS Gosh! Am I really that old? ... I'm not sure if I like a constant reminder every time I post! )

Hi guys,

I had thought about time events but believed they all ran from the start of the activity.

My experimenting has now shown that they are timed from when they have an activation state of at least 1.

Therefore it should be possible to use the time event to alter the state of the location events that determine if you need to stop. Therefore if you are slightly harder on the throttle you may pass the initial location point before it is active by a matter of seconds.

Interestingly this does mean that you can build in multiple events requiring a stop at a particular station.

A bit of further investigation/testing has found that timed events always seem to start from the beginning of the activity.

This does lead me to believe that in general I cannot use timed events to vary anything based on what time you actually arrive.

I am wondering about how OR deals with events going forward?