[MM#06] Limits of Porting Arcade Games (Patreon)
Content
The project was finally set to begin: porting the arcade game Trojan to the Famicom.
The process of transferring an arcade board game to the Famicom is called “porting” or “conversion.” All the graphics had to be remade for the Famicom, and much of the programming also had to be rewritten to match the hardware.
The production team consisted of me, a background (BG) graphic designer who had joined the company just a few months earlier, and our department head, who would handle the programming. The music would be created by Capcom’s in-house sound team.
At first, I thought this team size was just how it was supposed to be. True, the arcade division in the same office usually had around ten people per team, but compared to arcade hardware, the Famicom clearly had different data limits and drawing methods. Since we were basically rebuilding an arcade game rather than making something from scratch, I assumed the workload would be lighter.
Even so, it was my first assignment as a planner. Nervous, I went into the initial meeting with the lead programmer, only to be told:
“We’ll handle the settings based on the arcade version. You just focus on the characters.”
Since the content was the same despite the different hardware, maybe a new design document really wasn’t necessary.
In the end, I was tasked with simple screen transition effects and the pixel designs for the moving characters, known as sprites, while the new designer, F, would handle the backgrounds.
F was a year younger than me, a very quiet and composed guy. Like M.K., who had joined the company at the same time as me, F had extensive knowledge of computers and games, and quickly became a reliable colleague I could depend on.
Once the actual work began, however, several unexpected problems appeared. The biggest one was that there simply wasn’t enough graphic data to display on screen.
It wasn’t just that the overall data capacity was small—the real limitation was the amount of graphic data usable at one time. For example, imagine a house displayed on screen. That one house could use up all the available data capacity for display. If you tried to add another house next to it, it wouldn’t appear. Even if there was free capacity overall, the Famicom hardware couldn’t handle more display data. The only way to show a second house would be to erase the first one and load new data.
To create a townscape with multiple houses, the only option was to reuse the same house graphic and line it up repeatedly. That’s why backgrounds in Famicom games often look repetitive. The same was true for moving characters—you couldn’t have too many different types of enemies on screen.
This is why you often see repeating background tiles or the same small enemies appearing in sequence in Famicom games: there was a strict limit on how much character data could be used. And on top of that, the total memory was so small that if you tried to build the game the same way as the arcade, you wouldn’t even finish the first stage.
The backgrounds in Trojan consisted of rows of ruined buildings. Simply repeating wall textures wasn’t enough to capture the atmosphere of decay and filth. We had to carefully allocate the limited data across stages, and then find creative ways to depict the ruined scenery within the tiny amount of graphic data that could be displayed.
F was at a loss. Looking at the arcade version, it became clear that recreating the same backgrounds on the Famicom was impossible. What I had first imagined as a simple graphic task was quickly turning into a tough job of figuring out how to allocate data efficiently.
* * *
The project had started in early spring, and by now the season had shifted to damp, humid air. Looking up at the cloudy skies of the rainy season, dark clouds hung low every day, ready to burst into rain.
On my way back to the planning office from an errand, I ran into M.K. in the hallway.
“Hey, good work.”
“…Oh.”
He lifted his head at my voice, but he looked downcast.
“What’s wrong? You look gloomy.”
“The section chief just called me in. He told me…”
“Told you what?”
“That I’m going to Consumer, too.”
“Oh, I see.”
“….”
His silence and the way he hung his head bothered me.
“What is it?”
“You.”
“Huh?”
“Are you really okay with being dumped onto consumer games?”
“Dumped?”
“Was I really disliked that much…?”
“What do you mean, ‘dumped’?”
At the end of the hallway, I could see dark gray clouds being swept by the wind.
“You really don’t know?”
“Know what?”
“They say the arcade division got all the skilled planners and character designers, and the leftovers were dumped onto consumer games.”
“Leftovers? You mean us?”
“Yeah.”
Even though people said we’d been dumped, my desk never moved — only my assignment changed to consumer games, so I never really felt that way.
“I’ve never heard that rumor. Don’t say weird stuff like that.”
"Didn't the section chief had hate you?"
“Huh?”
“You’ve acted cocky since you joined.”
“No way.”
“You keep getting scolded for eating bread at your desk in the morning.”
“That has nothing to do with it.”
“Look, when you don’t agree with the higher-ups, it shows on your face right away. You’re easy to read.”
“…Really?”
It felt like M.K. was venting his frustration at me, just to hold himself together. But honestly, I couldn’t really understand his feelings.
I had never openly opposed a superior or said anything strange. Sure, I wasn’t blindly obedient either—I would often ask questions about my assignments on the spot. Maybe that did make me a bit of a troublesome subordinate.
Looking at M.K., eyes downcast, I asked honestly:
“Is Consumer really that bad for you?”
“….”
“Well, I mean, in terms of game quality, it’s obviously below Arcade. It’s basically kids’ toys.”
“It’s Jyari-Ban.”
“Huh? Jyari-Ban?”
“Yeah. In the TV industry, they call tokusatsu hero shows ‘Jyari-Ban,’ because they’re just childish programs for kids.” (*Jyari = derogatory slang for kids, Ban gumi = TV program)
“So you think Consumer games are the same?”
“What’s the point? Arcade is getting stronger and stronger, with more chips and better graphics. There’s no way that stuff can be ported to the Famicom!”
“….”
I couldn’t argue back. Even with the sprite designs I was working on for Trojan, I wasn’t satisfied with the results.
The window glass rattled as the sky grew darker. Rain had started falling. M.K. crossed his arms, I stuffed my hands into my pockets, and we both stood there listening to the sound of the rain in silence.
Unable to bear it any longer, I spoke up.
“I don’t really know much about games.”
“….”
“You have a computer, right? Show me some of your PC games next time.”
“Uh… sure, I guess.”
“Consumer is completely different from Arcade in specs. I’ve got a lot to learn.”
“You really are a strange guy.”
“Why?”
“Everyone else avoids Consumer, but you’re so eager about it.”
M.K. looked up at me curiously.
“Just imagine it. The games we make actually become products. They’re advertised in magazines, maybe even on TV. Our games line store shelves around the world, and kids everywhere play them. Just imagine it! We’re doing something amazing here!”
“….”
M.K. stayed silent, watching the rain hammer against the window. On his serious face was an expression that seemed weighed down by complicated feelings.
(Automatic translation by AI)