Elvas Tower: Creating Activity Behaviors in Timetable Mode - Elvas Tower

Jump to content

  • 4 Pages +
  • « First
  • 2
  • 3
  • 4
  • You cannot start a new topic
  • You cannot reply to this topic

Creating Activity Behaviors in Timetable Mode Rate Topic: -----

#31 User is offline   Gwyd 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 16
  • Joined: 27-February 22
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 20 July 2023 - 03:17 AM

Thanks Rob, that's unfortunate. I have been able to compile from GitHub successfully (although not with all the contributed tools), so I might try make some local changes to see how far I can rectify that. I was trying to sort out the platform stop issue that I spoke about earlier. I think I have worked out that due to the combination of a bunch of safety factors, the AI will always stop very short on a terminus platform. The biggest issue is that most track ends on this route have an end of track signal, which the AI will always stay very much clear of.

#32 User is offline   Gwyd 

  • Apprentice
  • Group: Status: Dispatcher
  • Posts: 16
  • Joined: 27-February 22
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 20 January 2024 - 06:01 AM

Having used OR signal scripting to seemingly solve my previous issue with the ghost red signal, I now move onto another signalling issue. I have found that some trains, after waiting a long time at a red signal, will grant themselves call-on at random, and pull up to the next train. In some locations this is somewhat harmless, but in areas like terminus throats, it can jam the whole route. Below is the code that I have used for the 4 aspect signals (2 and 3 are similar), and the manual makes it pretty explicit when a train should recieve call-on, and all the cases I've seen don't meet it. Additionally, I have found that some trains at random will get "confused" when they reach their terminus, not a ) loading at the final station and, b ) not disposing as is defined in the timetable file. They just wait in their final platform seemingly indefinitely. I will try and record some examples in future to show what I mean. Any clue as to how I could troubleshoot these issues?
SCRIPT UK_4_ASPECT
extern float block_state ();
extern float route_set ();
extern float this_sig_lr ();
extern float next_sig_lr ();
extern float opp_sig_lr ();
extern float def_draw_state ();
extern float state;
extern float draw_state;
extern float enabled;
extern float sig_feature();
extern float TrainHasCallOn();
if (enabled && route_set() )
{
	if (block_state() == #BLOCK_CLEAR)
		{state = #SIGASP_APPROACH_1;
		if (next_sig_lr (SIGFN_NORMAL) >= #SIGASP_APPROACH_2)
			{state = #SIGASP_CLEAR_1;}
		else if (next_sig_lr (SIGFN_NORMAL) == #SIGASP_APPROACH_1)
			{state = #SIGASP_APPROACH_3;}
		}
	else if (block_state() == #BLOCK_OCCUPIED && TrainHasCallOn_Restricted() )
		{state = #SIGASP_STOP_AND_PROCEED;}
	else
		{state = #SIGASP_STOP;}
}
else
	{state = #SIGASP_STOP;}
draw_state = def_draw_state (state);
if (state == #SIGASP_STOP_AND_PROCEED)
	{draw_state = def_draw_state (#SIGASP_STOP);}


  • 4 Pages +
  • « First
  • 2
  • 3
  • 4
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users