Cycle, Area or Cost ?

[Kwic]

Hi,
I think that you can NOT buit the cheapest/smallest/Fastest machine at the same time.

If you want to be the fastest, you probbly can NOT be the cheapest and/or slamllest.

So what do you privilege in your buits ? Fast, cheap or Small ?

[desrtfox071]

I build a solution that solves the given scenario.

Then I build three separate solutions that each optimize one of the three variables - for fun.


There is already a conversation regarding the optimization of one variable over another, or the possibility of combining the metrics here:

https://steamcommunity.com/app/558990/discussions/0/2381701715719939984/

[Alcator]

If you like a particular puzzle, you may want to make multiple solutions, each focusing on one of the primary factors - fastest, smallest, cheapest. That way, you get essentially three puzzles for the price of one :-)

[Trobby]

Always cheap. But i don't really notice until i complete the puzzle and see the histogram.

[martind]

From what I played I tend to go for cheap. It tends to be mechanically simple. Less parts moving at the same time.

[Blank]

So far I like going for cost since it lets me focus on programming just one or two arms and pushing them to the limit
Cycles is more about throughput while area is a non-stop parade of 'oh yeah that arm is in the way isn't it'

[PRinciple prickley!?!?!]

I usually just try to make a balanced solution that's pretty good in all departments.