Continuing on from when we last spoke, this post is going to focus on our preparation for part of the tech section of our pitch.
The prospect for any creative team of making a cool, fun mobile app ; seems to be all the rage these days. The first wall many teams run into is the level of programming involved. If that isn’t enough the prospect of writing your own game engine or learning how to use an existing one usually kills off the rest. But not our team. For the past three years we have been studying for our degree in Multimedia Design. We are designers, programmers, writers, film makers and audio designers wrapped up in a nice competitive little package. We are ready.
Being in the role as lead programmer; I was keen to get started and highlight potential issues early on – as to not waste time later on.
My first port of call was to ascertain what can flash do? How does it handle 3d? Can it? What engines already exist?
Over on Adobe’s site, they give a pretty good rundown on all their recognised 2d,3d and physics engines.
Continuing on from this resource I came across another Adobe sister site dedicated to Adobe gaming. This site was particularly helpful as it was more geared towards engines that perform well on the mobile platform.
From this preliminary investigation I already had a pretty good feeling that while Flash may be catching up in the 3d scene, it isn’t there just yet. However I was keeping an open mind about 3D and I chose to take a look at Unity.
We were being to lean back on AS3 with the aspiration of compiling using adobe AIR. Still the question remained; what engine?
This solution is currently being debated but our proposal is to use the Starling engine and the box2d physics engine.
Watch an example of both in action.
Click the html window and use the arrow keys to test the physics engine.
There are 3D libraries for flash like Away3d but like I said, they aren’t at the standard yet.