old LTN discussion thread

[tuttifrectte]

Has anyone work out a circuit that can fill a train to the brim, but not leave any items held by the inserters?

I want to create a station that can provide several items. I can't have inserters holding item because they insert it into the next train. I know I can do it by "locked slot per wagon", but I feel bad for the trains not getting as many items as it can get.

[steinio]

Hello,

can we please get a global setting for limit trains?
0 = no limit.

Greetings, steinio.

[Mobius1]

Nice idea what you told about min delivery, but its not true. It gets ore from supply stations and send it to my requester in base, working perfectly. I set min delivery on the requesting station, that is, as far as i know, correct.

Yes, that shouldn't give you any troubles

In base requester i set - 20000 iron ore, min delivery 7 (tried also 8) 000, it just creates 4k orders.. FIXED, vanilla (2) can only carry 4k instead of 8... Just in case, if i use not vanilla trains, will LTN know i can carry more? (MK2 Version e.g. from bobs)

Min delivery is the minimum quantity of a item that you have missing in storage before the LTN requests them with trains. Which means that if you request 20k iron ore, with a minimum delivery of 7k you will only start requesting iron ore again when your storage hits 13.000 or less.
4k is indeed the max cargo capacity of 2 cargo wagons, if you have in your depot a train with, say, 8 cargo wagons that train will be able to carry 16k iron ore. The work order is created based on the train size you have on your depots.

But how should i stop the requester stations from getting provider? Oo(!!!)

That is easy, just follow these steps:

With Logistic Robots

1- Wire from your constant combinator with the requester signals to a decider combinator set to "Each < 0 | Each"
2- Wire from your roboport to the input side of that decider combinator with the roboport set to "read logistic network contents"

• PS:if your work order is less than 1000, you should hook another decider on the roboport with "each > 0 | Each" setting so you don't send negative signals from your storage. In 0.15 when a robot is going to pick an item, its carry capacity is taken away from the logistic network before it grabs the item, so if you have a carry capacity of 5 and your robot is going to pick 1 item, it has a -4 signal in the network which is a requesting signal to LTN.

3- Grab a green wire from your decider combinator into the lamp of the station and that station will never be a provider.

Without Logistic Robots

1- Wire every chest you have on the station
2- Wire your constant combinator with the requester signals into a decider combinator set to "each < 0 | each"
3- Wire your chests into the input side of that decider combinator
4- Green wire from your decider combinator into the LTN lamp

Essentially what this does is: you have a -20k signal on the constant combinator, your storage have 14k iron ore, the decider combinator will read both wires comming into it and will sum them up, so it'll count -6k signal and it'll output -6k signal to the LTN station.
If you have 21k iron ore in your storage, the signal the combinator will read will be +1k and will not output that signal to the station since its set to only output negative signals (each < 0). So you're basically turning that station into an Unload station, without Loading capability.

[ichVII]

To come back to my Problem, i have a solution Suggestion, that may not be "to proon to user error":
You could include 4 new Parameters, namely "min-fluid-wagon-Count", "max-fluid-wagon-Count", "min-Cargo-wagon-Count", "max-cargo-wagon-Count". They should then work just like "min-Train-length" and "max-train-length" and should, as there is no binary Encoding Operation needed, not be to proon to user error.

As I am planning to publicly release a safe of what i want to do with this mod, It seems like a personal modification is not allowed.

[Optera]

Update for 1.2.4

By request I've added a toggle to output expected train inventories after laoding/unloading is done.
Default is disabled so it won't break existing stations. Provider should be fine mostly but Requester will break.
When enabled it allows for very sleek station designs considerably reducing the number of required combinators.

Here's my universal provider & requester for this mode. It uses 11 instead of 22 combinators now.

2017-05-13-12-16-07-8539489.jpg (101.42 KiB) Viewed 7344 times

blueprint

Code: Select all

