odd behaviouir of crusher recipe selection

[Rauschkind]

so, i have a crusher that gets its recipe by combinators.
no combinator is signaling "metallic asteroid cruishing".
yet, i see the crusher selecting this recipe frequently, it seems to default to this recipe when it has no recipe for a tick before selecting "no recipe" (as it should).
this is very annoying because it then will stick to the recipe untill it has depleted its storage.

i simply cant make sense of it. any advise how to make this machine behavie was greatly appriciated.

[jdrexler75]

Show your setup.

The crusher will select metallic crushing if you have "set recipe" enabled and it receives a metallic chunk signal. It doesn't need the specific recipe signal. This makes it easier to use deciders operating on metallic chunks (or the other resources) to set the recipe without needing a recipe translation.

That also means you can't both have "read contents" and "set recipe" at the same time, because its contents will send the signal for the recipe.

(This is a problem with all machines, not just the crusher, and I wish we could separate both functions to separate wires somehow.)

[LCStark]

It's difficult to say anything about it without seeing your setup. I've never had this weird behaviour occur on crushers. Most probable answer would be that you've got a signal contamination somewhere.

[Rauschkind]

The crusher will select metallic crushing if you have "set recipe" enabled and it receives a metallic chunk signal.

really. of course it gets a metallic chunk singal. i use that signal to control other stuff.
i want to control my crusher. i want to use the reciepe signal to control the reicpe.

this just seems so dumb. why??

[Rauschkind]

It's difficult to say anything about it without seeing your setup. I've never had this weird behaviour occur on crushers. Most probable answer would be that you've got a signal contamination somewhere.

i did not post a screenshot because its would show 16 deciders + 1 constant combinator, and i felt making sense of it was to much to ask from random strangers on the internet XD

[jdrexler75]

this just seems so dumb. why??

I explained why in my post. It's extremely useful for simple setups with deciders. Most machines are like this. I would've been upset if it hadn't worked this way! But you can make a suggestion thread about making this configurable if you like.

Or do it like this, using this design I can set the crusher recipe to ice/carbon/iron ore depending on which inventory is low, with ice having higher priority over carbon over iron ore, with just one constant box and one decider to handle all recipes. (Didn't get to asteroid reprocessing yet, that will probably go in a different crusher.)

Screenshot_20241118_005442e.png (289.41 KiB) Viewed 180 times

0eNrlWF1u4zYQvorAZymNHdmJje0CPUMfF4ZAUWObCEVq+eONG/gAPUgv1pN0SMmyLcmOnXSxCyzyEIo/38x833CGySvJhYNKc2nJ/JVwpqQh8y+vxPCVpMLPSVoCmRNTUQZJJahdKl0ma5eTXUy4LOCFzEe7RUxAWm451OfDxzaTrsxB44Z4j1MA4wXohKky55JapUlMKmXwqJLeHsKNY7Il8+TpboImCq6B1YsjXEAPrVYiy2FNNxxP45EGM8O1IuAYP3v8hR4tuTY2O8Rlt5X3Z8O1dTjTOljvSICytY/QgMfJenxwBn4Zw6ioDmHMye+Icmwmk2C/Kf0c3NFQkPmSCgMxWWkAjMdqB10TV56p7ULWREFlgd70gxxy9s1DH2SGUZ2jWj+MnGt5aPz69+9/yK18dkP83pRyrWSiNPxSpH4Aqs/X6UmsVsrZytlusbtSJ6aqLVYbJ2221KrMuESshrfdYhfY6lTAcYvla6yl0l4sgQ93kxuLoKk3mNMxRrev0T5ThAXdnT2lPyZfMXL0HKckVvrAQi/nQuzo3ejeh9pgHUL0KXEb0MMx0EPcE/JGtyb396gDKoHECrrF3lCAYZpXNYfkT7CRpXqFv7jcoFRKbyNqIgkravkGog3FvngX/SFEPTRR6YyNcogKvlyCxiMRNsIII/2tZi7CLqo0ehhZFfn7dEcG0uAQGtPOrOF895sG4YeVthmmA/ep2lxobqFsdC2O7gEsl5xxkGyblKpwApIxOez2fGdt+E1WtF8plglL2TOZN9IMrIw8xYuBMNM2zCU1NuHSgLZwKc8fh/L8YsKWYKkQnCVoAbTiRcLWTj5flSqDWVvr+GHAg8TqBZ8l70LDAuUMZG38tcw9mic30zzt0pwOwE5bWHipNBiTWE2lqZS2SQ7C9vHTs/hPA/iP78d/vAb/qcXPnXi+QMt4D5uevWyMa+a4zUDSXPjm6KWI2+n2ken3XtWN6uKPiYw1qiP8J+IL1q+c9HXsGRaroJ7AKiO48QlxzXWYxRf+WumJfx+kvz+juwZaoB8bLlehx++FP563qi3AGr5ik7AHF8804VMNKPPNpn04HMH4V0XufKcxPRslN8abD7mkXbCSlRTtcsRptiOYYWvwRb/2QCjkW3l7/nt2tF6Hy5QumueQpU2blNRtuEHqvtHjXK+3DTys4v0DyneY+oEUdH77juA0UFSqpCv6F5edu5L2rspnEh5Z/6sPZ+7p8DW9bLspD1caPnepT/yYDLkReu9Br6UTK6XpOwS70uE33seYUKzj9pBwHa83TjAq3U+QZ+MfmWfvSvLvkmjDmvmnHiqEBHpdvoziUTyJR4s4jGbNaOx/wiiNH3C0qF+boZjv/9EUkw2WteDpZDqepbPZJJ1Op+lsutv9B02iaws=

Copy blueprint

Just connect the constant box to the green input, and the inventory to red (in my case the hub but a belt system will also work).

It works the following:

• If the "each" signal is the ice signal (i.e. matches the green ice input), and ice is low, make more ice
• If the "each" signal is carbon, and ice is OK but carbon is low, make carbon
• If the "each" signal is iron ore, and both ice and carbon are OK but iron ore is low, make iron ore

If I had to translate the "each" signal to its corresponding recipe, that would be extremely irritating!

[Rauschkind]

xplained why in my post. It's extremely useful for simple setups with deciders

yeah. and it extremly can break a setup where this is not the intended function and it cant not be controlled.
at least put in a checkbox if ingredients should set the recipe.