Message Areas - "Signals, signals, signals"

Train-Sim.Com Message Areas

"Signals, signals, signals"

Email this topic to a friend
Printer-friendly version of this topic
Bookmark this topic (Registered users only)
Previous Topic | Next Topic Conferences MSTS Route Design (Protected) Original message
goonybird (19 posts)
Jun-05-02, 02:43 PM (EDT) "Signals, signals, signals" Can any of you give me some info on the following attributes of signals (signal script and configuration files too)?a) What is the difference between the 'least restrictive' type of signal and the 'most restrictive' type? For example, would respectively specifying these types to two signals that respectively serve a pair of identically unidirectional tracks which merge into a single track ahead enable the developer/builder to assign which of the (initially a) pair of tracks has priority over its complement to proceed? While the types 'opposing' and 'this' are obvious to me, 'least restrictive' and 'most restrictive' types aren't.b) Is it possible to embellish the scripting for a given signal to include arguments that cover both (or singularly) JN_OBSTRUCTED and OCCUPIED block states **in addition** to the CLEAR block state? I've done this, but am not convinced if I have the scripting language correct; this embelishment(sp?) has seemingly prevented trains from being clipped from behind by trains coursing the other exit over swiches where the rear ends to the preceding trains dangle.I see alot of discussion on, for example, manual versus automatic switches; I sense there being little focus devoted to signals themselves. I can't shake this nagging feeling that Dispatcher does not (repeat: does not) behave arbitrarily when it comes to automatically granting trains travelling the same direction and approaching the same merging-/mergent-placed switch (as opposed to a diverging-/divergent-placed one) to proceed through the junction due to the respective distances and timings needed to travel by these very trains. Well, of course, the distances and timings are factors in the Dispatcher's decision-making, but with all the function operators, variables, etc., listed/defined in the tech doc for signal script files, I really suspect these listed functions are there to be (possibly) deployed in a route's signal script file, but I've yet to come across a script file that uses any of those crazy-looking functions/operators. I truly believe that controlling the behaviour of signals does lie with the route builder/developer by the instructions we designate in the script and configuration files; but my knowledge base of how to embellish either type of file -- particulary the script type -- is so minimal.Whoa, I have even more questions about this central-nervous system (signals) of Train Simulator's but need to approach/ask questions about them just a few at a time. (All these far-reaching ideas yet I create no checklist for them all!) Alert Edit | Reply | Reply With Quote | Top
Table of Contents

Subject Author Message Date ID RE: Signals, signals, signals SP9800 Jun-05-02 1 RE: Signals, signals, signals goonybird Jun-06-02 2 RE: Signals, signals, signals sniper297 Jun-06-02 3 RE: Signals, signals, signals goonybird Jun-06-02 5 RE: Signals, signals, signals SP9800 Jun-06-02 4 RE: Signals, signals, signals goonybird Jun-06-02 6

Lobby | Topics | Previous Topic | Next Topic
Messages in this topic
SP9800 (287 posts)
Jun-05-02, 11:22 PM (EDT) 1. "RE: Signals, signals, signals" >a) What is the difference
>between the 'least restrictive' type
>of signal and the 'most
>restrictive' type?For example, you may have a signal with three heads. Assume all three heads have their own scripts. Also assume that, for whatever reason, one head is set at SIGASP_STOP, another at SIGASP_APPROACH_1, and the third at SIGASP_CLEAR_2. The least restrictive indication would be the SIGASP_CLEAR_2. The most restrictive indication would be the SIGASP_STOP.I hope this clears it up a bit. I just wish there was a better way to communicate between signal heads. Remove | Alert Edit | Reply | Reply With Quote | Top
goonybird (19 posts)
Jun-06-02, 11:14 AM (EDT) 2. "RE: Signals, signals, signals" Aha, your response has helped me a lot, thank you. I'll figure it out from there.Would you mind sharing with me what you find inadequate, if I may put it this way, about the ability of signal heads in MSTS to communicate with each other? Are there other kinds of pitfalls route builders should take into account when using signals? I find the whole signalling thing really confusing, and I'm not convinced that I've been focussing on/considering the right areas of signal attributes....Cheers! Remove | Alert Edit | Reply | Reply With Quote | Top
sniper297 (2370 posts)
Jun-06-02, 11:34 AM (EDT) 3. "RE: Signals, signals, signals" Bob Seiderer did a tutorial on signals, in the file library under misc., I think. Here's some of the old threads, the documentation is obscure at best.http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=1572&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=1740&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=2386&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=2444&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=2595&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=2670&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=3909&forum=DCForumID6&archive=yes
http://www.train-sim.com/cgi/dcforum/dcboard.cgi?az=show_thread&om=3073&forum=DCForumID6&archive=yes Remove | Alert Edit | Reply | Reply With Quote | Top
goonybird (19 posts)
Jun-06-02, 01:31 PM (EDT) 5. "RE: Signals, signals, signals" Right on! Many thanks for guiding me to some resource tools.Cheers Remove | Alert Edit | Reply | Reply With Quote | Top
SP9800 (287 posts)
Jun-06-02, 01:09 PM (EDT) 4. "RE: Signals, signals, signals" LAST EDITED ON Jun-06-02 AT 01:10 PM (EDT)Well, in the scripts I am attempting to write, I use a checkbox and APPROACH_3 to display Approach Diverging. I have it set up such that if one signal head is APPROACH_3, *all* the signal heads should be APPROACH_3. I had to use the least-restrictive thingy to do that. I think it would be a whole lot easier (given that you are careful with calling the other heads) if you could just have the script look at what each head individually is displaying, rather than getting the most- or least-restrictive indication of the whole signal. Also, I think it would be helpful to be able to do this same sort of communication between signals.Actually, while writing this, I thought of something, though it probably won't work. Remove | Alert Edit | Reply | Reply With Quote | Top
goonybird (19 posts)
Jun-06-02, 01:38 PM (EDT) 6. "RE: Signals, signals, signals" Thank you. I'm curious what you thought of....I'll check out the resources to the threads that Sniper297 suggested I look into before I ask any more questions.Cheers Remove | Alert Edit | Reply | Reply With Quote | Top

Lock | Archive | Remove

Lobby | Topics | Previous Topic | Next Topic