Download the release from scene.org, unzip it, and look inside before you run anything. There is one executable of about a megabyte, a folder of meshes, a folder of images, an MP3. And then there is a directory called cgeffects holding three hundred and thirty-three shader files, sitting there in plain text, readable in any editor. They are not compiled into the binary. The demo translates them while it runs, which means the entire visual language of the production is lying open on your disk, with the author's commented-out experiments still in the margins.
That is unusual, and it is a consequence of the way this group works.
Watch it first: Rupture on YouTube, six minutes and forty-two seconds, or fetch the executable from scene.org and run it yourself.
The group that never built a tool
By 2009 the demoscene had settled into a working method. You build an engine, then a demotool on top of it: a timeline, a curve editor, a preview window, something that lets a designer place a camera without touching a compiler. Farbrausch had werkkzeug, Conspiracy had apEx, Fairlight and CNCD had their own. The tool is the real product; the demos come out of it afterwards.
Andromeda Software Development, from Katerini in northern Greece, went the other way.
They had been at it a while by then. The group formed in the autumn of 1992 under a different name, writing games and applications before demos; Amoivikos joined as a graphician within a year or so. When Navis moved to England in 1996 the Greek scene went quiet, and the group came back to life in 2001. By the time of Rupture they had sixty-eight productions behind them and a habit of winning: Iconoclast took Assembly in 2005, Lifeforce took it in 2007 against Fairlight and CNCD, and Happiness Is Around The Bend and Spin would take it again in 2010 and 2011. Navis, who writes almost all of their code, put the reasoning plainly in an interview: building a demotool good enough to recreate every ASD demo so far would be an enormous task, probably harder than hand-coding them was in the first place, and he would rather not spend one or two years writing tools when four or five good demos could exist in the same span.
So Rupture is hand-written. His description of the method, given for the previous production and which he says applies to all of them, is a shader loader, a texture loader, a 3DS loader, and after that a great deal of hardcoding. No wrapper for cameras, no abstraction for clearing buffers, nothing between the author and the graphics interface. Straight OpenGL calls of the kind you would find in a four-kilobyte intro, in a production that weighs twenty-five megabytes.
He also names the cost, which is the part that makes the choice interesting rather than merely contrarian. Without an editor, he says, the others in the group sometimes cannot get very involved in directing a demo, because there is no interface for them to work in, only his notes in the form of obscure code. Seven people are credited on Rupture, and the shape of the film sits in one person's source tree.
What six hundred seconds of hand-written code looks like
The demo opens on structures that come apart. A city block dissolves into its own wireframe, a helicopter breaks along lines that were never drawn as geometry, a train runs through a landscape that keeps rebuilding itself in front of it. There is a boat at four minutes and fourteen seconds whose entry another coder singled out, Íñigo Quílez, who called the transition and the camera work excellent.
The technique underneath it is visible in those shader files. The names read like a catalogue of the era's best post-processing: depth of field, motion blur, circular and anisotropic blurs, halftone rasters computed per colour channel, posterisation, dithering, refraction, projective texturing. A great many of them carry projection or anisotropic in the filename, and that is the look people described at the time as the graphic filter, the thing that made an ASD frame recognisable across a hall.
Navis wrote on Pouët that these were, in his knowledge, wholly new effects, naming the wireframe generation and the boolean geometry operations. A commenter pushed back: boolean operations had been around for years. His answer is worth reading for its tone as much as its content. The operations here are not really performed on geometry, he wrote, but done as a trick in the shader using the discard command, and he was not claiming to have invented anything, only that he had not seen it done that way in a demo before. Another coder, ryg of Farbrausch, added that an earlier production had used alpha testing to the same end. Nobody was wrong, and nobody made a scene of it.
The borrowings are stated openly too. Navis lists them himself: the camera shake comes from Debris, and the films Mad Max and The Duel are in there.
That Debris reference has a history behind it. In an interview he describes the day his daughter was born: he stepped into an internet café, watched Farbrausch's Debris for the first time, and walked back to the hospital with his heart sunk, thinking the bar had just moved out of reach. He puts the feeling in its place a few sentences later, calling it peer pressure he shed after a couple of days, on the grounds that a group has to do what it does and stop watching the others. Two years later he quotes the camera he had once found intimidating, and says so in public.
Two musicians and a real guitar
The soundtrack is called Throw Navis Off The Train, and it runs 401.66 seconds. The demo runs 402. It ends when the song ends.
It was written by aMUSiC and Leviathan together, which in this group is not a division into melody and accompaniment. Leviathan described the arrangement when somebody asked: the tunes they make, they both collaborate on, meaning he works on the track itself alongside the other rather than laying guitars over a finished arrangement. The guitars are played rather than sampled, on an Ibanez seven-string, which aMUSiC confirmed when a listener assumed they were synthesised. The vocals are by Liska, who is Navis's wife.
The soundtrack was also where the criticism landed, and this is a group that answered it. One viewer found the music misplaced. Leviathan's reply was that he refused to become a pop act for the sake of votes, since metal is what he has in his veins. Another noted that the boat had no engine sound; aMUSiC gave three answers, the third being honest, that the effect went in twenty minutes before Navis left for Norway and was unpolished. He released an improved mix afterwards.
Other criticism exists and deserves to be reported straight. Some found the demo becalmed in its later stretches. One thought the shader set had appeared in so many ASD productions that it was becoming a house style. These sit in a comment thread of four hundred and ninety-nine entries, which is itself a measure of how much the production was discussed.
Hamar, April 2009
The Gathering happens each Easter in the Vikingskipet, the Olympic speed-skating hall in Hamar, and it had been running since 1992. In 2009 the theme was Fire and Ice. Five thousand two hundred seats, filled every year since 1998 with more demand than places.
It was also, by then, a party where the demoscene was no longer the main event. Much of the European scene spent that same Easter at Breakpoint in Germany, and one commenter said as much afterwards: ASD could have released this anywhere and it would have won anywhere. The competition rules allowed sixty-four megabytes and eight minutes, and scored two thirds by audience vote and one third by jury. Rupture used twenty-five megabytes and six minutes forty-two.
It won with 539 points. Quantum, by Nazareth Creations and Outracks, took second with 403. The margin is a third of the winner's own score, in a field of ten.
Then the awards arrived. At the Scene.org Awards for 2009, Rupture took Best Demo, Best Direction and the Public Choice, with further nominations for effects, graphics and soundtrack. In the direction category ASD had two entries on the shortlist, since Chameleon had won at Evoke four months later in the same year. One group, two first places, one calendar.
The person who ran the competition that year left a note in the thread saying that being able to put this in front of the Gathering audience made the whole party worth the work.
The reaction from other coders is the part worth quoting. One called it top-notch across idea, style, graphics, music and flow, noted that it kept its frame rate even at the highest resolutions, and predicted it would be the benchmark for 2009. Another wrote that the wireframe generation and the boolean operations were obvious to anyone who works with 3D, and that it had been a rare occasion in recent years where he watched a demo and asked how. A third put his finger on why the audience reacted: the group had impressed people past the point where somebody says that games do it better.
Navis wrote his own note after coming home from Norway, and it is the most human line in the whole thread. He said he would spend a few days in a melancholic, post-natal sort of mood, the kind he was sure everyone gets after finishing a big production, and that the reaction balanced it out.
The limit
The method has an edge, and Navis named it himself: no editor means the rest of the group cannot easily shape the film. Six other people are credited on Rupture, and the direction sits with the one who holds the compiler. Whether that is a price worth paying is a question every small team eventually argues about, and this group answered it with sixty-eight productions across three decades, which is at least evidence.
The source of the C++ side has never been published, so the shaders are as far inside as anyone gets. Whether the executable still runs on a current machine is untested here; there were already startup failures on certain cards in 2009.
And the title has never been explained. The archive and the executable both say Rapture, as does the filename on scene.org. Inside, the description file and the window title say Rupture. People asked on Pouët at least three times, in 2009 and again years later, and the group never answered.
Sixteen years on it sits at number twenty-six of everything the scene has ever registered, and somebody left a comment last year saying that the play with form, so unlike anything else at the time, gives it something that makes it hard to walk past.
Three hundred and thirty-three shader files, and no tool to show for them.