JonMyrlennBailey
Well-known member
Yesterday, I discovered how to generate AI trains from the portals and now I am experimenting with them on my route. There are seven portals on my Mojave Sub route as follows:
at the southeast end there are:
Palmdale
Barstow
Sealres Turn
at the northwest end there are:
ATSF to Fresno
ATSF from Fresno
SP to Fresno
SP from Fresno
I set up 5 portal trains set to be emitted hourly and immediately when session starts.
3 trains are set to come from the east end to various west end portals (a passenger, a short freight, a medium-length freight)
2 trains are set up to come from the west from various west end portals (a passenger, a long heavy freight)
The Mojave Sub has a double-track system in some parts and a single-track system in other parts: mainly over the Tehachapi Mountains with some intermittent sections of double track. My concern is there might be conflicts between AI trains moving in opposite directions at junctions where tracks merge from double to single. Trains might get in each other's way. There is also a feature to assign priority numbers to AI trains, 1, 2 and 3.
My questions are:
Should the longer heavier trains get the higher priority numbers (1)?
Should medium trains get a 2?
Should short, light passenger trains get a 3?
What about setting priorities when making schedules?
Should the priority be the first item on the drive schedule line?
Central Portal Control lets me assign priority numbers to each created train.
What about my timing for portal release of trains. Is it BAD to have trains
released from all the portals on the entire route at the SAME time or should I stagger portal
release times considerably? Should portal generation of trains be sequential or random?
Is hourly too frequent to release trains on the Mojave Sub?
What I want portal-produced AI trains to do is continuously REPEAT their respective assigned schedules: I want the same portal trains to re-emerge from their original portals after they complete their drive schedules over and over again. When configuring schedules, I have "Enable Repeat" as the last command issued to drivers of portal-generated A1 trains (if this even necessary).
at the southeast end there are:
Palmdale
Barstow
Sealres Turn
at the northwest end there are:
ATSF to Fresno
ATSF from Fresno
SP to Fresno
SP from Fresno
I set up 5 portal trains set to be emitted hourly and immediately when session starts.
3 trains are set to come from the east end to various west end portals (a passenger, a short freight, a medium-length freight)
2 trains are set up to come from the west from various west end portals (a passenger, a long heavy freight)
The Mojave Sub has a double-track system in some parts and a single-track system in other parts: mainly over the Tehachapi Mountains with some intermittent sections of double track. My concern is there might be conflicts between AI trains moving in opposite directions at junctions where tracks merge from double to single. Trains might get in each other's way. There is also a feature to assign priority numbers to AI trains, 1, 2 and 3.
My questions are:
Should the longer heavier trains get the higher priority numbers (1)?
Should medium trains get a 2?
Should short, light passenger trains get a 3?
What about setting priorities when making schedules?
Should the priority be the first item on the drive schedule line?
Central Portal Control lets me assign priority numbers to each created train.
What about my timing for portal release of trains. Is it BAD to have trains
released from all the portals on the entire route at the SAME time or should I stagger portal
release times considerably? Should portal generation of trains be sequential or random?
Is hourly too frequent to release trains on the Mojave Sub?
What I want portal-produced AI trains to do is continuously REPEAT their respective assigned schedules: I want the same portal trains to re-emerge from their original portals after they complete their drive schedules over and over again. When configuring schedules, I have "Enable Repeat" as the last command issued to drivers of portal-generated A1 trains (if this even necessary).
Last edited: