There's a bug on the achievement for the secret segment. It didn't pop the first time I completed it. I think that might have something to do with the red notification box that appears the first time you solve it. In general, I think you should take out all the instances where story stuff happens only once. It'd be kind of cool to be able to see the end of Stored Image Decoder again.

The 100_percent_v1 achievement is also bugged for me. All my segments are listed as nominal, but I can't get it to pop. I even deleted the personal statistics from the save file and re-ran all my segments again, but no dice. I'll keep testing.

Got 100_percent_v1 to pop finally. I deleted the best/last lines for Stored Image Decoder in the save file. Then I ran Stored Image Decoder again. Saw the <spoiler>, but still no achievement. So I ran it one more time, and then the achievement popped.

You might want to make sure the game is checking for that 100_percent_v1 achievement when it should be. It seems like maybe it's only checking on Stored Image Decoder, and then maybe only the second time you run the nominal solution. It doesn't appear to check after the second time. So if you do the puzzles out of order, you can't unlock that achievement unless you muck with the save data like I did to force the game to check for the achievement.

Cant download game from steam error message says its a corrupted download?

It would be nice if they used x86 assembly language in which case it would also be a teaching aid. It looks like its very loosely based on it?

The game's horribly limited assembly language and computation model is the only reason it's a game at all. If it used x86 assembly language every existing puzzle would be completely trivial (and x86 assembly wouldn't work with the game's current computation model).

why on earth would anybody want x86 assembly in a game?
why on earth would anybody want x86 assembly even in a very boring day job?

Its a puzzle game based on what looks lile a low level assembly language and so why not make it based on a real CPU code. I havn't played it and so maybe I'm missing the point of the game it was just an idea. I keep pondering on whether o give it a go. Maybe spending my time programming something may make better use of my time.

@Krispykrem I had been playing Windows, then intalled on OSX. Game crashes on OSX within the first second of the window appearing.

MacBook Pro (17-inch, Late 2011), OSX 10.10.1.

Heh, using a full set of x86 would make things so much easier. Even if I could use 6502 I could make many of these puzzles work. As it stands, its a unique challenge given a ludicrously limited instruction set :]

how about fix the bug that cause crashing on startup

Wow, these comments are throwing me off.

Please don't listen. The game is awesome, it is challenging, beautiful, moving and inspiring because of its qualities and very clever balance. Thank you so much, I play it every day for a bit and I get immense kicks out of it.

Some folks are missing the point of this game. It's not a programming tool and it's not assembly. It's a puzzle game which is why it only has a few commands that are very loosely based on assembly but they could just as well have used a totally fictional instruction set.

So don't complain that it's limited and should be based on the x86 instruction because it's just a game.

Hey, can we have some nice trading cards/ profile backgrounds for this game? I would love to have one! On my profile! :D

Any chance of a zoom for the graphs showing node/cycle/instruction counts? You cant tell if you're at the optimal point or not with such large numbers on the X scale. Even the node graph is confusing when it goes to just 34!

Nevermind. I just saw the justification for it.