New Route - Signals Question

The MSTS 1 Route Editor can be a beast to use, but it's capable of some amazing results, here you can talk with the wizards that are building some of the fantastic routes available and learn how to make your own.

Moderator: Moderators

Locked
ghills
Been on the forums for a while
Posts: 220
Joined: Wed Dec 08, 2004 6:39 pm

New Route - Signals Question

Post by ghills »

I have got to the stage where I am testing out signals. I downloaded Simon Barnes' BR(E) set and they look great. However, I am having some problems getting them to behave consistently.

As I had no signals on my route I overwrote the sig files and all appeared ok and on the whole they work fine. However, I have the following problems (so far):-

1) Feather Lights stay on when signal turns to red.

2) Penultimate signal shows yellow if going straight on into final platform but shows green if going left or right. That signal has both feathers and has one junction in each direction after the signal. It is linked to both.
The signals by the buffers show green also, except when going straight on and that is red as desired.

Any ideas would be greatly appreciated.
User avatar
systema
Very Active Forum Member
Posts: 3829
Joined: Mon Sep 08, 2003 8:00 pm
Location: The Heart of Cheshire

Post by systema »

ghills,

For the 45 deg feathers try modifying your script files as below.

All you need to do is change 'next' to 'this' in the second line of extern float and in the if statement.

///////////////////////////////////////////////////////////////////////////////
SCRIPT BR_E_R45F

// BR(E)Right Hand 45deg Feather

extern float route_set ();
extern float this_sig_lr ();
extern float draw_state;

// If required, show the 'stop' indication. (operates on 'AUTO' basis
if (this_sig_lr (SIGFN_NORMAL) ==# SIGASP_STOP || // Main sig on STOP?
!route_set()) // Switch not set as per link?
{
draw_state = 0;
}
else
{ draw_state = 1;
}

///////////////////////////////////////////////////////////////////////////////////////////////////////////////
SCRIPT BR_E_L45F

// BR(E)Left Hand 45deg Feather

extern float route_set ();
extern float this_sig_lr ();
extern float draw_state;

// If required, show the 'stop' indication. (operates on 'AUTO' basis
if (this_sig_lr (SIGFN_NORMAL) ==# SIGASP_STOP || // Main sig on STOP?
!route_set()) // Switch not set as per link?
{
draw_state = 0;
}
else
{ draw_state = 1;
}

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////

This is because the indicators are not included as part of the signal set as separate complete signals. The indicators are tied to the appropriate signal by the coding but need to know what THIS signal is doing not the NEXT one. This should cure problem 1.

Problem 2 I do not fully understand. Do you have signals placed near the buffers at the end of the track with points near the buffers?

Mick Clarke
ghills
Been on the forums for a while
Posts: 220
Joined: Wed Dec 08, 2004 6:39 pm

Post by ghills »

Thanks for that Mick, I'll give it a go.

As for problem 2, I placed some signals at the buffers as I read on another, old thread that you have to have a signal after the feather signal to get it to work - which it does. However, I have a neo-3-way point approaching the station. That is, you can go left into PL1, straight on into PL2 and right into PL3. (Naturally I have had to use a left point and a right point instead of a 3 way).

Anyway, the feather works for Platforms 1 and 3 but the signal is green and so is the one at the buffer. If I go straight on into PL2 which requires no feather the signal is yellow - as desired - and the one by the buffer is red - also as desired).

Hope it's a little clearer.
User avatar
systema
Very Active Forum Member
Posts: 3829
Joined: Mon Sep 08, 2003 8:00 pm
Location: The Heart of Cheshire

Post by systema »

I presume the feather signals are 4 aspect as per the BR(E) set. I think they are the only ones with feathers.

How feathers work depends on the scripting. They are normally what is is known as 'info' signals in MSTS. That is they do not control anything but give an indication depending on prescribed conditions. In this case the state of the signal proper and the route set. The BR(E) feathers do not require a signal after to work since they integrated with the normal 4 aspect signal, however, they will show incorrect readings if not linked to THIS signal rather than the normal NEXT. It is the signal proper (4aspect part) that is dependent on the next signal for its aspect indication. Its just the way they have been set up but the creator made a mistake leaving 'next' in the code for the feathers. Otherwise I agree, these are very good signals.

