Question for the developers or testers... what's the logic with how switches behave?...
Scenario 1:
This has happened to me twice.... I've lined up a switch to have a eastbound take the siding, while a westbound continues on the main during the meet...

When the eastbound takes the siding, the switch at the east end is changing paths to accommodate it. That re-routes the westbound onto the siding, and you have a head-on collision.
I suspect it is because the switch at the west end is still lined up for the siding, which is forcing a logical routing over the siding.....
Scenario 2:
This has happened as well...
Eastbound entering a main, with the switches at both ends lined up for the main.... the lead engine gets partway into the switch, and then SNAP! the train is on the main, including all the cars which haven't crossed the siding.

This happens in MSTS as well.
Is there any reason why switches can't be programmed to act like a spring switch, and allow non-diverging traffic to pass thru regardless of how the switch is set?...
Scenario 1:
This has happened to me twice.... I've lined up a switch to have a eastbound take the siding, while a westbound continues on the main during the meet...

When the eastbound takes the siding, the switch at the east end is changing paths to accommodate it. That re-routes the westbound onto the siding, and you have a head-on collision.
I suspect it is because the switch at the west end is still lined up for the siding, which is forcing a logical routing over the siding.....
Scenario 2:
This has happened as well...
Eastbound entering a main, with the switches at both ends lined up for the main.... the lead engine gets partway into the switch, and then SNAP! the train is on the main, including all the cars which haven't crossed the siding.

This happens in MSTS as well.
Is there any reason why switches can't be programmed to act like a spring switch, and allow non-diverging traffic to pass thru regardless of how the switch is set?...





Comment