[jonas]

vitro, on 11 April 2020 - 04:32 AM, said:

The interval clocks itself can be done right now throw Check_Timing_Trigger() function.

Is the Check_Timing_Trigger() function an OR signal script function? I ask because I do not know it from MSTS. (But I am rarely involved with signal scripts at the moment either)

vitro, on 11 April 2020 - 04:32 AM, said:

... Interval clock turns off after 9:59, and turns on again when train passes exit signal at station...

Does the interval Clock really switch off when 9:59 minute is reached? Is this how it works in reality, for example in the Moscow Metro? ...sorry for my not knowing.

[vitro]

jonas, on 11 April 2020 - 05:09 AM, said:

Is the Check_Timing_Trigger() function an OR signal script function? I ask because I do not know it from MSTS. (But I am rarely involved with signal scripts at the moment either)

Yes, it is recently added or-specific function.

jonas, on 11 April 2020 - 05:09 AM, said:

Does the interval Clock really switch off when 9:59 minute is reached? Is this how it works in reality, for example in the Moscow Metro? ...sorry for my not knowing.

It depends on how Clock is set. After 9:59 it can switch off, or begin from 0:00. In Novosibirsk Metro it start counting only minutes on two right digit positions. Here's example of first case: https://www.instagra.../p/BTthroOFGuy/

[jonas]

Actually an interesting video - thank you for providing it!

Thought about the expecting OR game experience some more: In an activity lasting longer than 10 minutes, in OR/MSTS such an interval signal would always be dark when the player train is approaching, because there are no trains ahead whitch had reset the signal to zero and more than 10 minutes have already passed since actitity begin.
When the player train has passed such always dark signal it would reset to 0 and then count up to 9:59. All this "in the back sight" of the player train, the player would rarly see the count up, because he is already on his way to the next station. There he meets again a dark interval signal and so on.
vitro, how do you imagine the experience of such an interval signal for the player in OR? Maybe I am missing something?

[eugenR]

see here in Post #13:
http://www.elvastowe...ng/page__st__10
But I don't know how tu use this Functions
Regards
EugenR

[vitro]

jonas, on 11 April 2020 - 08:44 AM, said:

vitro, how do you imagine the experience of such an interval signal for the player in OR? Maybe I am missing something?

I expect that there is more than one train in activity or multiplayer. It is cool sometimes to follow a train with minimal interval, observing signals switching right in front of you, follow timetable, etc.

[roeter]

jonas, on 11 April 2020 - 08:44 AM, said:

Actually an interesting video - thank you for providing it!

Thought about the expecting OR game experience some more: In an activity lasting longer than 10 minutes, in OR/MSTS such an interval signal would always be dark when the player train is approaching, because there are no trains ahead whitch had reset the signal to zero and more than 10 minutes have already passed since actitity begin.
When the player train has passed such always dark signal it would reset to 0 and then count up to 9:59. All this "in the back sight" of the player train, the player would rarly see the count up, because he is already on his way to the next station. There he meets again a dark interval signal and so on.
vitro, how do you imagine the experience of such an interval signal for the player in OR? Maybe I am missing something?

You're forgetting about timetables. I have a timetable with a suburban route with trains at 5 mins. interval, and 3 mins interval during the rush hour. Any of those can be the player train. So unless you select the first train, there is always a train ahead of the player train within 10 mins.

Regards,
Rob Roeterdink

[eugenR]

jonas, on 11 April 2020 - 05:09 AM, said:

Is the Check_Timing_Trigger() function an OR signal script function? I ask because I do not know it from MSTS. (But I am rarely involved with signal scripts at the moment either)

Does the interval Clock really switch off when 9:59 minute is reached? Is this how it works in reality, for example in the Moscow Metro? ...sorry for my not knowing.

The Functions
Activate_Timing_Trigger()
Check_Timing_Trigger( x )
are new in OR and working, see here in Post #13
http://www.elvastowe...ng/page__st__10
With Activate_Timing_Trigger()in the Stop-Path of the signalscript you hold the Timer on zero
In the clearpath you hold the signal as long on red, as the timer isn't higher then the Time x ( in seconds)

But I don't see a way to read this timer, only perhaps, to show minutes to wait, you check the Timer for every minute and show the result.

	if (!enabled ||	block_state() !=# BLOCK_CLEAR || !route_set())							
	{
		state = SIGASP_STOP;
		Activate_Timing_Trigger(); 
	}
// Signal is enabled and the block ahead is clear
	else if ( Check_Timing_Trigger( 10 ))  // wait 10 seconds to clear the signal
	{
		state = SIGASP_CLEAR_2;		
	}
	else 
	{
		state = SIGASP_STOP;
	}
        draw_state = def_draw_state (state);

Regards
EugenR

[ebnertra000]

Could this timing trigger be used to delay the change of signals as a train passes it (from green to red, let's say). As it stands, if the cab isn't right up front on the lead unit, the signal will drop while it's still well within sight, even when travelling at speed. In most cases, there is a few-second delay between the signals being passed, and when the signal reacts to its being passed

[eugenR]

ebnertra000, on 12 April 2020 - 07:17 AM, said:

Could this timing trigger be used to delay the change of signals as a train passes it (from green to red, let's say). As it stands, if the cab isn't right up front on the lead unit, the signal will drop while it's still well within sight, even when travelling at speed. In most cases, there is a few-second delay between the signals being passed, and when the signal reacts to its being passed

With the new Functions of Rob, there would be a solution:
http://www.elvastowe...ode-signalling/
see: additional signalscript functions

	if (!enabled ||								
		block_state() !=# BLOCK_CLEAR ||				
		!route_set())							
	{
		state = SIGASP_STOP;
		if ( Check_Timing_Trigger( 5 ))
		{
			draw_state = 0;
		}
		else
		{
			draw_state = this_sig_lvar( 0 );
		}		
		
	}
	else 
	{
		state = SIGASP_CLEAR_2;
		draw_state = 1;	
		store_lvar( 0, draw_state );
		Activate_Timing_Trigger(); 
	
	}

store_lvar is storing the drawstate of the cleared signal ( because mor complex signals have more than one clear_states)
in the STOP-Case the signal is switching immediatly to State = SIGASP_STOP
but it will show after changing to STOP for 5 seconds the "old" draw_state.
Regards
EugenR

Edit:
A better solution would be, if Rob Röterdink could realize a new Function as
Train_is_passing the_Signal
This Function should change to true, when the !=# block_state is changing to true and the train is passing the signal.
together with store_lvar ( 0, draw_state ) the Signal could show the Clear draw_state until this Function change to false.

Regards
EugenR

[VicenteIR]

eugenR, on 12 April 2020 - 12:07 AM, said:

But I don't see a way to read this timer, only perhaps, to show minutes to wait, you check the Timer for every minute and show the result.

It looks like a signal heads of type (let's say) INFO may be created on one shape. On the clock we have four digits, each digit is a signal head - four digits - four signal heads. The last digit will show (n) from the function. The funtion needs to count only from 0 to 10 in this case. At 10 it will reset to begining . The right digit of seconds will have nine draw_states that should be (n) from counter itself. From 0 to 9. Other digits should be set by variables by calling this_sig_lvar (key) function. Decimal digit should have six draw_states. When the function will counts first time, draw_state will be 0. When you reset the counter, lvar stored will be (key,1) for first reset, (key, 2) for second etc. When this digit ups to 6, reset it to 0 and start to count the digits (signal heads) for minutes. This clock may resets when a train passing the marker of the signal or when next NORMAL signal gets least restrictive state by id_sig_lvar (sigid, key) or next_sig_lvar (key). The question is how much time will take a function reset because on this way the clock will not be 100% accurate )))