I would say therefore try removing the signals near the buffers and see what happens. I don't know why you get green though on entry to the platforms. it should show at least double yellow as the last signal should be on yellow. (Explore Mode) When you remove the buffer signals the entrance signal should show single yellow.

Mick Clarke
User avatar
johny
Very Active Forum Member
Posts: 2609
Joined: Fri Dec 07, 2001 12:00 am
Location: N. Warks, UK.

Post by johny »

I trust you have contacted the author of these signals regarding these problems so that a patch to the kit can be made, rather than just let him maybe discover in the future that there is/has been a problem.

John
User avatar
systema
Very Active Forum Member
Posts: 3829
Joined: Mon Sep 08, 2003 8:00 pm
Location: The Heart of Cheshire

Post by systema »

John,

The amazing thing is this is the first time that I am aware of, any one has reported this problem. This signal set has been out some time. Lets see if my scripting works for ghills and if so, I agree the author needs to know about the fix.

Mick Clarke
User avatar
johny
Very Active Forum Member
Posts: 2609
Joined: Fri Dec 07, 2001 12:00 am
Location: N. Warks, UK.

Post by johny »

Mick,

It often works out that way, recently there was a reported problem with John Milligan's semaphore kit, that was due to a missing ) at the end of the types section in the sigcfg.dat file, that kit had been out six months or more before the error was found. I guess the knowledgeable using that kit realised what was wrong when copying and pasting in to their route, so nothing was publicly known about it until someone, less knowledgeable, ran in to trouble and wondered why MSTS would not load.

John
ghills
Been on the forums for a while
Posts: 220
Joined: Wed Dec 08, 2004 6:39 pm

Post by ghills »

Mick, you are a genius and I'll fight anyone who says otherwise :-)

Thanks so much. You've really made my day. Even the dummy activity - at a thru station with a passing AI train - worked like a dream.

We better let the author know. Should I send a pm?
User avatar
systema
Very Active Forum Member
Posts: 3829
Joined: Mon Sep 08, 2003 8:00 pm
Location: The Heart of Cheshire

Post by systema »

My pleasure.

By all means PM the author and let him know the problem and its solution.

Mick Clarke
Kevin99
Been on the forums for a while
Posts: 150
Joined: Wed Feb 21, 2007 4:08 pm

Post by Kevin99 »

Can I push in this conversation with an associated signal problem. I too have built a short route and have started to add semaphore signals. At first glance all seems to be OK however my distant signals fail to clear when a train has passed. I have rearranged the positions etc. still have the problem. I noticed that the display in the activity editor shows these signals in out line rather than red or green.

When I built the route I used the signal shapes from the Mersey route and the sigcfg and sigscr from UK1.

I would be gratful if anybody could help

Thanks

Kevin99
User avatar
WSR2005
Very Active Forum Member
Posts: 1359
Joined: Wed Oct 05, 2005 6:22 pm
Location: South Devon
Contact:

Post by WSR2005 »

Distant signals only clear when the home signal it precedes clears, therefore you will not be able to clear a distant signal merely by passing it unless the home signal is right next to it.

Tim
ghills
Been on the forums for a while
Posts: 220
Joined: Wed Dec 08, 2004 6:39 pm

Post by ghills »

I'm afraid I now have another - interesting - problem. On my route I have a thru station that continues on the mainline but also has a line to another line which joins up with the mainline again later. The "other" track is double track and has more than 4 signals on both lines. Therefore it doesn't matter whether you're running correct or wrong line, there are still signals protecting trains ahead and those on the mainline.

Anyway, whenever I have a train following another on the mainline, the train ahead gets held at the end of the loop until the following train has passed the beginning of the loop. It's as if the computer doesn't know which route the following train is going to take so has to wait and see. Even then, if the following train were to break off its path it would have 4 signals or more to pass and have to catch us up!!

I can't understand the sim's logic on this one. For those who know the line, it's like a train heads south past Cheshunt towards Liverpool St. via Tottenham Hale and when it's approaching Hackney Downs it has to wait for another train approaching Cheshunt to see if it takes the Seven Sisters route and can go thru red lights AND catch us up...???

Any ideas on this one will be very gratefully received :-)
Locked

Return to “[MSTS1] Route Building”