Some of the other production calculators have the ability to change from a production view, which this one does way better than any others currently, to a table list of machines, the recipes they're using, how many, and the total output for each. Which would be great to have, in my opinion.
Some may disagree with this statement but a table view, I'm not at all concerned with the input requirements of each machine although having that info could help in some circumstances, but assuming that the calculator has done its job it's actually not important.
My concern is purely about going through with a fine-toothed comb to make sure it's not trying to use a base and an alternate recipe in different parts of the graph. Caused some issues with my final tier space elevator production line... Took a while to figure out what was going on and manually remove all of the extra options, esp. base recipes, to ensure everything was hunky-dory.
This view would primarily help with bulk factory layout as it makes it really clear how many machines are needed for each item which when you're building backwards would really aid with modularising the layout because there's one thing the current view doesn't help with and that's actually laying everything out in a grid. It shows the conveyor highway connections but... doesn't give many clues as to the final layout and it's really hard to work out what's being produced where in the tree. Like you have to trace through multiple connection points because the nodes say how many machines they represent but not the item they produce just the recipe name which for alternates is more than less than unhelpful.
I did try to figure out how to add it myself but... Typescript was a nope but manageable and then I realised it was built on Angular and I just couldn't... way to much abstraction for my brain. If I can't jump into the browser console and dig through the objects in memory and find what I can see in the code... I just can't... like. Urgh. But I'll say this, I think it should be quite easy to do from what I did understand of the current code, even if it's just a button that dumps out a CSV formatted output of the array I found.
greeny
commented
1 year ago
Some of the other production calculators have the ability to change from a production view, which this one does way better than any others currently, to a table list of machines, the recipes they're using, how many, and the total output for each. Which would be great to have, in my opinion.
Some may disagree with this statement but a table view, I'm not at all concerned with the input requirements of each machine although having that info could help in some circumstances, but assuming that the calculator has done its job it's actually not important.
My concern is purely about going through with a fine-toothed comb to make sure it's not trying to use a base and an alternate recipe in different parts of the graph. Caused some issues with my final tier space elevator production line... Took a while to figure out what was going on and manually remove all of the extra options, esp. base recipes, to ensure everything was hunky-dory.
This view would primarily help with bulk factory layout as it makes it really clear how many machines are needed for each item which when you're building backwards would really aid with modularising the layout because there's one thing the current view doesn't help with and that's actually laying everything out in a grid. It shows the conveyor highway connections but... doesn't give many clues as to the final layout and it's really hard to work out what's being produced where in the tree. Like you have to trace through multiple connection points because the nodes say how many machines they represent but not the item they produce just the recipe name which for alternates is more than less than unhelpful.
I did try to figure out how to add it myself but... Typescript was a nope but manageable and then I realised it was built on Angular and I just couldn't... way to much abstraction for my brain. If I can't jump into the browser console and dig through the objects in memory and find what I can see in the code... I just can't... like. Urgh. But I'll say this, I think it should be quite easy to do from what I did understand of the current code, even if it's just a button that dumps out a CSV formatted output of the array I found.