Friday Facts #384 - Combinators 2.0

[nixCorvus]

Great changes! Everything I hoped the new combinator would be for has been implemented. The only thing I would still like to see are the R/G check boxes on the Arythmetic combinator as well. This would make it possible, for example, to multiply each signal of the green cable with the corresponding signal of the red cable. I would be happy to receive early access as soon as you have implemented this. Where can I pre-order the extension? Shut up and take my money!

[crj]

if you have some ideas (for the Selector combinator) we would welcome them

How about some kind of unique-ID mechanism? That would be really handy in multiplexing signals from different parts of a mega-base, and is currently tricky to do. (The best way I know of is to leave a locomotive permanently parked at a train stop!)

[Tertius]

I wonder if it is possible with the new decider combinator to fully provide a stack filter inserter with one filtering item as well as the corresponding stack size, with 1 decider only.

Consider you have a list of items to load into a train. 5 wall, 10 repair kits, 15 belts. You want to load exactly this number of items into the train.

Currently, you need 2 combinators for this: one decider to get one item (with the ANYTHING operator) and its count. This is what you set as filter in the stack filter inserter. And you need another decider to convert the count of that item into a fixed signal (for example S) to set it as stack size. This is done with the EACH operator and output S(input count).

In my opinion this is an operation worth to be done with 1 combinator only. However, it doesn't seem to be possible to set the output options to something to achieve this result. Neither the new decider nor the new selector combinator.


Example with current 1.1 logic:

Screenshot 2023-11-10 150447.png (682.27 KiB) Viewed 3730 times

