|
The thing I actually want most in this game is some real keybindings. You won't believe how many times I've inserted ddkp into the program while trying to rearrange things. I binged through most of the levels last night, just primes and sorting to go. And my brain has wasted most of today designing a solution to the former one. Game is addictive and I haven't even started seriously thinking about optimisation yet.
|
#
¿
Jun 3, 2015 05:07
|
|
|
|
| # ¿ Apr 29, 2024 08:09 |
|
|
Wild M posted:I haven't done that one yet, but don't you just have to shuffle numbers between the stacks and inject new numbers in their proper place after doing some subtraction and comparison? Though I don't recall the node structure there. That's the basic strategy, yeah - you use your two stacks to emulate a list, and then use whatever sorting algorithm you can implement in the space constraints to sort it. Much of the complexity comes from the fact that the node arrangement is rather pants-on-head and (I assume deliberately) designed to require lots of instructions just moving things around and leaving you squeezed for actual code space.
|
|
#
¿
Jun 3, 2015 15:39
|
|
|
In general yeah, you should be splitting things across nodes if you can. For example, if your first node zeroes out everything that isn't 1, 4 or 5, that makes signaling easier. Also remember that you have the position of the instruction being executed as effectively another piece of state. -- Primes ended up being fairly straightforward, though of course it took forever to run. There are a bunch of optimisations I need to do on that.
|
|
#
¿
Jun 4, 2015 01:12
|
|
|
Quinton posted:I went with a really trivial convert RLE sequences to sequence of color numbers, feed that from one edge, feed X values from another edge, feed Y values from a third edge, and fuse them into X, Y, C, -1 and spit them out. Super straight forward, skips the trickiness with needing to break the sequences at the right edge (since single draw commands cannot wrap onto the next line), but not nearly most optimal. This is basically what I did as well. There's a really obvious optimisation that I only realised after finishing it.
|
|
#
¿
Jun 4, 2015 04:08
|
|
|
Sequence Sorter done.That's the first time I've had to use JRO shenanigans just to make the topology work, but overall I'm reasonably happy with it as a first solution. I'll probably give things a break for now.
|
|
#
¿
Jun 4, 2015 10:27
|
|
|
Well, since we're posting solutions, here's my unoptimized prime detector, courtesy of Euclid. 97485/5/38, and there's potentially enough space to compact it to 4 nodes.
|
|
#
¿
Jun 4, 2015 12:44
|
|
|
ymgve posted:I just saw someone else proposing a different algorithm that might be better, too: This is kind of how I solved it. The selection sorting itself was pretty straightforward, but recognising the end of the sequence and outputting a 0 there was a bit tricky. One helpful insight is that you don't need to keep the sequence in order, so you can just pull out the lowest element seen so far when you're copying the sequence, and if you see a new lowest element you can just put the old one back in at that point.
|
|
#
¿
Jul 7, 2015 03:09
|
|
|
ErIog posted:The problem is that I can't tell if my changing the code fixed the problem or my passing is still just a fluke in the random data. I wish the game was more rigorous with how it tests the solutions. Random data is fine, but passing doesn't mean anything if you pass due to the RNG giving you data that doesn't trigger holes in your algorithm. Pairing random data with some hand-constructed data meant to smoke test the algorithm would be a nice compromise solution. This is actually what the game does do AFAIK - the first run of the program (which is the one used for scoring your solution) is on a fixed set of data, and the second run (which only happens if the first run passes) is randomised. Really, the problem is that the fixed set doesn't always do a good job of exercising all the edge cases.
|
|
#
¿
Jul 8, 2015 08:08
|
|
|
http://steamcommunity.com/sharedfiles/filedetails/?id=481921899 So am I like, the only person who's finished Signal Exponentiator?
|
|
#
¿
Jul 15, 2015 12:17
|
|
|
I think there's one big trick you're missing: when subtracting two numbers to compare them, you only need to keep one of the original numbers around. You can reconstruct the other one via addition. This should let you eke out a little more space.
|
|
#
¿
May 20, 2016 01:51
|
|
|
This is seriously my jam. Why is it not October yet.
|
|
#
¿
Sep 13, 2016 02:20
|
|
|
|
| # ¿ Apr 29, 2024 08:09 |
|
|
TheKnife posted:I impulse pre-ordered the physical manual edition before even watching the video, are you supposed to get an e-mail from zachtronics or humble store after that? Because I only got a paypal receipt Yeah, you get a humble link, and it has a link to a form where they want your address. Shipping the physical stuff is apparently starting on ~26th.
|
|
#
¿
Sep 13, 2016 15:48
|
|