[2.0.55] Incorrect Train Icon Showing (No Path instead of Waiting for Destination (Zzz))
Posted: Wed Jun 25, 2025 2:46 am
After setting up a raised rail system on Fulgora, I built the two destination train stops ("Scrap Input" & "Scrap Output"), and set a train to run between the two of them. I have some circuit logic that sets the train limit at each station according to need and availability respectivly, and have many hundreds of hours using these circuits. If the Input station doesn't have enough scrap, the station limit will increase by 1 or 2 (need depending), and similar logic is set for the Output station.
When either the Input or Output station are satisfied and therefore have their train limits set to 0, and a train wants to go there, it SHOULD display the Zzz "Waiting" symbol. Instead, the train displays and gives out the global (universal?) symbol signifying the "No Path" error. As soon as the destination station opens up, the train loses the 'No Path' error and proceeds as normal.
TL;DR The train displays the 'No Path' error icon when it should be showing the "Zzz" Waiting signal. There is nothing wrong with the path. Once the station is available, the train functions as normal. Pictures attached. (Pictures shows closest station only, but there are other stations in the network that give the same problem, as indicated by the multiple No Path signals)
When either the Input or Output station are satisfied and therefore have their train limits set to 0, and a train wants to go there, it SHOULD display the Zzz "Waiting" symbol. Instead, the train displays and gives out the global (universal?) symbol signifying the "No Path" error. As soon as the destination station opens up, the train loses the 'No Path' error and proceeds as normal.
TL;DR The train displays the 'No Path' error icon when it should be showing the "Zzz" Waiting signal. There is nothing wrong with the path. Once the station is available, the train functions as normal. Pictures attached. (Pictures shows closest station only, but there are other stations in the network that give the same problem, as indicated by the multiple No Path signals)