TL;DRAs Director of Cinematics he co-directs the Squadron 42 performance-capture shoots and leads the team integrating them into cutscenes, most of which are meant to run in real time.
I think one big part would be the actual narrative PCAP that feeds into all the cinematic scenes for Squadron 42, that we actually go to shoot at Imaginarium. So I would accompany Chris as a kind of co-director, basically directing the actors, while I'm making sure that the staging is correct and the lighting looks good. I'm basically like a virtual director of photography.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
So you were there directing with Chris basically every speaking role bit for Squadron, right?
I'm leading the team here, and we are making sure that the PCAP gets integrated properly into our scenes, and it's a bit tricky with our game because it's not just pre-rendered cinematics. We want to achieve most of them in real time. So it's a constant back and forth and handover with the designers that actually make it happen, so that we can trigger it from AI and back and forth.
TL;DRThe shoot was an emotional mix of living the dream and feeling stuck there, with highlights of watching actors inhabit their roles and Gary Oldman asking about how his character would speak.
I had a full range of emotions. It went from living the dream to 'I can't believe I'm still stuck here', because it was so long. I had everything going on. But it was amazing. Especially, my favorite was, I think, both Marks were great, and Gillian, of course. And just seeing them putting on this suit, that humbling suit, which is totally not comfortable, and just playing these roles that we had in the scripts for so long on these pages, and actually getting into these roles in a proper way. Gary Oldman was actually asking things about how would he speak and what is the whole background.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
I do still remember the first time Oldman stepped up on the podium for his very first shot on his very first day. He was just rehearsing, but he was in full character. And everybody was running around, there's 40 people on set moving everything around, and he gave his thing in full volume and everybody stopped. The place was just perfectly quiet and he ran through the entire thing. It was awesome.
TL;DRHomestead aimed to test how mature the planet tools were in artists' hands, so they picked an arid, savannah-highland landscape over jungle, which was held for later, and worked daily with engineers.
I think one goal was we wanted to see how mature our planet tools are when they are actually touched upon by artists, and they actually create something substantial with it that is actually playable. So this is where the idea for Homestead came from. And then we basically went, okay, do we really want full jungle already? And we wanted to keep this for later, because also our asset pool was basically not full jungle already. So we were like, first let's do lots of jungle and trees, and now let's move this to later. And then we were like, okay, what can we really do now that looks really great already, which would be an arid desert planet, but also savannah highlands. So we chose kind of like if you would go to Tanzania, a Kilimanjaro-style landscape. So we picked that, and from then it was basically working with the engineers, Carsten, Marco, Chris Bolte and Sascha, every day, making sure that the newest features are stable and make sense for what the artists need to do.
I think this just became natural, because we wanted to make sure that if we have transitions from three ecosystems into each other, like you start off on a mountain range, go to a rocky plateau, and then into a desert, that this feels cool also if you traverse it as a player. And then we invented some kind of mission goals that you would have in the PU if you actually do this stuff, to push you through the space. And then Todd came on board and actually made sure that it's a proper PU design, a proper mission design. And it basically just evolved naturally.
TL;DRYes, cinematics and in-game use the same face assets, differing only in camera distance, depth of field and lighting, and the faces are so detailed that current face accessories are lower detail.
Yes. The only difference is always: what is your field of view? How close can you get to the guy? Is depth of field on? What is the lighting? These are the same assets. We are not switching to another type of asset if you're in-game.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
I will say that that's fairly rare, at least in my experience: hey, here's a cinematic, now we have a different LOD for the head that's crazy high, or here's the special cutscene head that we're swapping in. But he's absolutely right. Our faces are the faces. And they need to be able to hold up from a distance, and then you need to be able to get close and see them as well.
They're actually so detailed in some cases that our current accessories for the faces are lower detail than the actual faces. So they are very detailed, and in-game you need to really bump into them, really close, to enjoy the detail that they can offer, which is great.
TL;DRThe character and animation departments contribute most, supplying fixes and raw animation, plus tool-side R&D so ships can be moved in cinematics.
It's definitely the character department and the animation department, I would say. Constant back and forth with the character department on, look here, some penetration on the armor, or how can we fix the Snoopy cap, and what is with the hair, and all kinds of things. Animation, of course, because it's actually the raw material of what we're using in the cinematics. Without animation, we wouldn't have anything. We could just show ships drifting around and the characters would be static. And then, of course, there is a certain part that is kind of tool-side R&D, because, for example, our ships need to move in a proper way in cinematics that is kind of puppeteered, almost like remote control. So there's this part of the equation as well.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
And we have a lot of those guys. When characters are created and so on, things get funneled here, and Hannes is working with those various studios, and a lot of things end up getting assembled here. With you and with our lead cinematic designer and the animators here in Frankfurt, you guys end up cramming it all together and throwing cameras in and lighting it and the whole bit, yeah?
We actually did lots of R&D as well on the animation side when it came to what we showed at Gamescom with Miles Eckhart. This was also done by our animation department here that is attached to cinematics.
TL;DRRocks, trees and bushes are populated automatically anywhere on the planet, while content like crashed ships is currently hand-placed, with logical automatic distribution still being researched.
So what we have is basically two types of dressing currently with our planet. One is we can just populate everything with a certain rule set for rocks and trees and little bushes and everything. That's totally automatic. So if you go to a different location on the globe and jump into a forest, it looks populated already. The content currently needs to be hand-placed. If there's a crashed ship, we hand-place it in a certain area that we find suitable. There's a real sense of adventure going on. If you have this 1,000-kilometer diameter planet in front of you and you're actually scouting, you're actually flying around: this would be awesome as a landing site for pirates. We will basically have these bubbles of content, like a crashed Javelin or a crashed little Cutlass, whatever, and these get, currently at least, hand-placed. We are also thinking about distributing them logically, of course, because planets are so big, but this is ongoing, so they need to do lots of R&D for that, so that we basically don't place a Cutlass where it's floating in the air, or in a canyon that you can't reach. There needs to be a certain logic rule set for that, so that it actually works properly and reliably.
TL;DRHe's confident about the very large number of Squadron 42 scenes, which mostly keep the player's viewpoint and agency, with full filmic cutscenes a small part and a balance between design and cinematics ongoing.
So there's lots of things going on, but for example, we have lots of scenes that are comms calls, and these comms calls are kind of easy to set up. So there's a big chunk that is comms calls. Then there's lots of scenes that are kind of drifting into gameplay territory, where we are just helping out or supporting. And then, of course, there's a big bulk of scenes that are the social interaction, interstitial scenes during each chapter, which is a big part of the story. And then a small but very important part is the full-on filmic cinematics, which is the stuff that is the most fun.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
Those are the ones you always get excited about the most, right?
If I have control over the camera, I'm in love. Because then I can get really close to the characters, I can change my lenses and everything. But our rule set for Squadron normally is: if we can do it, it should be coming from player agency. We still stay in the player's eyes. We have some cases where, if the player is not present in the scene, yes, we will cut to this, and then we can cut to it filmically.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
That's interesting to note, that we're doing as much as we can to keep control in the player's hands. Even though there were some, as we were talking them through, where we kind of had to take control away from the player, we didn't want to completely, so we put them on rails. But again, there's so many of these that are interactive, if you will. Somebody approaches you and, hey, I can go this way and hear part of the story, I can go that way and come back to this later if I want, but you're making a choice, and whatever choice you make, something new clicks off and you run down that route.
I'm fighting a constant fight. Some gamers out there probably are like, oh god, this guy is a cinematic guy. He will fight for quick time events and framing dead bodies instead of actually discovering them, and stuff like this. But there's this back and forth between design and our department where we went through these scenes: does it make sense to take away the camera for a certain bit and only give you look control? Or do we want to give you full freedom, but then can we funnel the player into a certain view? It's an ongoing process, but I would say I'm happy about the balance that we have in the game. It's definitely not something that's constantly on rails, or complete freedom.
Camera shake, all the stuff, all the cameras get set up in CryEngine. The characters get set up in CryEngine. Of course, we're using Maya to feed the animation into CryEngine.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
Yes, partly MotionBuilder. Of course, we do texture work. Certain assets are then done in Substance Painter. We have a timeline tool in the engine, [so we don't] need to actually stage the cinematics in Maya with a camera or something like this. This is a really big advantage of our engine as well, and we should make use of it.
TL;DRWhen the player is present, scenes are from their viewpoint with at least look freedom, and only some key story moments, like a briefing, seat the player.
We kind of answered this, but basically the rule of thumb is: if the player is present and he's not knocked out or something, then it's from the player's point of view, and he at least has look freedom. Most of the time he has full freedom. When conversations happen, we will at maximum lock the player in a soft lock. He can still back away from the conversation. But for some important things, like you get a briefing with Mark Hamill in the briefing room, we actually sit you down in the chair to watch the briefing.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
There's certain elements we need to give the player in order for them to move. Even if that's just a few pivotal ones, they need that information to know that they'd better do this thing or this bad thing is going to happen.
Our captains for the hub ships, at least we captured it and it's pretty cool: [if you behave] too much like a jackass on board and not like a military officer, then you land on the bridge and the guy is basically like, I had high expectations for you and you disappointed them. So there will definitely be the opportunity to also behave like a creep or a bunny-hopping idiot. But in some crucial scenes where we want to get the story across, we say no. We don't want to have key characters dying or something and the player is concerned.
TL;DRHe rates the old Bishop speech's facial performance at roughly 80–85% but the asset only about 60% due to technical issues, and says it will be re-rendered with the much better current Bishop.
The performance itself was pretty good, but we had lots of technical issues. I can name a few. I think some normals on his face were inverted. We had the wrong type of skinning. The hair was really not good, and his uniform was just the first pass. From an asset point of view, it was not really that great. So I would probably say facial performance maybe 85% or 80%, and what the asset actually looks like maybe 60%. So he looks much better now. Of course, at one point I need to go back and re-render this, because this will also be game content that you can actually view on TV screens. So it will definitely be re-rendered with the latest Bishop, much better.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
The reason why I ask is I've seen things deforming a lot better, and new shaders on the eyes, and once you see things actually firing off the way that they need to as a one-to-one, some of the stuff I've seen has been nuts.
Our problem is always that we kind of make it look polished, but of course it's an ongoing process. There's lots of things that you still need to work out, technical things. For example, a month ago we got something really amazing from Jeff, one of the graphics programmers. Before that, in CryEngine the eye shader was always just giving these little dots, no matter how big the light source was. And now, if there's a big area light in front of the character, we actually see it reflected in the eye. Way better than before.
BC
Brian ChambersDevelopment Director, Foundry 42 Frankfurt
It's amazing to me how just that simple thing, when I walked in and saw that face on your screen, it's immediately noticeable. Sometimes it adds something where you're like, wait, what's different? You may not even know and recognize it.
The eyes especially, you always know that something's wrong with them, but you cannot really tell. The eyes are something that humans, since they are babies, can immediately recognize what's off there.