0eNrtW1uPozYU/isrHquwwmBuUdWHSv0FXfWlWkUOOMQdAtSY2Z2u5r/3AEkgjCHHmey+bEaamQD258M537n4km/WNm94JUWhrPU3SyRlUVvrv79ZtcgKlrf31EvFrbUlFD9YK6tgh/ZKMpFbrytLFCn/aq3J6+pql4TJrLS/sKwsRj3d188rixdKKMH7kbuLl03RHLZcArQWYGVVZQ194COMBzh2EDgr6wUAQRarlAJgWP/c+ej67XjPcKuU0KRo8rwVeDKSex6pVvB+2V7Z3WvqxvKGsVIhedI/dTWongEqQaNSPKofo1F9A9QQjRpgLeh777RgaCC/j5Y/MkDF8yI2QMXzgjhYZdPgncomBP8GFM9BYuCGFE9CYuCHFM8NYuCIFE8O4mPN6MXvNWNg8AYGRDTwRc+AHQbO6BmwY/DGvEzKQ6nEM9diugvq1uUUx0BePO1cA9/z8LRzDXzPw3PBNfA9F88Fd/C9A09Fc7B5Du2lSOyqzLk+b388Khk+wAgFB2G2ZSPb0sONP+tGGVwx5YlIubSBIFtRMHArbbSOzmPACFBQKVnmmy3fs2cBPaDZEWcDz9Kub93e3QlZq82bIupZSNWwfKij+hY2Z8ne6geoFWvLN6e9OFRMdpKtrd+gT9moqjFA/bOHrF5AuKZQm50sDxtRAIa1VrLhr/2IRW+XTm7S/pE8HRdvAq7aKJoImTRCdddQ6UFnt22dSc6LaXs3GGl/DuBVZ6FxBGPJk70TuQIziaLmEj7oi6KTkdyOCCOqUb3RTpIcypRvyt2mrLg8+j4Z5NyzIt1IztKu3cWjmsNvKx9Y4z/eq3PVS7w5Ddhp2shaM/bQaxir0HAUDTNRK/CoZM9r8Fr+bwP/r+m0dy5TLeKp5c9KHl3MUOyjJnXCBrMECHTAsXGsGUbQxRq68jxduPGc23Tv/jDdezO698gNbuj+hG7Y1hAYN/Rc08xDHpmnSxyBWebxyDTzBEgLecZRgcaLFcjKC7VRgRpSgdIHFTpLRoZU8KdUiJBU8M2jH/V/xuhHkQoNbkqEg06/eyIM5iQPzaOCuxAVIMpQoo0K0U0q8qIfpqJwTkWxubcMYv9E3kIdjbdARH3mUkL4vpCO6NaJHcPE4YWPxNEpPjZMHPE0ccS4OEeJcbTw/KVooS0g6FBLLvqYN+9jOlTvtgA0WYU5Nt70QaDfBTptLJ0HKJok50zau4a3hu8MDGp/1b7tUC61602FXauyWlpt8iarTcvx5Mz8G4jPihe1F0V2SX7Xcd7yH1rUHGKTKjfdW1jrHctr3uoLglXH7eP9Pi51t9s3rXh6+aS7OD9Cy/rJLFb5E8aTPlbVpyVSq26qKn/5kJcsbTXQQue9Zvt9vqyLAtvuM2uXVGkcOV7sEh/+ERp4ges5NIhCX+tIty/U+d8z1Oktfo9wd4l8j6jnk9mop2k9XU8i7V7uu1aeaHDzlPdhw5MNqYkNp4sR8zbELlvQofyV5basSqm0JW/U2y3UYkQ3z3cfPDjxwDfiAUXzADmBo/HNpefDhicbRiY2nE4W5m2onVboDoQM04dzVcoLLrMXmKpBrbZjiX6fLTw597Su2ja7HVjwOGNxzj+6wcnNCT38ngT6tMycX29gDof53N25486a33/r7Eu08jV1nc5ewxzjpJ1rBjsvhoazKxHjScGVE2ZMKpHnoEm73vM871XZTRNavp+Pqn3G67Al0mKBNKsLz1gX7l11AcV+we0vbKIGx+jIXsYUH3V3ndGxveu9zxHjIApgtp1KcSGNO5LGQ+BVzaH6hyVPIwhvQKAIhJzB1NdWjZRcjVD8kVYwahl49gaKDEgYFUmWMjlWydAdo5EkF7udzb9WObDpmdfjdxqQqAnjPWfKeIpkPL25dH9E635bdS5av4k5q8VC70o0D5D29G8uwR/27HcH0Nl3tVj0XbFnhLRnYJqRhq2Uu2QkJVlRt7NBe8tz9Y6s1EBTmUnonE6hfLMMVVe5UO0ipRYBE4F3rFbDroUWBpOYasV53i+d6qsWHwNygGw/WT3WZ9sAk21FNdc9RGU2kV8k6qF7hOx+Or0zyq4DSIwA2YpsVh2j/Ohg7YxjMMHC4XiMqiM6vGU2owqKfjNumc+EIms1fZ1GMFTW7oRoC1GC5bKtSrtX9sxrYVg92k3QspKguZ3sO6QFhpPYqG4LEFWBNi+Epnlh2Ii9S16QvGJC2tVlZe8aJoVOdtl0irLbdcf3pAXtlvQAFxmlCCaF2h94tzc26FVLZoxnaYoxLZaPVdrE4FowjJNNdgDBSSTLZrw2NMfrF470cJE53LBBqUXEpJfz6rbefYmJUAuMxSWAWbL6ZhmgkmUm2eHAtjmHjMLZ0wUaMUsDy/L4RgEuQpTJ2gAX3bwO/ZjI9Gd45iYy/pWJTGy0eh0j7RlfCa3ar+2MTXr95NAAfJ9jLjVvYTaDtW1wpNFxJOuXW6zdgZsdJ6JXjrHonQoIUEPYTJv8+B3d4UtS7TWJRw36lH/e8/8LqoBSZk2Rffid5yxtuo3/L2x8jKLH7NnPN8e37gx5CioFg7d7BiHbeyJ5qrsZRX/2QzvWH4W692CrxV5KHPiofdBJ97nVXBcR16PvWa8scNO63xCJCA1jNwwjL/KghHv9H2Pmyxo=

Copy blueprint

In my opinion, much too much combinators for a rather simple task to load a supply train with a configurable bunch of items.

[Splitframe]

Looks good. Addon release next week?

[farcast]

I can't wait to see what kind of horrors I'll be able to create in 2.0!

With deciders having infinite conditions, is it possible to make a computer out of one decider combinator connected to itself?
...ah, I'm getting too excited, you can't tie different outputs to different conditions can you? It's all or nothing. Still, maybe that just makes it harder, but not impossible...

Wait, how will the wild-card signals work?

[mmmPI]

Happy to read the FFF, quite surprised to see the change to the decider combinators because it was the least complex and now it's not clear anymore with all those possibilities added
To me it feel it helps for larger build, to make them smaller, I'm not sure it's making combinators look less daunting to see all the menu open at the same time for small build.

I think the abiilty to manipulate green and red wire separatly was quite a requested feature too and is a nice addition.

I'm still unsure how i would use the new combinator, i suppose it will make more sense to me when i actually try to automate interplanetary logistic but i'm not surprised there is something to adress this specifically and welcome the further implications.

I like the idea that there is a possibility to get a random output easily.

Since the scope of the Selector combinator is quite broad, there is also room for further functions we could give it, if you have some ideas, we would welcome them.

I'm not sure how it could work, but i have this idea that maybe it could be used also as sensor to detect on which environment/planet/gravity/pressure/velocity of the space platform it is located so that one could make blueprint that react differently depending on where the player copy them. ( ie : if space platform goes faster , light more lamps on each side or make them blink faster; or throttle/adapt some number based on gravity or day/night cycle lengh).

I'm sorry but you implemented many of the ideas i had in that new combinators, it make me think the others are not good

[Drury]

the selector combinator would've been useful a while back, good to see it

[Tooster]

[...] The second thing I'd like most is the ability to select certain properties from red or green only.. stuff like everything * everything would be a lot more useful if you could say "red everything * green everything".

YES. Vector operations, would perform out := green <OP> red for each channel at the same time. Yup. So many times I wanted to have this in the game...

[plepper1]

d) Output the stack size of the input item.
e) Output the rocket capacity of the input item (useful for Space Age logistics).
f) Transfer the quality of an input signal (more on that another day perhaps).
...
I know this seems petty, but it got me thinking more about this and looking at bullet e made it worse. The input MUST be a rocket, and the output MUST be the capacity.

I think you misunderstand. The input for 'e' is not a rocket. The input for 'e' is an item, such as iron plates.
The output is then "how many iron plates can a rocket carry".

[Moroquen]

I cannot live without this. Amazing!

A few humble suggestions:

(1) Could reorder the elements of the decider input signal configuration?

I think that the equation (signal - operation - signal) should be kept together visually, because that's the core functionality of the combinator. The wire configuration should be on the outside (figuratively, these are "the wires that go into the 'box' from the outside").

Additionally, I would place the R and G labels on the outermost and the checkboxes between the labels and the signal symbol - aka flipping the order of the label and the checkboxes for the left-hand signal. Again, that would reinforce the "wires go in from the outside and connect to the logic of the combinator" concept.

My sketch:

Decider-Combinator-UI.png (54.74 KiB) Viewed 3542 times

(2) Can we have wire selectors for the arithmetic combinator too?

I often run into operations like "substract the value of a signal on the green wire from the same signal on the red wire". Right now, that requires an additional "multiple by -1" arithmetic combinator that adds clutter for no good reason. It would also make the arithmetic combinator UI more consistent with the new decider combinator UI.

