The need for this trigger is coming from a thread started by Sniper297. I decided to open this thread specific for the trigger so it won't get buried somewhere in Sniper's stuff. Please take a look to more details in his thread at http://forums.auran.com/trainz/showthread.php?97264-AI-traffic-train-performance-revisited.
I think I have a good understanding of what is required and I came out with these requirements/specs.
I think I have a good understanding of what is required and I came out with these requirements/specs.
Specs to include in version 1:
- A new trigger will be created named PortalTrigger.
- This trigger will execute one of two actions, either turn ON or turn OFF spawning trainz at some selected portals.
- The trigger will not be attached to a particular portal control. However, for this to work a portal control must be able to understand the requests sent from the trigger. As a result, there will be a new portal control perhaps a clone one out of an existing portal control.
- The trigger will be activated by a specific train which will be selected by the player from a list of available trainz in Surveyor.
- The configuration of the trigger in Surveyor will allow the player
- to set the trigger’s function (turn on or turn off spawning),
- to select the player’s train,
- to add any available portal to the list of controlled portals,
- to remove any of the portals previously selected.
Specs to include in version 2:
- When session starts, all portals added to the trigger will be disabled (not spawning trainz). As the player train enters the turn-on-trigger all portals belonging to the trigger will be enabled (start spawning trainz at whatever sequence was scheduled in the portal control). As the player train moves on and eventually hits the turn-off-trigger all portals belonging to the trigger will be disabled.
- The trigger will be activated by either of two options, by any train or by any train out of a list of selected trainz. Note that choosing the 2[SUP]nd[/SUP] option and selected only one train is the same as selecting a train in version 1.
- The trigger will change color in Surveyor depending on whether the trigger is set to turn ON or turn OFF spawning. This will help greatly in Surveyor see at a glance what each trigger’s action will be in Driver.
- I think this is a doable solution. I estimate that the coding of the trigger and building its model in Blender can be done in 1 week (spare time). The modified portal control may be CPC since it is the one I am familiar with. The problem is whether we get permission to make it public. The actual code changes in the control may not be too many, I hope.
Feedback is very important at this time. Please post your comments/changes/suggestions before the implementation begins.
Cheers,
--José