Backseat Drivers: an interview with Joey Bracken | Ignite Chelmsford


Joey is a writer, director, casting director and actor for video games, commercials, TV and animation. Ignite Chelmsford's Community Manager, Bucky, recently sat down with Joey to discuss his unconventional career path, the nuances of the gaming industry and his most recent work on the co-op driving game, Backseat Drivers.

Your career in games has taken you from voice acting to writing and directing, all the way through to developing video games. How would you describe what you do?
I'd describe it as an absolute privilege!! I constantly have to remind myself that I must never complain. Teenage me's head would have exploded if he knew he'd get to do this for a living.
To answer your question, though, it's not a very straightforward answer, but I'll do my best.
I'm mmmmmostly a writer, director and casting director for games ... who occasionally does some acting. I specialize in the VO workflow, and it's always of benefit to be part of the whole sausage making process so that your work fits in cleanly, which typically means working with audio, narrative, design or level design teams (or a combination) start to finish. Those are diverse disciplines, and that can mean competing priorities, but the people I work with are all so unbelievably smart and capable that it makes my job easy.
The best ideas will win. The process usually starts with figuring out what information needs to be relayed to the player, who'll be doing the relaying, and why. So I'll start with answering some high level questions like: are we trying to move a story forward? Provide some optional background context? Help the player feel a specific emotion? Add color or flavor to a scene? Depending on the goal, I'll approach it differently, but most of the time you want the dialogue to complement the gameplay rather than distract from it. Once we figure out what needs to be said and when and why, I'll write a script (then rewrite that script, and again, yeah, rewrite it again). It's never perfect first time because the best ideas have to gestate and grow, so as new ones hit me I have to put pen to paper right away, and that can happen any time. Usually as I'm trying to get to sleep, annoyingly.

Next, though, if I'm casting, I'll first send a short sample of the script to people in my network for them to try out. That's if I already know anyone I think would be a fit for the character. If the dialogue calls for a natural performance, which most does, it's often better for the actor to be close to the character wherever possible, in attitude and personality. The less "acting" required, the better. That kind of sounds wrong? But I think that's really what good casting is about. I never try to make a square peg fit, so if I don't have a direct line on someone appropriate, I'll work with another casting director to share with their network, or post the role somewhere public. I collect a handful of the best reads, give feedback to anyone I think could benefit from it, and if I'm working with a client or in partnership with a studio, I'll share my shortlist with them to pick their favorite. If it's for one of my own projects I personally have the agonizing task of choosing, which is an unenviable task, let me tell you ... then, it's time for directing (the point at which I stop fiddling with the script, save for if the actor has an idea they want to throw in as we're working through it). If I'm running a directed session, I'll normally join a call with the actor in a recording studio or just at their home setup, and we go through all the lines together with me providing situational context where it's needed, about what the character should be feeling, trying to communicate, or whatever.
You're often trying to cover a lot in the time you've got, whether it's a one or four hour session, so I get quite animated. If words fail me I'll resort to dumb facial expressions, arm flailing, screeching, you know, whatever gets the job done. I'm only half joking on the faces and the wiggling. I try to take pride in my work, so if it gets the point across and helps the actor embody the character to hit the right emotional notes, I'll do it.

Anyway!! If I'm delivering finished audio and not raw recorded session files, it's time to cut. Game engines need audio cut into individual files with tight heads and tails, so that means listening back to the session that you just recorded, of the script you wrote earlier, and snipping out the best read(s) of every single line and saving that to a new file that meets whatever naming convention you're working to. Usually something easy to parse for the people that have to work with it, but nonsense to anyone else, like P1_CH3_G_IN_BUB_03.
You're right though, I don't just work on voice. There's side projects where I get to do a bit of everything. Art, design, levels, scripting. Me and a few friends released "Backseat Drivers" last year. With a small team you've got to roll up your sleeves and pick up whatever slack there is and push yourself outside of your comfort zone. I learned probably more in the year-and-a-bit making that game than I did in the five years before! But that's the best way to learn, I think, jumping in and muddling through as best you can (then going back and redoing what you just did from scratch because you know so much more than when you started). Even stuff you think you wouldn't be able to do in a million years. You'll surprise yourself. And if you struggle, there's a ton of resources out there that'll help you grow in whatever direction you need to.
How did you get started in the industry? Is there any advice you'd give to folks wanting to break in?
Yeah, right, the games industry has a reputation as being super cutthroat and difficult to penetrate... There's thin margins and high operating costs for a lot of developers, so it can be hard to get in and then just as hard to stay in.
I first became aware that voiceover even existed when I was very young, like 4 or something. My uncle Steve ran an ADR loop group that record ad-libbed background voice for various productions. Movies and TV shows, usually BBC ones. He brought me along quite a few times, which is what first exposed me to this whole world. Or, at least, the post-production part of it.
The traditional route from that kind of start would be to do more and more of that type of background work, get an agent, and get larger and larger roles ... that didn't really work for me though. I tried, and it gave me some working knowledge to begin with, but it isn't what got me to where I am now. Probably because I didn't pursue it properly, to be honest. I didn't go to school for acting, or anything like that, so I didn't have the connections or understand what the path into acting and voiceover was even meant to look like.
Instead, starting from when I was about 16, I started messaging and applying to join various mod projects I thought were interesting, like Pirates Vikings and Knights II, or No More Room in Hell. Those are a couple of the more notable ones that somehow thought my performances were good enough. I'd work with them to provide character voice of my own with my bottom-of-the-line recording setup, and to bumble through trying to cast for other roles. It was great, honestly. Those fan projects, with no money involved, can be a lot of fun. Just people getting together to make something to share with everyone else for no reason other than that they think it's cool. They are a fantastic way to learn game dev skills, especially because there's people at different skill levels involved. Some will be really advanced and maybe even professionals working in the industry, but some will be starting out, just like you. So you can learn from everybody. I still work with some people from PVKII and NMRiH to this day, which I think says a lot.
What I haven't mentioned is that there's a lot of hard work. A lot of repetition. You can't just try something once and expect it to be great. You have to try it again many more times than you might expect. You need to practice and practice to become adept at whatever craft. That might sound obvious, but there's no shortage of people that don't seem to know. So, just try things. Start simple. Start at the start. Fail, repeatedly, then try them again. Read every resource out there. Read blogs. Watch all the good tutorials. Then do slightly more advanced things, fail. Repeat. Even when you feel like you're getting nowhere, there's almost certainly been a lesson along the way, even if you can't identify it yet.

Last year, you released Backseat Drivers - a co-op driving game where one person drives and one person yells directions, as your car (and surroundings) seemingly work against you. Can you give us a brief overview of how production went?
It was a lot! A lot of late nights. I happily worked those late nights, though. That project unlocked in me a thirst to really excel, to make something really really good from the ground up.
The initial idea came from my friend and colleague Garrett Lindquist, though I'm a bit hazy on the specific details. You'd have to ask him. But the game's first prototype and a LOT of work came from Max Phillips, who is just absolutely gifted. He's a tech artist, but also a character artist, but also an animator, and a level designer, and a programmer, and and and ... I'd be here all day if I was talking about what he can do. He's got an encyclopedic knowledge of game dev and of the Unreal engine and taught me an incredible amount. And thankfully, he was patient enough to pass on knowledge to me. I understood conceptually all these disciplines and the process, but had never been hands on at this level before. Having someone like him around is a blessing. So, thanks to him, we at GhostJam (the company we developed under, sort of set up as a game dev collective) had momentum on Backseat Drivers from a popular demo that Max and the guys less crushed out incredibly fast. I think there were only about 6 of us, and only 3 of us working on the game full time.
My first time playing the prototype, and many times after that, I was just crying with laughter. So I suspected we were onto something special. Watching the testers play the game together and laugh themselves into coughing fits is what confirmed it.

