JonMyrlennBailey
Active member
it is virtually impossible to always avoid collisions between trains at a crossing no matter how you adjust the invisible signals, the trigger position or the trigger ranges. Most of the time vehicles will cross safely. Once in a blue moon, they will inevitably "mix paint" or "blood" at the TMS crossing.
This is especially true when you have a slow-moving "train" as a AI-controlled horse carriage (8 mph max, 4 mph under yellow) vs an oncoming F7 silver streak, 25 mph or faster. The AI driver of the horses may slow down even if the signal turns red as he is passing it and end up ghosting through the crossing fast train. At the crossing, the speed limit for my horses on their route is 10 mph, max. I try to get them across the visible tracks with very DANGEROUS realistic-looking-and-speeding railroad trains as expeditiously as possible. What are the rules for horse-drawn vehicles at railroad crossings in the real world? Horses pulling wagons are much slower than automobiles to accelerate. Of course, the horses driven by the guys in cowboy hats must always yield to any oncoming "railroad" trains or get turned into ground dog food or glue. That is the natural and sensible rule to have.
Obviously, this Trainz programming logic would not work in a world where PHYSICAL autonomous vehicles at railroad crossings are operated as expensive collision damage and loss of lives would otherwise be certain.
How would an autonomously-driven car safely negotiate railroad crossings in the real world? There has to be a point of no return once the car crosses the red light: it can't hesitate or stop dead on the tracks with a train coming. Once it decides to GO it must hurry on through without looking back. It is like an airplane that barrels down the runway. The aircraft must either lift off or abort take-off depending how much runway is left. It is all math and physics.
Yes, good software controlling automated transportation must be fast and decisive. Split second life-or-death decisions must be made. There is no room for error or gray area. It has to be all or nothing when negotiating a crossing. It is a GO or NO GO proposition. Depending upon the speed and distance of traffic from the crossing involved, can the vehicle approaching the crossing stop safely in time if there is an oncoming train nearby? Would the moving vehicle close to the crossing in question do better to just gun it?
It is like the game Frogger. In my case it is "Horser". Can the ponies beat the choo-choo at the crossing?
This is especially true when you have a slow-moving "train" as a AI-controlled horse carriage (8 mph max, 4 mph under yellow) vs an oncoming F7 silver streak, 25 mph or faster. The AI driver of the horses may slow down even if the signal turns red as he is passing it and end up ghosting through the crossing fast train. At the crossing, the speed limit for my horses on their route is 10 mph, max. I try to get them across the visible tracks with very DANGEROUS realistic-looking-and-speeding railroad trains as expeditiously as possible. What are the rules for horse-drawn vehicles at railroad crossings in the real world? Horses pulling wagons are much slower than automobiles to accelerate. Of course, the horses driven by the guys in cowboy hats must always yield to any oncoming "railroad" trains or get turned into ground dog food or glue. That is the natural and sensible rule to have.
Obviously, this Trainz programming logic would not work in a world where PHYSICAL autonomous vehicles at railroad crossings are operated as expensive collision damage and loss of lives would otherwise be certain.
How would an autonomously-driven car safely negotiate railroad crossings in the real world? There has to be a point of no return once the car crosses the red light: it can't hesitate or stop dead on the tracks with a train coming. Once it decides to GO it must hurry on through without looking back. It is like an airplane that barrels down the runway. The aircraft must either lift off or abort take-off depending how much runway is left. It is all math and physics.
Yes, good software controlling automated transportation must be fast and decisive. Split second life-or-death decisions must be made. There is no room for error or gray area. It has to be all or nothing when negotiating a crossing. It is a GO or NO GO proposition. Depending upon the speed and distance of traffic from the crossing involved, can the vehicle approaching the crossing stop safely in time if there is an oncoming train nearby? Would the moving vehicle close to the crossing in question do better to just gun it?
It is like the game Frogger. In my case it is "Horser". Can the ponies beat the choo-choo at the crossing?
Last edited: