What would be nice is a trigger that will only work in one derection..it could be set up like the track marks..this way when a train passes over it in the same drection it would trigger BUT if a train passed over it in the oppeset drection it will not..it would be used to set up lights on a single line ..
NEW Trigger..
- Thread starter mrmom
- Start date
Can be done
As far as I am aware the crossing triggers by Boat assets can be set to work either one or both directions.
Angela
As far as I am aware the crossing triggers by Boat assets can be set to work either one or both directions.
Angela
can i find this trigger on the DLS???
Single trigger can't discern direction
Had a look at Boat's ASB Crossover Trigger <kuid:76656:70002>. This is designed to work with Boat's Active Signal Box kit and would not easily be useful as a stand-alone trigger. In any case, my reading of the instructions indicates that the trigger is not direction sensitive. It is the order in which a pair of triggers are traversed that results in different actions by the ASB controller in response to the same trigger.
Triggers are inherently direction insensitive. A message is sent went a consist enters, from any direction, its trigger area which is described by a circle's radius. Another message may be sent when the consist leaves the trigger area. To have Session Rules that are applied selectively in accord with the direction a consist is moving along a track - as implied above - requires (a) a pair of triggers spaced along the track, and (b) Rules that respond to the order in which the trigger pairs are triggered.
Had a look at Boat's ASB Crossover Trigger <kuid:76656:70002>. This is designed to work with Boat's Active Signal Box kit and would not easily be useful as a stand-alone trigger. In any case, my reading of the instructions indicates that the trigger is not direction sensitive. It is the order in which a pair of triggers are traversed that results in different actions by the ASB controller in response to the same trigger.
Triggers are inherently direction insensitive. A message is sent went a consist enters, from any direction, its trigger area which is described by a circle's radius. Another message may be sent when the consist leaves the trigger area. To have Session Rules that are applied selectively in accord with the direction a consist is moving along a track - as implied above - requires (a) a pair of triggers spaced along the track, and (b) Rules that respond to the order in which the trigger pairs are triggered.
Trigger Check
Hi Mrmom
Not sure if this will work for you but I have setup a couple of triggers to change the camera view when a train enters a tunnel (I set this for one particular train otherwise I jump in and out of the cab for no reason when other trains enter the trigger!)
The first shot here shows the trigger layout.
Uploaded with ImageShack.us
The second shows the session setup - the indented trigger check and set camera rule is the important part.
Uploaded with ImageShack.us
This basically sets up an If.. then type statement. For the above arrangement it means that if a train enters TunnelNth1 trigger then triggers TunnelNth2 trigger then change the camera viewpoint.
I got this idea from someone on the forum but can't remember who now, but thanks.
Hi Mrmom
Not sure if this will work for you but I have setup a couple of triggers to change the camera view when a train enters a tunnel (I set this for one particular train otherwise I jump in and out of the cab for no reason when other trains enter the trigger!)
The first shot here shows the trigger layout.
Uploaded with ImageShack.us
The second shows the session setup - the indented trigger check and set camera rule is the important part.
Uploaded with ImageShack.us
This basically sets up an If.. then type statement. For the above arrangement it means that if a train enters TunnelNth1 trigger then triggers TunnelNth2 trigger then change the camera viewpoint.
I got this idea from someone on the forum but can't remember who now, but thanks.
Triggers...one way..>
This is what Im trying to do..My south bound train leaves the yard and passes over a trigger (a) which will change a light (L1) to red stopping a north bound train so the south bound has the rightaway..once the southbound reaches the trigger (b) at the passing track it releases the northbound sending it on its merry way..BUT when the It reaches the yard (the north bound) it triggers (a) so the light (L1) changes to red again and there is no way to change it back to normal state again..Now if trigger (a) was a one way trigger lets say pointing south the north bound trains would not set the trigger...and in turn the light (L1) would stay in a normal state until another train was headed south...Unless I have been missing somthing when I set up my triggers this could be a nice item to have...
This is what Im trying to do..My south bound train leaves the yard and passes over a trigger (a) which will change a light (L1) to red stopping a north bound train so the south bound has the rightaway..once the southbound reaches the trigger (b) at the passing track it releases the northbound sending it on its merry way..BUT when the It reaches the yard (the north bound) it triggers (a) so the light (L1) changes to red again and there is no way to change it back to normal state again..Now if trigger (a) was a one way trigger lets say pointing south the north bound trains would not set the trigger...and in turn the light (L1) would stay in a normal state until another train was headed south...Unless I have been missing somthing when I set up my triggers this could be a nice item to have...
New Check Trackside Rule
Hi all - I have written a modified version of MiZi's Check Trackside Rule which I am currently testing.
I still need to get in touch with Mizi to advise him about hijacking his rule but with luck it should soon be ready for beta testing.
It needs two sources of triggering information (called targets) to determine the train direction but can also work non-directionally.
This rule eliminates the need for multiple child rules.
Features:
Can use a Trackmark, Trigger or Junction as a trigger source.
Triggering can be on Enter, Stopped at or Leaving a target.
Supports Ordered Lists and can run repeatedly or just once.
You can select a range of vehicles to trigger the rule as per the original.
Diagnostic messages can be controlled within the rule.
Anybody interested in beta testing this?
I only have a dial-up ISP so am not on line all the time.
Regards - Trevor
Hi all - I have written a modified version of MiZi's Check Trackside Rule which I am currently testing.
I still need to get in touch with Mizi to advise him about hijacking his rule but with luck it should soon be ready for beta testing.
It needs two sources of triggering information (called targets) to determine the train direction but can also work non-directionally.
This rule eliminates the need for multiple child rules.
Features:
Can use a Trackmark, Trigger or Junction as a trigger source.
Triggering can be on Enter, Stopped at or Leaving a target.
Supports Ordered Lists and can run repeatedly or just once.
You can select a range of vehicles to trigger the rule as per the original.
Diagnostic messages can be controlled within the rule.
Anybody interested in beta testing this?
I only have a dial-up ISP so am not on line all the time.
Regards - Trevor
mrmom,
Bloodnok has a direction trigger for use in his sound horn kuids. He also has one that is bi-directional. They are:
Sound Horn BiDirectional,<kuid2:60850:23112:4> and Sound Horn,<kuid2:60850:23113:4>
I've tried them in TS2010 and they work. They only work in AI mode, however.
Bob
Bloodnok has a direction trigger for use in his sound horn kuids. He also has one that is bi-directional. They are:
Sound Horn BiDirectional,<kuid2:60850:23112:4> and Sound Horn,<kuid2:60850:23113:4>
I've tried them in TS2010 and they work. They only work in AI mode, however.
Bob
Humble pie
After looking at the script for Sound Horn,<kuid2:60850:23113:4>, I discover I was in error to claim that an object in the trigger class - such as the Sound Horn sign - cannot be direction sensitive. The script requests the approaching train that has entered the Sound Horn's trigger area to perform a forward TrackSearch and determine, once the Sound Horn sign is found, whether it is approaching from the sign's 'Face' side or 'rear' side.
For mrmom's purpose, the script would need to be modified to control a light rather than sound a horn. A user interface to select the light that is to be controlled would also need to be developed.
After looking at the script for Sound Horn,<kuid2:60850:23113:4>, I discover I was in error to claim that an object in the trigger class - such as the Sound Horn sign - cannot be direction sensitive. The script requests the approaching train that has entered the Sound Horn's trigger area to perform a forward TrackSearch and determine, once the Sound Horn sign is found, whether it is approaching from the sign's 'Face' side or 'rear' side.
For mrmom's purpose, the script would need to be modified to control a light rather than sound a horn. A user interface to select the light that is to be controlled would also need to be developed.