
Originally Posted by
wmuzeke
I took a deep dive into this issue and I think I have finally figured out what it is. The truck being undriveable was just a red herring. There is a bug in Open Rails that has to do with saving the game (F2) and resetting wait points. If you hit F2 before the AI traffic spawns or before it gets to the wait point, then the wait point reset works correctly. If you hit F2 after the AI traffic reaches the wait point, the wait point reset will not work. I have tested this many times with different routes and activities. I am using version 1.5.1. This only happens when you use wait times versus absolute wait until (HH:MM). There is an open bug on launchpad started in 2019 regarding this issue (#1848878 "AI train WP restart events don't work after save") that is marked as "in progress." I hope it can be fixed soon. Anyway, try running the Amt572 activity without saving and the truck and the rest of the AIs should start normally.