Bonus points if you would re-use the output configuration from the decider combinator for the arithmetic one (aka allow to send the output of the operation to more than one signal and select the wires.

(3) Constant value output for decider combinators

I think the "custom value" idea from j_matya is fantastic. I think it could be simplified to "constant value" with a default value of 1.

Thank you so much for all these fantastic improvements in the recent FFFs. It's unbelievable how much better you make an already incredible game!

[Somtuk]

d) Output the stack size of the input item.
e) Output the rocket capacity of the input item (useful for Space Age logistics).
f) Transfer the quality of an input signal (more on that another day perhaps).
...
I know this seems petty, but it got me thinking more about this and looking at bullet e made it worse. The input MUST be a rocket, and the output MUST be the capacity.

I think you misunderstand. The input for 'e' is not a rocket. The input for 'e' is an item, such as iron plates.
The output is then "how many iron plates can a rocket carry".

If that's how it is meant, then you are right, I did misunderstand.

I still feel the whole "this function is specific to rockets only" aspect seems out of place. I hope it gets reworks a bit.

[Kyralessa]

Will this make it easier to make an S-R latch?

Every time I make one, I have to look up how to do it again.

[Brambor]

I would like to get a specific tick (morning perhaps) on this surface. I made combinator based calculation of how much power does my anti-meteor defence need until morning and checked that the accumulators will last. This is based on number of ticks in a day, solar power multiplier, ammount of solar panels and ammount of accumulators.

Detecting when the morning starts for the first time reminds as a annoying problem left to solve and the solution is... not nice (after first morning the next arrives after certain number of ticks). I don't care if it is morning, sunset, sunrise, middle of the night, but give me something. Also, not Nautilus time but this surface time.


Edit: "selector > select surface" would return the tick T since last morning.

[revanar]

Now I'm hoping that we get the ability to somehow read the composition of train cars in a station---that paired with the selector combinator would make it relatively easy to build train stations that could automatically adjust their properties based on the length of train that's visiting them!

[Attal]

This is priceless!

Very nice selector guy!

[PaszaVonPomiot]

I feel like christmas every week.

[deer_buster]

Regarding multiple outputs...it would be nice to specify which output wire color gets what output

[StansTheMan]

This is nice and all... but does this FINALLY give us a way to 'sanitize' our inputs? Specific case: I was working on making a station using LTN that would allow me to load multiple types of cargo. The problem is that LTN's station, alongside expected cargo, also dump out a whole bunch of other data. And as I was using filter inserters with set filter, this could lead to them trying to set their filter to a signal instead of an item. If I were able to 'sanitize' my input, this would be a lot less cumbersome. Because right now the only way I could would be to add an arithmatic combinator which multiplies the values of all the data I didn´t want by -1. I think a nice feature for the 'selector combinator' would be to specifically filter out either groups of signals (so u can filter out any 'non-entity' signals like letters) or specific values, though a group would be most useful in my specific case.

Huh. I think you are doing it wrong or I am misunderstanding things.

Just place a Constant combinator with a -1,000,000 signal of every blacklisted item. = Blacklist.

Or place a Constant combinator with a +1,000,000 signal of every whitelisted item, connect to an arithmetic combinator with input "each", subtract by -1,000,000, output "each". = Whitelist.

Obviously this onlys work because machines and inserters filter via positive leftover signals. Dunno how LTN works in this regard

[Kadet123]

The only suggestion I have for all combinators is in the sprites and connection locations: offset the connection locations so that the connection points don't form a straight line.

For example, in the post's very last picture of a line of 5 combinators, on both the left side (inputs) and right side (outputs) all the connection points form a straight line, which makes it harder to tell which wires go where on wires that go vertical between combinators, especially when multiple wires overlap. The overlap of wires could be reduced a little by, on each side, moving the top connection point left a pixel*, and the bottom connection point right a pixel, so that vertical connections don't overlap so much.

* Pixel meaning some tiny bit, not necessarily exactly one pixel.

[AileTheAlien]

Great changes, thanks! Combinators were really fiddly before, because you needed separate ones just for a simple and/or.

Now I'm hoping that we get the ability to somehow read the composition of train cars in a station

Yeah, this plus...I think cargo was missing? Maybe you can already read the cargo totals for a train, without any mods.