I have noticed this odd peculiarity with the Griswold signal that comes with the Cascadian: The stop banner in the middle does not rotate.
If I go off of memory a Griswold Rotating Banner signal will have the stop sign (if equipped) rotate via magnets/chains into the view of motorists. Was this meant to be like that on the Cascadian?
Re: Griswold signal does not rotate
Posted: Thu Jan 03, 2019 12:09 am
by ricksan
There's a YT video of a Griswold signal that shows the rotating-stop-sign action -- never seen that before! The one seen on Cascadian is based on GN standard sign #83, the literature for which specifies things like dimensions, materials of construction and colors, but is silent about sign rotation. It's possible said rotation could have been present by default.
Do I really have to mess with this?
Re: Griswold signal does not rotate
Posted: Thu Jan 03, 2019 2:17 am
by ErikGorbiHamilton
ricksan wrote:There's a YT video of a Griswold signal that shows the rotating-stop-sign action -- never seen that before! The one seen on Cascadian is based on GN standard sign #83, the literature for which specifies things like dimensions, materials of construction and colors, but is silent about sign rotation. It's possible said rotation could have been present by default.
Do I really have to mess with this?
I'd say it's your call
Re: Griswold signal does not rotate
Posted: Thu Jan 03, 2019 2:27 am
by BNSFdude
Ah yes, Griswold's were made in Minnesota, and were quite present on the scene here. These two in particular only recently had the signs removed:
Re: Griswold signal does not rotate
Posted: Thu Jan 03, 2019 11:07 am
by ricksan
Thanks to Eric and Anthony. As I said, I had no idea the Griswold signals worked this way.
Good news: I made the signal work in my sandbox route!
Currently, the stop signs are a fixed part of the crossing signals. As is also the case with a set of crossing gates, the animated stop signs must be separate child objects. Both the signals and the stop signs have to be individually adjusted to their final positions once the crossing gizmos are installed. That's also true if we simply overwrite existing crossing files -- inevitably everything will need to be realigned. Either way it affects the track data base (Tracks.bin) which is currently undergoing modification for the west-side add-on (Everett, etc.). There may be a way to update the east side (Cascadian) without affecting the west side, and vice versa, but we'll have to think about it and do some experimentation before we make a formal crossing signal upgrade available.