Francesco Roccucci · AI Director

Yeah, so basically it's always Subsumption, but we have two different tools. One is an internal tool, embedded in our editor; maybe we can show it in one session. What that means is we want to be able to reference things directly in the levels, and with the external tool we couldn't do it. So we always had a bit of additional information, the platforms, that were supposed to expose information to the external tool. This one is basically meant to streamline the creation of Subsumption data a little bit. So you can create activities and missions in the internal tool. You can create platforms. And the idea is that all the internal data gets automatically propagated to the tool, without us necessarily having to expose it to the external tool and then use the external tool to do these operations. Apollo also includes some other features that the external tool didn't have, for example the editing of the master graph that Fadi and Michael have been working on. Michael and Fadi are our programmers who focus a lot on tools and systems. We also have, for example, a different view of our missions: in the external tool you have one graph for each logic, and now we have a large graph for the missions where you can see the different blocks. You can collapse them, and it automatically understands what you're linking to. So you can still create different files that people work on at the same time, but it's a little bit more streamlined. You have the full picture of your mission in there. But basically, it's our internal Subsumption tool, and it's meant to grow into giving us more power for editing missions, for example. One thing that we want to do in the future is object containers that can automatically include missions, so we can actually reference data directly from the level.