0eNrlW1tzozYU/isZHjtmR0IXwLPtL+j0pe1TZ8dDbMXWFIMLsrvpjv97JXACBgQ6JOtsdl+S4fahc/nOdySLL959ehSHQmbKW37x5DrPSm/51xevlNssSc059XgQ3tKTSuy9hZcle3OU5ltZKrn2VZHIzC9VfvDOC09mG/HZW+Lzwh1hvROl8gvxz1H/F0ULJoDDJGslT8I/FPlJbq7AyPnTwhOZkkqK2sTq4HGVHff3+s4lfsYsjVHbnR5UIlP9qkNe6qfyzAxCI/k4WniP+r8en7eRhVjXF6vhdkADd1DuDErcQakzKHUHDZxBmTsocgblzqDucQqdMd3DFDljukcpdsZ0D5JxvRuoe4ywM5sA43Qmk7s/sTOX3OOOnanknp/YmUkAImFnJgEoj52pBChO2JlLgDKKnckEKfgNmTZibTTIX+f7e5klKi8GK/QHVoEjja3VVxV5uroXu+Qk9f36pgvKSl/bVE+W5uyDLEq16mnjSRbqmKSNPNZ3+NSr0UuVGKFH5mB/SIpqUEvvF/1AflSHIwBSnETxqHYy29bYh0c9xGOmVg9Fvl/JTIN5S1Ucxbl+dVZ7rRo9Nn8KsWnLsNRHjJ8/6bsDy+Ug0JfPQ07Hrv3AQADIUwA+sEHsdtVJ1n/7DzLVbYovs1IUahzSN5jDYV3LYn2UarXPN2KVP6zyg9DRqECwu8NMtj0hVcctA6pjYvMY6Vg1Zk7Q8tA1AcZte07ZGRnbTS9b6v7sAfLLJNDC2xZCZL1LzOYpOt2yDvgMX/nslTIAOHIGz1x8nbmtWNOvbAXtp27nBO/musVsDqzA6EetwIOBYGFTg4H5FsIcH97C7+SdKF84rnyxzefRfOXjE8IXg8sHv5nuheO6R5DFXwS56x77bmQvtsoesVVRgufIHr2Z6tkHDu/X6FuJHsH9vO2cIG6iRwis9pIftfYOa140oXn2bKMwv9+k1wjeieZFo5pHuM3nbLbmoXHJIxxaO9CtFM8k2qjihTZvhc6Kh78XwTOpYxM8WydFohmCF9xO76zjBrdpwZvJXdRP2usTFLnJHYWtspEfteoOq108pXa2XKMY5HZ+C7fjdyJ28ajYUWpzeTBb7MJxsaPuS4DR9yIMxs0WYaA2AaUUWmDDWzUFho9jTQG1Lf9SBiLybZbI8HspoBxNFFB7LvEZTUZ8sybDPu4QyoH4rZoM2l03prx7gjk2GU1HmBRS7faiCtcYT4IWT6ZNblBfRhyRrHfX3PF1YWg50PtpDncqVBAxaHztWTzBE9aNFbet29EYVrAoKBCvUr6SzEWuvpl+pCcdVmGMukG9jhljo50Nc2zpGQKzjXwrbAu+NtuG/BpYuTbUKcTjnYKVeAzW8mN2e+L1A9Il3cfZAbHS7SFJS+C0K+gTwT1g2MpPe+gCMKP4mzKqFAbG4blf//jNXyfFNvf/TbZ6gOe34B+aKIvEHrFgShdxn9uDESZjG3L92gdD25mszVnwkvrjKCBWBaCj1tTEsxsz3R6/ZDrqqu768rEU+lVpXpQXVYZMLayhZqN7r21b1pDTfL0UmnYqX1WAl9q20EFPNnXNu5yHGjPUDg7a1syK9mIjj3tfpPoFhTbxkKdicLP0Jej4Kehzdkv1KBtac5jZZkYshI49njN01p3EdH8B79kS2W3hEztrhrCGjY+gxgdzjO/+9jEQt0Vvsc22/k9mYA0bHwONp3Nsp3gyNv1OzlaI0QysQds5Atr+vLEMlvUT2xtH4twXnfFFANyHXkxNmIZdg6GuiSZdM0zj7o45blvt400j+CRd421geDWiln7wYf2oV4MsHw7ZFBXVUnqsZ1CYhjQi3IRt9COiicXDCg2jkIQUR2br5uinRBM/5VRgjPAoRLHZAf/8JREEi7SwAh5RwqjRuwsWBWHRtpGEBjgMg8ZhDITFWlg8xCiKeOMuDoLiLShCGKOUNN4KQVBh20Ieavtw46wIBBW1oCKizUONq2IQUtxCojimBDWewvVa8OxZoK0n4gTI2djG2eA1OLvXjeZGpNKsRPml/E9c0Q0hKGsNXt2+piLbql3bw1DS7pPP01gEFqZLH67VpfrccNn6THLhpcm9SOtp6J1/92dmvJKkd7+ragJ6d6IfkL5LnyzroklpwLAubYicz/8DyxSPaQ==

