Identify which crossing not closed

Correct me if I'm wrong, but doesn't this message only come up when you try to set a route over a crossing which isn't closed? Therefore it should be pretty clear which crossing is the one in question, as I don't think there's any route on Exeter which goes over multiple manual crossings - even if there were (e.g. South Humberside, which has one or two routes like that), it would still be quite obvious where the issue is.

Thanks for correcting me on that point. I was confusing "Crossing not closed" with "Crossing blocked by road vehicle".

On checking the Wiki General messages page, I notice the latter is included but the former is not, so I've just added it.

These messages include the crossing name (between the angle brackets <>):
<crossing> barriers are down
<crossing>: train passed with crossing open
Crossing failure at <crossing>
Excessive delay to road users at <crossing>
Excessive delay without a train to road users at <crossing>
Train on green MWL at <crossing>*
Train on open AHB at <crossing>*
* No description of the meaning of this message in Wiki

These messages do not:
Crossing blocked by road vehicle
Crossing not closed


Even though I misunderstood the message, the original purpose of this thread was to request that the name of the crossing be included in the message, e.g., "<crossing> crossing blocked by road vehicle".

" said:

*Snip*

Again, in the case of "Crossing blocked by road vehicle" - the message is only generated when you click the crossing clear button. You know which crossing it is because it's the one you've just clicked.

"Crossing not closed" is not a default message, instead it's a custom one that Peter has coded into Exeter to infrom the user as to why they have been unable to set the route. As it's a custom message, not general, I've removed it from that page of the wiki as it has no place there (General messages being for standard, sim-generated messages)

" said:

" said:

*Snip*

Again, in the case of "Crossing blocked by road vehicle" - the message is only generated when you click the crossing clear button. You know which crossing it is because it's the one you've just clicked.

"Crossing not closed" is not a default message, instead it's a custom one that Peter has coded into Exeter to infrom the user as to why they have been unable to set the route. As it's a custom message, not general, I've removed it from that page of the wiki as it has no place there (General messages being for standard, sim-generated messages)

I've reverted that change on the Wiki, I agree from a developer to developer point of view that it is a custom message in the context you and I would think it is. However from an end user points of view it's used in more than one sim (I can think of three of the top of my head), and always has the same meaning.

Well, I had no idea this was a sim-specific message. However, if it occurs in at least three sims, I agree it should be made a general message.

Seems it's time for someone in authority to review the list of general messages (at least those applying to LCs) and winnow a few out, particularly as Loader code is taking over. Failing that, it seems only common sense that a sim manual should list any custom LC messages (haven't checked Exeter's but don't recall seeing this). As the number of sims grows steadily this will become harder to do.

On further reflection I can't see the need for any sim-specific messages; they should all be part of the core code as it's inevitable that some future sim will find a need for them. The only argument against this is that a list of Magna Carta proportions might slow SimSig down, but surely some judicious pruning would ensure a smaller list of universally applicable ones.

Documentation, documentation, documentation.

Failing that, it seems only common sense that a sim manual should list any custom LC messages (haven't checked Exeter's but don't recall seeing this).

This has all been brought to Peters attention, and is on his list of things to do to the sim.

" said:

This has all been brought to Peters attention, and is on his list of things to do to the sim.

Quite a bit to be done huh? I wonder what else is on that list other than, perhaps, the addition of the other LC at Paignton. I look forward to the new version when it emerges.

Dave

Wasn't the other one removed on purpose?

Is there a need to explain the obvious? I agree some messages contain jargon and should therefore be glossed, but "Crossing not closed" or "Crossing blocked by Road Vehicle" appearing just after you've tried to do something at a Level Crossing should be pretty obvious. Perhaps a little more observation required?

I'm not in the habit of nervously looking up at Messages each time I click the LWR (LoWeR) button at an LC to see if I made an error - I'm too busy scanning

which is why I started this thread - to ask that the crossing responsible be identified with the message

I'm not going to play a game of reversion cat and mouse, but I do feel very strongly that this is something for individual simulation manuals to mention. Certainly at the very least the re-removal of the Cambridge-specific pilotman working messages.

I should also explain that I don't have a lot of room above the View panel for Messages so am limited to the last 4. I'm not in the habit of nervously looking up at Messages each time I click the LWR (LoWeR) button at an LC to see if I made an error - I'm too busy scanning, so it's on to the next area of interest and I'll return when I hear the sound I associated with barriers being down. So understandably, if I've just lowered the barriers on 2 or 3 crossings and find I can't set a route or the CLR button isn't winking, it's time to sort out which one caused the problem.

By this time any error message such as Crossing not closed is likely to have been pushed off the list by subsequent messages, which is why I started this thread - to ask that the crossing responsible be identified with the message. The only message specific for LCs is Level crossing clear, to which I assigned a unique sound (very helpful). Crossing not closed and Crossing blocked by Road Vehicle must fall into the category of General Messages. If I assigned a sound to them it'd be like spending a night in the jungle.

Also worth noting that all the crossings that behave in that manner on Exeter are wrong anyway as you should be able to set a route over them. This has all been brought to Peters attention, and is on his list of things to do to the sim.

I notice Stephen Fulcher wrote in post #4:
Quote:

Also worth noting that all the crossings that behave in that manner on Exeter are wrong anyway as you should be able to set a route over them. This has all been brought to Peters attention, and is on his list of things to do to the sim.

As a single-screen player (for now), I was gratified to read this. Exeter due for an upgrade? Hmmm. I wonder if we could persuade Peter that all controlled main line signals in and out of Tiverton Junction can now be set to automatic working (blue roundel). That would leave more time to figure out solutions to exotic moves at Paignton, Fairwater and the like. ;)

As a single-screen player (for now), I was gratified to read this. Exeter due for an upgrade? Hmmm. I wonder if we could persuade Peter that all controlled main line signals in and out of Tiverton Junction can now be set to automatic working (blue roundel). That would leave more time to figure out solutions to exotic moves at Paignton, Fairwater and the like. ;)

If they don't have autos on the real panel, then it won't be put on the sim. It is after all a Simulation and not a game.