well, other OS like MacOS and Linux have this functionality built-in. Complain to Microsoft? Why not complain to both? Most other game developers realized that shortcoming of Windows and added an option to mute on loosing focus into their game. Run WSL2 on Windows with the KDE environment and final...

Looking through stop creation I remember now.
LTN stops are always created with send to train and read from train enabled to prevent having to stamp over every stop when enabling "Schedule circuit conditions" late into a game.

Sry for late replay, I hardly check the Forums these days. Can you explain what belt latency is? I measured my longest belt with items on it. Even 355 x 4 belts, would be about ~ 1200 items. One full load is 160 stacks, so that would be 32000 chips. I don't see how LTN could request a full load and ...

Can't reproduce.
On Factorio 1.1.57 and LTN 1.16.7 copy/cut and paste, saved blueprint, stamping over existing stops all works fine for me.

Check if you have a mod altering blueprint functionality or train stops installed.

Depots ignore ALL signals except Stop is Depot and Depot Priority. Depot: (ignores Requester & Provider signals) https://raw.githubusercontent.com/Yousei9/Factorio-LogisticTrainNetwork/master/graphics/icons/depot.png Stop is Depot - flags this stop as depot (default=0 false) https://raw.githubus...

You can make an exact replica of functionality, as long as you write your own code. You just need a new name and new graphics for the new mod. The mod has a license for it , not a patent for the idea of making trains into logistics robots. The "internal structure" is going to differ at so...

What I see is this: LTN for bulk transports, move more or less material from A to B on a regular base: not a good idea. You can have much fun in doing this with the enhanced trains in 1.1 very well. Much more efficient, much faster (CPU & total time), much less possible errors. LTN for one-time...

Sorry, but I don't feel like letting go of a project I spent so many years on. However LTN would require yet another rewrite from scratch to make use of all the current base features. Even the premise of improving performance by cutting down the total number of trains seems to be wrong. I've heard c...

I do feed the warehouses, and the chests unloading both to the warehouse (Through the green signal in my screenshot). I've given up. LTN occasionally overrequests and gets too much. IDK if it's from the time that some of the stuff is on the belt before it reloads and the signal gets readded back in...

Dear all, Please move to 500 lane tests. Its more accurate. See my analysis https://forums.factorio.com/viewtopic.php?f=193&t=101648 probably the mod "EditorExtensions" strongly affects UPS Removal of editor extensions would make testing more painful, I'm look into that now. You can t...

Super old thread but still comes up in google. To prevent non-empty trains from dispatching: Wire the Depot train stop to a Rail signal in front of it. If train not empty, then disable the rail signal. Can also add a speaker for an alert too. Works for both standard and fluid cargo. A much cleaner ...

Sounds to me like you don't feed the warehouse content to LTN input. What's the station name of your warehouse so I can search the log? Normally Request Threshold is set to the size of a single train, to ensure you only schedule a train when it has space to unload. (Stack Request Threshold is even m...

Merged into existing thread. I'm still not going to reinvent train handling just to fix output not matching schedule when inserters holding items in their hands insert items before trains properly enter a stop. The simple solution is to use locked slot signal so inserters are not left stuck with it...

There's a mod for that: https://mods.factorio.com/mod/UI_Hotkeys

Turn off every single UI element individually or all at once.

LTN reserves deliveries from providers until a train leaves the provider.
It makes no difference if the item is not physically in storage or reserved by a delivery, either way there's not enough supply.

Not a bug with LTN itself
Moving to LTN Manager Subforum

Why did you change everything that made the API site fast and easy to read? Headers in bright yellow with blurry font (especially in bold) and normal white text on light grey makes my eyes hurt. Search should filter functions containing the search text. For example what is it trying to tell me here ...

Temp stops are a workaround for targeting train stops by unit_number rather than ambiguous name.
Instead of trying to fix the workaround, I'd rather have the ability to tell the scheduler to go to a specific stop regardless of name.

Without wait condition trains will overshoot and path to a wrong stop when there's multiple stops with the same name.