setting descriptions where refomated to hopefully be more readable

added chinese translation from 745275633

fixed a bug where adding wagons to a train parked in provider/requester would throw an error

You could include 4 new Parameters, namely "min-fluid-wagon-Count", "max-fluid-wagon-Count", "min-Cargo-wagon-Count", "max-cargo-wagon-Count". They should then work just like "min-Train-length" and "max-train-length" and should, as there is no binary Encoding Operation needed, not be to proon to user error.

Feels redundant as ltn will use the best matching train regardless.
e.g. a request between 7501 -15k fluid will likely pick a train with 2 fluid wagons.

Thinking a bit about limiting trains to an encoded train composition entails I noticed it's ambiguous.
e.g. a terminus setup only will have each train turned around after a round trip
a train L-C-F-L will be L-F-C-L
There's no clean way to resolve this. So no, this will never happen.

[tuttifrectte]

Update for 1.2.4

By request I've added a toggle to output expected train inventories after laoding/unloading is done.
Default is disabled so it won't break existing stations. Provider should be fine mostly but Requester will break.
When enabled it allows for very sleek station designs considerably reducing the number of required combinators.

Damn this is nice, now I can calculate (expected inventories in train - current inventories in train) to get a number which positive means the train needs to be filled and negative means the train needs to be emptied. This is great for stations which are both providers and requesters.

Thank you for your great work

[nuhll]

Update for 1.2.4

By request I've added a toggle to output expected train inventories after laoding/unloading is done.
Default is disabled so it won't break existing stations. Provider should be fine mostly but Requester will break.
When enabled it allows for very sleek station designs considerably reducing the number of required combinators.

Damn this is nice, now I can calculate (expected inventories in train - current inventories in train) to get a number which positive means the train needs to be filled and negative means the train needs to be emptied. This is great for stations which are both providers and requesters.

Thank you for your great work

Nice to see hes adding things for the 1% of users

btw, did anyone notice if you flip your blueprint with LTN stations in it... it gets deleted and just the lamp and the output is printed... (ALT + R)

[tuttifrectte]

If a provider station supplies items A and B, and a requester station is requesting 100 of A and 100 of B, is it intended that there is no delivery if minimum delivery size is set to 200?

Nice to see hes adding things for the 1% of users

btw, did anyone notice if you flip your blueprint with LTN stations in it... it gets deleted and just the lamp and the output is printed... (ALT + R)

It is because the train station cannot be mirrored, so the game just does not place it. The game considers the lamp and output as different structures. It is interesting that the flipped train station still shows on the blueprint.

[Optera]

Nice to see hes adding things for the 1% of users

That's because I happened to be in that 1% myself

btw, did anyone notice if you flip your blueprint with LTN stations in it... it gets deleted and just the lamp and the output is printed... (ALT + R)

You would have to talk to the author of whatever mod you use to mirror blueprints and ask them to add a special case for ltn stops.

If a provider station supplies items A and B, and a requester station is requesting 100 of A and 100 of B, is it intended that there is no delivery if minimum delivery size is set to 200?

I'm torn on this.
Summing up all items to get past min_delivery size makes sense.
However it would require a different strategy finding suitable providers as min delivery size no longer applies to each item but the whole request which can be served by multiple providers.
Min delivery size would become a pure threshold for requesters with no effect on providers. Similar to activating best effort.

