Livestream Discovery Scanner 5 - Crafting the Krait MkII with Jordan Clarry and Pawel Ptaszynski
- Thread starter Will Flanagan
- Start date
Cargo hatch and bay attached to it, even prior to Horizons, is PVH isn't it?
Really good stream. But I was a little disappointed you did not explain this...
I did try and asked the question.
I watched the stream later in the evening - the hour went very quickly! Fascinating seeing the design process, thanks.
Rheopectic coffee surely?
The opposite of Ketchup, which is a thixotropic liquid that loses viscosity - becomes runny - under a shearing force (Tomato ketchup shake the bottle. None'll come out, then the lot'll). A rheopectic additive that makes the coffee more viscous under shearing and a vibrating cup, surface tension ought to keep it in?
Just don't add sugar, because - as I'm sure everybody knows - 'kaboom'.
Either that or use one of these? 
Tha
Thanks for not ruining the suspense.
@Will Flanagan I seem to recall other Discovery Scanner episodes having some follow-up Q&A on the forum. Any chance of that with this one? (I guess I understand if the guys are busy tho).
Hi Alec,
I haven't been able to check in with Jordan and Pawel regarding your questions at the moment. We've now let them know, so we'll try our best to answer those questions as soon as we can!
Awesome, you da man Will!
We have answers for you @Alec Turner!
From an art side, the cargo hatch is a similar asset that is used for the planetary vehicle hangar, as long as we’ve made room for the cargo hatch, the SRV bay is also included.
We simply focus on adding polygons in areas which get most screen time, which is common practice for any video game asset.
When designing a ship, we factor in the essential modules right from the start. For example, we knew from the onset that we wanted the Krait MkII to have a fighter bay. As we discussed in the livestream, it was quite a challenge to ensure that the ship still looked slim while fitting a tall structure (the fighter bay) within it.
When the ship was being conceptualised, the artists use volumes of visual blocks for each of the necessary components and then built around them. We generally know which modules a new ship will use before the concept artist begins their design.
Any large design or visual flaws are generally resolved within the concept stage of a ship's design. Smaller issues may persist in a later stage but these are mostly surface level and are resolved in a moment’s notice. We get a lot of information back once the ship is sent off to our QA team, where we then have a decent amount of time to address any issues they discover.
There are many factors that went into the design of the Krait Phantom’s engines. From an in-universe, lore perspective, Faulcon DeLacy wanted to market a new, cooler Krait; they’re trying to sell a product, after all. The engines themselves are actually built from the same components as the Krait MkII’s engines, going from a 2x3 thruster stack on either side of the ship to 9 thrusters on a straight and flat configuration at the back. The thrusters are the same model but the idea is that, like with everything else with the Phantom, thrusters where removed to save weight and make the ship look less bulky and heavy. The flat configuration helped slim the ship down, this, along with the fighter hangar being removed, resulted in a ship that looked visually different from its bigger brother.
David always has a keen interest in what we develop and his feedback is part and parcel in introducing anything to the game.
From an art side, the cargo hatch is a similar asset that is used for the planetary vehicle hangar, as long as we’ve made room for the cargo hatch, the SRV bay is also included.
We simply focus on adding polygons in areas which get most screen time, which is common practice for any video game asset.
When designing a ship, we factor in the essential modules right from the start. For example, we knew from the onset that we wanted the Krait MkII to have a fighter bay. As we discussed in the livestream, it was quite a challenge to ensure that the ship still looked slim while fitting a tall structure (the fighter bay) within it.
When the ship was being conceptualised, the artists use volumes of visual blocks for each of the necessary components and then built around them. We generally know which modules a new ship will use before the concept artist begins their design.
Any large design or visual flaws are generally resolved within the concept stage of a ship's design. Smaller issues may persist in a later stage but these are mostly surface level and are resolved in a moment’s notice. We get a lot of information back once the ship is sent off to our QA team, where we then have a decent amount of time to address any issues they discover.
There are many factors that went into the design of the Krait Phantom’s engines. From an in-universe, lore perspective, Faulcon DeLacy wanted to market a new, cooler Krait; they’re trying to sell a product, after all. The engines themselves are actually built from the same components as the Krait MkII’s engines, going from a 2x3 thruster stack on either side of the ship to 9 thrusters on a straight and flat configuration at the back. The thrusters are the same model but the idea is that, like with everything else with the Phantom, thrusters where removed to save weight and make the ship look less bulky and heavy. The flat configuration helped slim the ship down, this, along with the fighter hangar being removed, resulted in a ship that looked visually different from its bigger brother.
David always has a keen interest in what we develop and his feedback is part and parcel in introducing anything to the game.
Awesome, thanks Will (and thank the guys for taking their time to answer these). I only wish I'd asked better questions now (and/or paid more attention).
