Closed Reosoul closed 1 year ago
Unless you skipped initialization or manually changed globals there's no way for global.ConnectedSurfaces
to ever be nil.
Downgrade to LTN 1.18.0 will force another initialization.
Alternatively using /c remote.call("logistic-train-network", "clear_all_surface_connections")
from console will reset that global too.
Thank you so much, using the command fixed it! Not sure what initial cause would have been
Playing with Space Exploration and LTN. Don't see others having this issue..
Created a requester, provider and depot set up in space using space trains. As soon as I enable a request, the following error occurs. Same setup is used on Navis without issue.