I am using searchlight signals. When I start a session all signals remain red. I assumed that one of the first things would be to set all signals to a state appropriate to the session's presented initial conditions. The train then advances toward the signal and quickly assumes its slow crawl (2mph) toward the signal eventually stopping. ALL the signals on the route exhibit this anomaly. Using the E. Kentucky route (EK3) with one active engine/train. Perhaps it has some characteristic that renders it incompatible with the new program. Deleting all signals on the route allows the engine to proceed normally to its destination.:wave: Ticket:#UQS-670-72968
Last edited: