The view from above always makes the most sense. With Medal of Honor: Airborne, industry veteran Patrick Gilmore has looked back over years of virtual war to figure out how, in this golden age of AI and physics, EA’s troubled series can reinvent itself. He could be the ideal candidate for the job. He’s associated as much with Disney as D-Day, having produced over a dozen games starring Mickey and co, he brings a fresh perspective to a series that’s long been considered stale. And despite Airborne’s nonlinear nature, his solutions are surprisingly straightforward.
Aren’t you a bit tired of the WWII genre by now?
Patrick Gilmore: Well, this is the first Medal of Honor game I’ve done since Allied Assault so I haven’t been immersed in it for as long as others on the team. For some this is their fourth or fifth MoH. They’re the kind of people focused on the history, the weapons, the soldiers and the events of the war. Personally, I could imagine getting tired of it someday. Actually I’d get tired of it when I discovered there was nothing new to get out of it.
Is that EA policy - keeping the same team of engineers but rotating the creative leads to keep things fresh?
Gilmore: I think that might have been a big part of it. I was sitting down with one of the producers the other day and - I can’t remember the exact line he said - but he was like: “I’ve just done debugging the weapon files and I fixed all the cluster patterns for the Thompson and I checked the muzzle flash is right and the reload rates...” He just spewed out this technical stuff that drilled right to the heart of the play experience.
What you often get on a franchise like this are the people who’ve gone on the weapon shoots and fired every single one of these weapons. They’ve played paintball, undergone military training or been coached by one of our military advisors to help capture the knowledge of what it’s all about. You don’t want to lose that, right? But at the same time we’re always trying to infuse new energy into the franchise. So I guess it’s not an EA policy but good practice in general for something like this.