I could add request threshold and provide threshold and change how providers are deemed eligible.
If I do that min delivery size, ignore min delivery size and best effort will become obsolete and removed.

[tuttifrectte]

Nice to see hes adding things for the 1% of users

That's because I happened to be in that 1% myself

btw, did anyone notice if you flip your blueprint with LTN stations in it... it gets deleted and just the lamp and the output is printed... (ALT + R)

You would have to talk to the author of whatever mod you use to mirror blueprints and ask them to add a special case for ltn stops.

If a provider station supplies items A and B, and a requester station is requesting 100 of A and 100 of B, is it intended that there is no delivery if minimum delivery size is set to 200?

I'm torn on this.
Summing up all items to get past min_delivery size makes sense.
However it would require a different strategy finding suitable providers as min delivery size no longer applies to each item but the whole request which can be served by multiple providers.
Min delivery size would become a pure threshold for requesters with no effect on providers. Similar to activating best effort.

I could add request threshold and provide threshold and change how providers are deemed eligible.
If I do that min delivery size, ignore min delivery size and best effort will become obsolete and removed.

I don't understand the bolded sentence. How does min delivery size currently has an effect on providers?

Another request, can be get two more signal outputs: "# trains queued for pickup" and "# trains queued for delivery"? It has the following benifits:
- More fine grain control of stations who are both requesters and providers (e.g. I can limit # of pickup trains but allow infinite # of delivery trains by a circuit)
- With programmable speakers, this means we can have alerts on map.

[ssilk]

Simple question: Is there a way to convert 0.14 games to 0.15, so that I don't loose the train stops? Currently the train-stops are removed when I try to load a 0.14 game.

[nagapito]

Simple question: Is there a way to convert 0.14 games to 0.15, so that I don't loose the train stops? Currently the train-stops are removed when I try to load a 0.14 game.

Maybe something changed on last version that made the upgrade impossible....
Try the 1.2.3 version to upgrade the map to 0.15 and after upgrading, update the mod.

My map updated without a problem to 0.15 with the previous version

[Optera]

Simple question: Is there a way to convert 0.14 games to 0.15, so that I don't loose the train stops? Currently the train-stops are removed when I try to load a 0.14 game.

I can directly load saves from 0.14.x to 0.15.10 with LTN 1.2.4 without anything from LTN breaking.
Migrations working so far:
0.14.22 with LTN 0.8.1
0.14.23 with LTN 1.1.1

All blueprints have that weird signal offset bug though....

[ZlovreD]

Strange bug with station which supplying angels-ore4

screen

upd: Seems problem with priorities. If setup few stations with prior=100, some with 10 and some without - then those, with prior=0 ignored at all.
But maybe a valuable note, those stations what with =100 is empty and all stations supplying different resources.

[Optera]

Strange bug with station which supplying angels-ore4

screen

upd: Seems problem with priorities. If setup few stations with prior=100, some with 10 and some without - then those, with prior=0 ignored at all.
But maybe a valuable note, those stations what with =100 is empty and all stations supplying different resources.

Seems like an configuration error to me.
Without best effort/ignore min delivery size active providers have to have at least min_delivery_size of the requested item in stock to be valid.
Valid providers are sorted by least deliveries - highest provider priority - highest item count.
The first provider after that is picked.

[ZlovreD]

Seems like an configuration error to me.
Without best effort/ignore min delivery size active providers have to have at least min_delivery_size of the requested item in stock to be valid.
Valid providers are sorted by least deliveries - highest provider priority - highest item count.
The first provider after that is picked.

I'm realise a core behaviour of LTN.
Maybe there some "blacklist" mechanics? Because as seen in screenshot "UpdateStop" step return actual amount of resources which provided by the station, and then LTN says what there is no stations with a4 ore.
Station have only train count and lenght limitations signals.

And when i was re-build station - it start supplying ore. As i has sayed - strange bug.

[Optera]

Seems like an configuration error to me.
Without best effort/ignore min delivery size active providers have to have at least min_delivery_size of the requested item in stock to be valid.
Valid providers are sorted by least deliveries - highest provider priority - highest item count.
The first provider after that is picked.

I'm realise a core behaviour of LTN.
Maybe there some "blacklist" mechanics? Because as seen in screenshot "UpdateStop" step return actual amount of resources which provided by the station, and then LTN says what there is no stations with a4 ore.
Station have only train count and lenght limitations signals.

And when i was re-build station - it start supplying ore. As i has sayed - strange bug.

There is no blacklist.
However deliveries are reserved the moment a train is sent to pick them up so multiple trains don't try and load the same item.

[nuhll]

Sometimes LTN is mysterios..... why he want to make a train with cooper 3357, 286 plastic and green cricuit 3400? (into a train with 2 vanilla wagons? max 4000) Min delivery is 3900 or 4000

Edit, found another example see screenshot

Only thing i changed was limit train 2, because sometimes waiting trains were blocking my main line, now he seems to nearly everytime create such silly orders, whats wrong? After some time its back to normal and he creates only deliverys with 3900 or 4000 (now i changed to 3950 and he created 3960) which is fine. Sometimes it happens when he say "merged delivers blabla 80 stacks" (is it possible to disable this? Atleast per station?

[Mobius1]

Hey optera, is it possible to make a map setting or map option to change the default 180s inactivity on load orders? I found a very annoying loop on work orders that changing that 180s to 5s would fix it.

The issue is with robots, more precisely, fast robots with high cargo capacity with the new 0.15 logistic system. When a robot goes to pickup the item, its cargo capacity is added to the system instead of the ammount of item being picked up, so, I have this situation happening:
1- A station requests 10 barrels of waste.
2- The producer (provider) has 7 barrels, the robot goes to pick it up (cargo 6).
3- The robot, while flying, changes the available item on the logistic network to 13 items (7+6 = 13).
4- A work order is issued to that location requesting 13 barrels (when there's only 8).
5- Another robot goes and picks up another waste barrel, the logistic shows 14 (8 + 6).
6- Another work order is issued to that location requesting 14 barrels when there's only 9 of them.

So the trains goes into the station and stand there waiting to get that ammount of barrels, but the work order load is 27 barrels when in the station there's only 9, so the trains will be standing there, waiting to be loaded past 20 seconds of inactivity. With a simple adjustement on the queue to 5s they would leave the station with 9 barrels and allow another train to pick up another work order.

[nagapito]

Hey optera, is it possible to make a map setting or map option to change the default 180s inactivity on load orders? I found a very annoying loop on work orders that changing that 180s to 5s would fix it.

The issue is with robots, more precisely, fast robots with high cargo capacity with the new 0.15 logistic system. When a robot goes to pickup the item, its cargo capacity is added to the system instead of the ammount of item being picked up, so, I have this situation happening:
1- A station requests 10 barrels of waste.
2- The producer (provider) has 7 barrels, the robot goes to pick it up (cargo 6).
3- The robot, while flying, changes the available item on the logistic network to 13 items (7+6 = 13).
4- A work order is issued to that location requesting 13 barrels (when there's only 8).
5- Another robot goes and picks up another waste barrel, the logistic shows 14 (8 + 6).
6- Another work order is issued to that location requesting 14 barrels when there's only 9 of them.

So the trains goes into the station and stand there waiting to get that ammount of barrels, but the work order load is 27 barrels when in the station there's only 9, so the trains will be standing there, waiting to be loaded past 20 seconds of inactivity. With a simple adjustement on the queue to 5s they would leave the station with 9 barrels and allow another train to pick up another work order.

Wait, what?
You must have some mod that is messing up the logistic network!

My logistics network doesnt do that, it actually does the opposite. While the robot has the item, the logistic network doesnt count it, so when the robot pick the 6, the logistic reports only 1, the one in the chest and ignores the 6 in the robot.

Even if it considered the 6 in the robot, it should only consider 1 in the chest, so it should never be 13!

Oh, and my logistic does this moving from active providers to storage chests, which are all chests that count for network content, if it was to requester chests would made sense of it ignoring the amount since request chest are ignored for network content.