by Widewanderer » Thu Apr 07, 2016 3:13 am
Hello Robert,
How about turning this all about, and consider using Mark Brinton-scripted signals throughout? Or, indeed, signals powered by AndiS's new scripts? I, for one, find the habit of signals passed in the reverse direction clearing automatically behind a train (as is the case with Kuju Default-scripted signals and the UK Pro colour light set) most unsettling to see, and I avoid the use of these scripts in routes I am editing/developing myself. Defaulting to "on" prevents the signals clearing automatically when passed in a reverse direction - as featured in Mark Brinton and AndiS powered models. Be aware, however, that Mark Brinton's scripts will not allow a signal to clear if a train actually reverses until that train actually begins moving fractionally towards the signal - a trade off. AndiS handles this slightly differently, providing what he calls "movement predictors", a range of track-linked tools which can be placed at the scenario level, to control how signals behave in various situations. The two scripting systems are not compatible with one another, so a decision needs to be made regarding which to use, right from the outset.
John used default Kuju scripts (with a few modifications/enhancements from AndiS) for his very excellent models, but the said Kuju-based scripts still leave the problem of signals clearing automatically when passed in reverse. To that end, I had a go at adapting John's models to work with Mark's scripts - and it all worked, very easily. It's merely a matter of editing the blueprints for each signal model one wishes to use, changing the reference to the script to be used, of course, and altering the child names to reflect the naming convention Mark has used in his code. That's it.
For my own amusement, I now have a set of John's BR(WR) signals powered by Mark's scripts, and my copy of the Falmouth Branch signalled throughout with these models. I am much happier with the "feel" I now get when driving along this pretty little route - now that the rather ghastly "default" signals are gone. The next move from me for this route will be to try and get AndiS's scripts working with these signals - and again, it looks as if it should be quite straightforward, just a matter of some good old-fashioned leg work and time, producing appropriate "front-end" lua scripts for each model. The format of these little scripts is very simple - AndiS has already done all the really heavy lifting in the "back-end" scripts which are hidden away!
To produce the new set of Yelland/Brinton BR(WR) boards, I cloned the GeoPcDx and bin files into my own developer folder ("Widewanderer"), so as to be able to leave John's originals untouched by my potentially dodgey experimentation! Fortunately, it all worked out. If John and Mark are both in agreement, I would be more than happy to share my findings, but ultimately, that would have to be their call...
Robert, your South Devon route looks lovely. Good luck with your decisions about signalling it, and if I can help further, do let me know.
Best wishes,
Rob Saul Junction, Glos.