Complex Emit Train on Trigger

[Hayashi7]

I can't figure out if this is even possible, let alone how to do it. and I don't know how to write scripts. I want a portal to emit a specific train depending on which trigger was hit, and all trains coming from that portal will be automatically assigned a schedule. (Each train emitted gets the same schedule.) For example, if any train hits trigger A, the portal will emit train (existing consist) Y. If a train hits trigger B the portal will emit train Z. The reason for this is that I want to be able to choose which train is emitted next, rather than random or sequential. So when I'm ready for a grain train, I run over trigger A and when I'm ready for a coal train I hit trigger B. Or am I being totally whacked out here? Any help appreciated.

 

[itareus]

Have a look at these:

Quick Portal Manager v3,<kuid2:61392:5012:21>

Central Portal Control,<kuid2:117746:1013:7>
CPC: Emit Train,<kuid2:117746:1014:4>
CPC: Emit Train On Trigger,<kuid2:117746:1044:4>

I don't think they will do exactly as you want but you may find a way to do what you want.

 

[kkopchynski]

Hi,

I used to do something very similar or perhaps identical to what the OP is asking. It was quite a while ago on previous versions, so I don't remember much and I'll have to check next time I am in the game. This was before Quick Portal manager existed. I used the CPC items mentioned above. I got bored with exactly the same train with same driver coming out, though. Nowadays I pop into a small route in surveyor, make up the train I want, and then send it to the correct portal using Quick portal manager.

If you happen to own the previous Marias Pass full version, they have a session to run the aluminum plant that does pretty much as you ask.

Best of luck,
Kevin

 

[Hayashi7]

The problem is getting all desired trains to emit from just 1 portal, on demand. With CPC I have to use a different portal for each train. I'm sure there's a way to do it with a custom script, if I knew anything about scripting. I suspect that the script would need to be written for the specific route/portals/trains.

 

[stagecoach]

I always place a blank base board (or two) some distance away from the route, not attached. I place all my portals on this board which produce or consume. There is an arrival and exit portal which consumes a train and sends it to the portal on the route. All portals are set for the different trains needed. The trigger lets the train out of the creating portal and send it via the exit portal to the portal on the route.

 

[Paulsw2]

Doesn't the QuickDrive rule in TS12 enable you to place any consist from your list anywhere in the route whenever you want while in Driver? Perhaps not automated enough, though quite quick and easy to do?

Paul

 

[Dap]

Quick Portal Manager V3 will let you load untold number of consists as unscheduled for multiple portals on your route. You can schedule them in surveyor to be emitted at a specific time, or you can schedule them in Driver as you see the need. http://trainz.guynet.org/ you can find the well written manual on his website.

 

[celje]

... I want a portal to emit a specific train depending on which trigger was hit, and all trains coming from that portal will be automatically assigned a schedule. (Each train emitted gets the same schedule.) For example, if any train hits trigger A, the portal will emit train (existing consist) Y. If a train hits trigger B the portal will emit train Z. The reason for this is that I want to be able to choose which train is emitted next, rather than random or sequential. So when I'm ready for a grain train, I run over trigger A and when I'm ready for a coal train I hit trigger B. Or am I being totally whacked out here? Any help appreciated.

We have solution by using two rules, Central portal control (CPC) and CPC: Emit train on trigger. In CPC you set portals (you can repeat the same portal, they have a different index) and consist, driver and schedule, then in CPC: Emit train on trigger you put in Portal index and triggers.

But you must know, this two rules are not exact enough, in couple of times (1-2 hours) mistakes are shown and unpredictable consists will be emitting.

A little better is Portal manger
.
Only rule which is accurate (for now) is Quck portal manager V2/V3 but it use time for setting.

 

[Hayashi7]

Problem solved. What I came up with is not ideal; it's kind of a kludge but it works, and it doesn't use complex assets or scripts. My goal is:
1. Emit scheduled trains from portals under AI control which ultimately exit other portals.
2. Make up trains from local industry which travel under AI control to a portal for load/unload, then return to the yard.
3. Call specific trains at need. These consists replace ones that for whatever reason have derailed (and been deleted). I've found that the re-rail functions in Trainz are not reliable under all circumstances.
Solutions, in order:
1. Each end of the mainline has a "consume" portal and "produce" portal for AI scenery (eye candy) trains. Can't use 1 portal for both unless traffic density is extremely light; I haven't found a way to completely eliminate cornfield meets at or near the portal.
2. Never have a train return from the same portal unless you have only 1 train; trains must return from an alternate portal.
3. I've made up several consists of cars & locos used on my route; using Central Portal Control, a train is emitted on trigger from yet another portal & travels to the main yard. Any cars I don't want are sent along to an exit portal.
So, my route's mainline has a north & south "end", plus a branch line with a west end. Each end has 4 portals (AI in/off, local in/off), plus 1 more for emitting "extra" consists on demand. 13 standard portals plus CPC. I've discovered through testing that with high traffic densities I need to be very careful about placing track markers and direction markers, and path rules, to make sure every train stays on it's intended path. Stopping & waiting instead of taking a convenient double-ended siding, for example.

 

[stagecoach]

With your above set up you could reduce the portals on the actual route. At each end just have your consume and produce portals (6 portals). Creat baseboards somewhere away from your route (not attached to the main boards). Place all portals to produce your different concists (lets say 10 different consists, so 10 portals). Place a portal for each produce portal and one consume portal on the main route (4 portals). This becomes a yard area if needed, trains are produced and sent to the yard consume portals which returns the consist to to correct produce portal on the route. All consume portals on the route send trains to the yard produce portal. Once a train arrives you can have portals for load/unload and return or just exit. Having all portals on one or two baseboards makes it easier to watch what the portals are doing. The route portals might be named :- North In, North Out, South In, South Out, West In and West Out. The yard portals :- Yard North In, Yard South In, Yard West In and Yard Route Out. Set the yard in portal to retun at the correct portal on the route.