Currently, I cannot enable the matrix solver if two subfactories share a common recipe. However, it is quite common for me to place two simple recipes like iron gears into several subfactories, meaning, I want to know exactly how many machines I need per subfactory, not for the entire factory, as I usually don't put things like iron gears or copper wire on the bus. It is however extremely annoying that that means I cannot use the matrix solver.
I therefore have two suggestions:
Allow the user to specify that recipes in a subfactory only count towards the required amount of that particular subfactory, not the overal factory
Allow to enable the matrix solver only on certain (sub)factories, treating their subfactories as standalone recipes with fixed inputs/outputs, that way I can use the traditional solver for some floors and the matrix solver for other floors.
Also it would help a lot if I could tell an entire factory to produce ingredients for a set of other factories, but I could imagine that that might be harder to implement.
Suggestion
Currently, I cannot enable the matrix solver if two subfactories share a common recipe. However, it is quite common for me to place two simple recipes like iron gears into several subfactories, meaning, I want to know exactly how many machines I need per subfactory, not for the entire factory, as I usually don't put things like iron gears or copper wire on the bus. It is however extremely annoying that that means I cannot use the matrix solver.
I therefore have two suggestions:
Also it would help a lot if I could tell an entire factory to produce ingredients for a set of other factories, but I could imagine that that might be harder to implement.