Pulse, previously titled Ruckingenur: Puzzle, is the second game in my games for engineers series. In it, you must arrange devices on a grid to redirect and filter pulses in order to achieve different objectives, depending on the mission. It’s sort of like the incredible machine, in that you have to assemble pre-created parts to achieve an effect. Once you get past the training missions, each of the missions (there are two) come in two separate flavors – slim, which contains the exact set of parts required for a specific solution, and normal, which contains far more and allows for open ended solutions.

There are five different kinds of pulses in Pulse: red, green, and blue pulses are considered data pulses, while trey pulses are clock pulses, all of which can be considered signal pulses. The yellow pulses are power pulses, which can not always be routed like signal pulses, and are traditionally used to trigger special features in devices.

One of the biggest problems people seem to have with Pulse is figuring out how to use the data latch. The data latch is used to copy data pulses – to use it, send a data pulse into the left side, storing the color of the data pulse inside the data latch. From that point on, hitting the right side with a clock pulse will cause a copy of the data pulse to bit shot out to the right. To replace the data stored in the data latch, simply send a new data pulse into the left side.

Download Pulse

A screenshot of Pulse in action.

4 Comments to Pulse

  1. May 11, 2009 at 12:26 am | Permalink

    Love it

  2. Nemoricus's Gravatar Nemoricus
    May 19, 2009 at 2:23 pm | Permalink

    For some reason this game won’t run on my computer. It gives an error message as follows:
    “Application has generated an exception that could not be handled.
    Process id=0x8d8 (2264), Thread id=0x2bc (700).”
    Any idea why this is happening?

  3. Michael's Gravatar Michael
    June 2, 2009 at 1:33 pm | Permalink

    I also get an error. It is titled: “ruckingenur.exe – Application Error” and reads: “The application failed to initialize properly (0xc0000135). Click on OK to terminate the applocation”.
    Am I doing something wrong?

  4. Michael's Gravatar Michael
    June 2, 2009 at 1:35 pm | Permalink

    Oops, I spelled “application” as “applocation”. Sorry for that, and the double post…