I have 4 dropoff stations for uranium ore. Those are the only stations with messages from the logs like "[LTN] Requester station uranium dropoff not available in network 0x1" That message means LTN doesn't see it as valid station for creating deliveries. If it's an requester like the name...

For performance it might matter, depending on how get_merged_signals() is implemented.
My guess is that it's not even measurable.

My BP mostly use green for reading and red for sending to keep things consistent and easier to find errors.

LTN receives and sends signals on both wires.

In dependency view "Last Updated" is either wrong or misleading.
It shows 4 hours for mods that havn't been updated in years.

In case this shows when dependencies where last checked it should be renamed to "Last dependency check".

I was hoping the author would see this and give me permission. If not, I can start from the combinator instead. More to learn that way. Firstly, a public forum is the worst channel to ask for permissions. Secondly, reading through your design proposal I'd still decline. But when a product is badly ...

Enabling circuit conditions globally has no effect on stations that don't make use of them. The only requirement is for a single wire to connect to every station, can be just an isolated pole with a wire between it and station. Otherwise trains will try to read from a not existing circuit network an...

Enable "Schedule circuit conditions" and build whatever logic you want for keeping trains locked in a station or force them out.

Working as intended.

Depot Priority is used for selecting available trains.
For returning to depots trains just use base game train pathing to a depot name.

Implementation wise the rocket would itself have a hidden train too because LTN tracks deliveries by train IDs. But you have one train on the planet that visits the provider. Then I need another train in space that finishes the delivery in orbit. Sourcing that train from LTN is the issue. I don't w...

Correct me if I read it wrong. You want to have LTN manage a delivery between surfaces where the train is sent along with the cargo in a rocket. Instead of forcing LTN to handle requests between surfaces I'd break it into one request per surface. Have a transmitter relay the required material to LTN...

With a system with that much inherent latency the best way would be:
1) count items entering the system
2) subtract items leaving for production
3) send current counter to LTN

You could also just filter at unloading, remove that filter buffer warehouse and send the main storage to LTN.

FritzHugo3 wrote: ↑

Mon Oct 30, 2023 6:54 pm

Is there a technical reson or why ltn dont respect that or why depots ignore the signals?

Depots work better by pathing to nearest name rather than using temp stops.
Doing so makes it far too easy to end up with same depot names with different train length limitations.

Use Network ID and train length to filter trains. Encoded Position is read only for smart loading/unloading. Position signals are direction dependent, while trains only have a concept of front and back during travel. e.g. <L-CC-<L-L> can't be distinguished from <L-L>-CC-L> until the train starts mov...

LTN is the wrong subforum.

Mods can't even touch train pathfinder (That's why LTN uses temp stops).

Depots use name based pathing like vanilla trains.
Provider/Requester use temporary stops on top of the actual stop to path by stop.unit_id.
There are some configurations where trains may not pick the stop under the temp stop after reaching it, e.g. disabling the stop or setting vanilla train limits.

That does not adress the main edge case I am experiencing: Station A requests 1000 of X. Station B(problem station) contains 3 of X. Train with 4 cargo wagons is dispatched to Station B to pick up 3 of X. Staton B recieves 2 more of X from the factory. Second train with 4 cargo wagons is dispatched...

Just report to LTN what's actually available.
If your station tells LTN it has items that it doesn't then your setup is wrong.

The whole point of LTN is to combine requests.
If you don't want that use Providers and/or Requesters dedicated to one type of freight.

It's possible by including a combinator set to your preferred settings in the blueprint for your LTN stations.