Prototype

Trace wants to know less about the games I play, and more about the games I work on. 🙂 I joined Radical Entertainment to work on the Advanced Technology Group (known as ATG). We create the technology (the "Titanium" engine) that all game teams at Radical use to create their games. Radical’s ability to make that happen was one of the things that attracted me here. As I learn more about how they got to this point, I realize that it has been far from easy, but it’s not an impossible task like *ahem* previous experiences might suggest.

Prototype is the first "proper" next-gen game that Radical will release. Read the articles and coverage in the net for more details, because I don’t really know what is public and what isn’t. 🙂 All I will say is that the game is shaping up quite nicely, and even if it’s still a long way before it’s finished, it has the potential to be one of the most fun and thrilling games of this-next gen.

This entry was posted in Uncategorized by Jare. Bookmark the permalink.

4 thoughts on “Prototype

  1. More details about the ATG would be nice… 🙂

    Did the team start in parallel with a videogame? What methodology are you using? How is the team structured?

    etc, etc…


    ent

  2. Sure, it would be nice to get a lot more info about ATG.
    And even nicer to publish all the source code here too.

    Or maybe this is not a "learn how to do common tech" class.

    Cherno

  3. Hehehe Cherno always so nice and kind… 🙂

    Anwyay, ATG essentially follows (loosely) the Scrum methodology. No long-term monolithic Gantt charts, rather a clear vision of the general goals (features and dates they are needed), and a flexible approach to medium and short-term planning. There’s the teams you would expect: low-level platform, rendering, online, physics, tools, etc, but there’s a good amount of cross-pollination between teams. ATG lifts and refactors stuff from games, and also develops new pieces from the ground up based on projected needs of the game teams. Titanium evolved over the years from a set of separate libraries and tools to a cohesive engine, toolset and processes / guidelines.

    I imagine you nodding as if all this was obvious. And it probably is. 🙂 Actually making it happen is the hard part… and not just from the technical point of view. 😉

Comments are closed.