Hi all,
I have another request in my signal creation saga. I got the Bournemouth West (three home arms + co-acting arm + route indicator) working my original way (i.e. classing the indicator as a co-acting arm and specifying the right animations) without a hitch, so onto the next challenge:
I'm trying to make this signal, which is composed of two dolls, one with a home + distant arrangement and one with a single distant arm. These correspond to the next signal which is a standard junction signal with two home arms.
And below is the code that I've set up for it, minus the sound component:
require "Assets/AndiS/FPSignals/scripts/FP Universal Semaphore.out"
function Initialise ()
DefaultInitialise() -- no need to give the route count here
gArmTable[1][ARM_HOME][SEM_CHILD_NAME] = "ARM_HOME1"
gArmTable[1][ARM_HOME][SEM_PROCEED_ANIM] = "Clear01"
gArmTable[1][ARM_HOME][SEM_BLOCKED_ANIM] = "Stop01"
gArmTable[1][ARM_DISTANT][SEM_CHILD_NAME] = "ARM_DIST1"
gArmTable[1][ARM_DISTANT][SEM_PROCEED_ANIM] = "Clear01"
gArmTable[1][ARM_DISTANT][SEM_BLOCKED_ANIM] = "Stop01"
gArmTable[1][ARM_DISTANT][SEM_CHILD_NAME] = "ARM_DIST2"
gArmTable[1][ARM_DISTANT][SEM_PROCEED_ANIM] = "Clear01"
gArmTable[1][ARM_DISTANT][SEM_BLOCKED_ANIM] = "Stop01"
end
This uses the philosophy of ARM_DISTx corresponding to ARM_HOMEx and ARM_DISTy corresponding to ARM_HOMEy.
I've tried swapping the second distant arm over to a separate doll by numbering it with a 2 next to gArmTable instead of a 1 but that did not seem to work, and I can't see how requiring the distant base script would work.
Any ideas?