When Animation Was an Engineering Problem
Animation Obsessive's deep dive into Jordan Mechner's rotoscoping work for Prince of Persia is, on its surface, a history of one developer's quest to make a tiny character move convincingly on antiquated hardware. But the piece is really about something more fundamental: the relationship between artistic vision and technological constraint, and how the latter can paradoxically sharpen the former.
Mechner started making games on the Apple II as a teenager in the early 1980s. By the time Prince of Persia shipped in 1989, that machine was already a fossil. The article emphasizes just how limited the platform was.
The Apple II's memory was 48K. That's less than a normal text email.
Within those 48 kilobytes, Mechner set out to create what he believed would be a breakthrough in character animation. His ambition was not modest. He wrote in his journal during development that he expected something unprecedented, even knowing the visual limitations were severe.
The figure will be tiny and messy and look like crap... but I have faith that, when the frames are run in sequence at 15 fps, it'll create an illusion of life that's more amazing than anything that's ever been seen on an Apple II screen.
That phrase -- "illusion of life" -- is a deliberate echo of the Disney animation bible by Frank Thomas and Ollie Johnston. Mechner understood, even as a twenty-something amateur, that believable movement transcends resolution and color depth. The article makes this point repeatedly, and it holds up.
Rube Goldberg Rotoscoping
The most compelling section of the piece details the absurd chain of analog-to-digital conversions Mechner engineered to get his brother David's movements into the computer. The process for Prince of Persia went roughly like this: film a teenager in a parking lot on VHS, play back the tape on a VCR, photograph the paused screen with a 35mm Nikon, develop the photos, outline each frame with Magic Marker and Wite-Out, Xerox the results into clean silhouettes, then digitize each sheet one at a time using a CCTV camera connected to a special card in the Apple II.
The whole procedure took months. Each step introduced degradation and required manual correction. It is, by any modern standard, an insane workflow. But the article treats it with appropriate reverence rather than irony, because the results were genuinely remarkable. The character's run, jump, and sword fighting all carried a weight and naturalism that no hand-animated sprite of the era could match.
Mechner's earlier game Karateka had used a similar but slightly less convoluted process -- tracing Super 8 footage onto paper via a Moviola, then digitizing with a VersaWriter tablet. Even then, the difference between hand-animated movement and rotoscoped movement was dramatic. As Mechner recalled about studying the source footage of his karate instructor:
I remember the frame of the high kick, the fighter leans back and also the arm goes back. ... In the beginning, when I tried to do a frame of a high kick, you know, it was more idealized. I didn't realize that the body would have to move quite that far back.
This observation gets at something important about human perception. People cannot always articulate what makes movement look right, but they can instantly detect when it looks wrong. The subtle counterbalance of a body during a kick -- the torso leaning back to compensate for the extended leg -- is something animators miss when working from imagination alone. Rotoscoping captured these details automatically, even through Mechner's degraded pipeline.
The Disney Connection Mechner Did Not Know He Was Making
The article notes that Mechner's rotoscoping technique originated in animated films, citing Disney's Snow White as a precedent. There, animators traced live-action footage of actors but then deviated from it -- tweaking proportions, removing frames, keeping only the strongest poses. The article states that Mechner "didn't know that yet" when he started rotoscoping for Karateka.
This parallel discovery is worth pausing on. Mechner arrived at a technique independently because the problem demanded it: how do you create convincing human movement when your own drawing skills are not up to the task? Disney's animators had faced the same question decades earlier and reached the same answer. The convergence suggests that rotoscoping is not merely a shortcut but something closer to a natural solution for bridging the gap between artistic ambition and manual skill.
A counterpoint is worth raising here. Rotoscoping has always had critics in the animation world. Some animators view it as a crutch that produces movement that is technically accurate but lacking in the exaggeration and timing that make great animation feel alive. Disney's own team used rotoscoping as reference material, not as a direct trace, precisely because unmodified rotoscoped movement can look eerily flat -- too realistic to feel animated, but too simplified to feel real. Mechner's work arguably sidesteps this criticism because the Apple II's extreme visual limitations imposed their own abstraction. A character rendered in two colors at fifteen frames per second cannot look uncannily realistic no matter how good the source footage is. The rotoscoping provided the skeleton of natural movement; the hardware imposed the stylization.
Why the Animation Survived
Prince of Persia was ported to dozens of platforms over the years. The visuals were redrawn repeatedly for better hardware -- more colors, higher resolution, smoother frame rates. But Mechner's original animation data, derived from his brother's movements in that parking lot, remained the foundation. The article makes a strong closing argument about why.
Making the animation believable and exciting wasn't really about tech. Despite all the tricks Mechner used for it, this was an artistic problem.
This is the central thesis, and it holds up well. The great irony of Mechner's work is that the most technologically laborious part of his process -- the months-long chain of filming, photographing, tracing, and digitizing -- produced something that was fundamentally technology-independent. Good movement is good movement. The 1937 animation in Snow White still reads as graceful. The 1989 animation in Prince of Persia still reads as athletic and alive. Neither depends on its original rendering technology for its impact.
The article also captures an appealing detail about the combat animation. When Mechner needed sword fighting for the game, he turned to classic Hollywood swashbucklers and found his answer in The Adventures of Robin Hood. Six seconds of the film's climactic duel, shot in exact profile, gave him what he needed.
I did my VHS/one-hour-photo rotoscope procedure, spread two-dozen snapshots out on the floor of the office and spent days poring over them trying to figure out what exactly was going on in that duel, how to conceptualize it into a repeatable pattern.
The image of Mechner on his hands and knees, studying Xeroxed stills of Errol Flynn's swordplay, trying to reverse-engineer choreography into a game loop, is a vivid picture of creative problem-solving under constraint. He was not building a motion capture studio. He was using a VCR, a camera, a Xerox machine, and his own pattern recognition to extract the essence of cinematic combat.
What the Piece Leaves Out
Animation Obsessive is thorough on the technical history but lighter on the broader legacy question. Prince of Persia's rotoscoping technique influenced a generation of game developers -- notably Eric Chahi's Another World and Delphine Software's Flashback -- but the article does not trace that lineage. It also does not engage much with the eventual obsolescence of 2D rotoscoping in games, as 3D motion capture took over in the mid-1990s. Mechner himself moved to 3D with Prince of Persia: The Sands of Time in 2003, which used conventional motion capture rather than the analog chain he had pioneered.
There is also a fascinating class dimension to Mechner's story that goes largely unexamined. He had access to expensive equipment -- a VHS camera (which he admitted he returned after use), a Nikon, a Moviola, multiple Apple II peripherals -- and the leisure to spend months on a single game. His father suggested the rotoscoping approach and even wore a gi to serve as a movement model. This was a young man from a supportive, resourced family, not a scrappy outsider working with nothing. That context does not diminish the achievement, but it complicates the narrative slightly.
Bottom Line
Animation Obsessive delivers an exceptionally well-sourced account of how Jordan Mechner solved a problem that should have been impossible: making a two-color character on a 48K computer move like a human being. The piece is strongest when it lingers on the physical processes -- the parking lot shoots, the Magic Marker silhouettes, the Xerox machine -- that turned real movement into digital animation. Its core argument, that great animation is an artistic achievement rather than a technological one, is convincingly demonstrated by the fact that Mechner's work from 1989 still holds up nearly four decades later. For anyone interested in the intersection of animation, game design, and creative constraint, this is essential reading.