Working on a game can be a slog at times, because there really is so, so much to do, even with one like this that seems simple. But there is hidden complexity. Devilish complexity! Like, OK, it's a game about an old lady driving a car and can't see where she's going and a little kid in the back has to give her directions. Super simple. Except, how's the car going to move? How are you going to simulate the physics of the items flying around in the car? How do they communicate with each other? How do you reliably replicate everything the game is doing over a networked connection so stuff doesn't go out of sync? All questions that people smarter than me were around to answer, thankfully.
You've got to trust your team, especially when you're that small, and thankfully they are a brilliant bunch.
What's something people don't know about the games industry?
Probably that most games never see the light of day.
Even though there's thousands upon thousands released on Steam every year, there's tons more that never made it that far. It's like what I talked about earlier, with how so much of the process is repetition and incremental improvements ... that's what a lot of games are, especially from solo and indie devs. Just experiments, probably some of them very good, but they never get finished because either they didn't meet the creator's quality standards and they cut their losses, or they learned what they needed from as far as they took it, then moved on. Though there's many that don't make it for sad reasons, and they ... actually, now I'm sad thinking about games I haven't finished.
Can I change my answer?
OK. My new answer is that most people don't know that every game sucks. It's absolute crap, possibly isn't fun, and is probably hideous to look at, all the way from when it starts getting built up to surprisingly close to release. There'll be maddening bugs, non-functional systems, unfinished art. This is why game devs can seem especially "precious" about their work leaking early. They don't want it presented in that state.
And on top of that, I can guarantee that 90% of the games you've played are glued together with barely functioning, sub-par code, and the person who wrote the code was annoyed that they wrote it that way, but they had such a long to-do list that what ended up in the the game is all they had time for. Does it work? "Ship it!"

Your career has taken an unconventional path. Do you think your experience in voice acting gave you any valuable insight when it came to ultimately designing and developing video games?
Hmm. For me, the two are closely linked. Aside from the odd commercial and a handful of other bits and pieces, most of my voice acting work has been in games. Though I'd say it's made me a better listener. I try to listen closely to what people say, and if I've heard them but aren't understanding what they're trying to express, I'll ask a clarifying question. That's a habit I think I developed from listening super-duper hard to actors' performances when directing sessions. I'm listening out there to make sure they nail it, but in other work and in every day life I listen to try to find the root of the point they're making.
You've lent your voice to titles such as Dota 2, Warhammer 40k Warpforge, Chivalry II and many more. Is there a genre, game or character that you'd love to voice but haven't had the chance to yet? And do you have a favourite type of character to voice?
I want to be in a Dungeons & Dragons game. I should've been, by this point. I'd make a great wizard. Or barbarian. Come on, Hasbro, what are you playing at?
Seriously though, I don't think I've done any RPGs? I don't envy the sheer volume of dialogue needed for open-world RPGs (they'll usually have large teams who write for this very reason), but I reckon I'd really shine in one. Cast me as a heel, or a goblin, whatever. I don't care. It's time!

What are you working on at the moment and/or what is your next project?
I'm working on a few secret things with Torn Banner Studios, I've got a great relationship with them and their projects are really varied so I get to stretch all kinds of different writing muscles. It's been such a blast working on Chivalry II, and No More Room in Hell 2, and [secret upcoming project/s]. It's so satisfying and I'm immensely grateful to everyone there. There aren't enough good words to say about them, they're brilliant.
Right now I'm in progress on a game called "Rest Assured" with some friends, it's a third-person singleplayer action-horror game set in 1990 in Washington State. Oh, and also a couple other secret things. And another side project where you run a fantasy medieval postal service ... ahhhhhh, I've already said too much. But it's early days on all those.
Lately I'm trying hard not to work late or get too hyper laser focused on stuff. We just had a daughter this year, so I have a much easier time prying myself away from my messy desk to spend time with her.

And lastly, where can people find your work?
You're reminding me I haven't updated my site or made a new voice reel in aaaaaages. Way too long. But joeybracken.com is where you'll find some semi-recent bits and bobs from the last few years, hear me yelling, growling, etc. None of my game dev stuff is on there, actually. Ahh! IMDb is probably a more comprehensive overview of what I've been in at this point. For shame!! I really have to get my stuff updated.
∘₊✧──────────────────────────────────────✧₊∘
Joey is a writer, director, casting director and actor for video games, commercials, TV and animation. You can download Backseat Drivers on Steam here, and follow more of his work at joeybracken.com.




Comments