Digimask started on the cutting edge of personalization technology and has continually evolved to maintain that position. Looking back over ten years of technical advances and commercial milestones, we are ... (more)

The latest movie in the blockbusting 'Narnia' series - 'Prince Caspian' .  Disney is using Digimask to turn 'YOU' into a Narnian ... (more)

Digimask has recently partnered with Dassault Systemes to bring a Sport-themed application to Facebook users. The Virtual+Reality application turns you into a marathon runner and allows you to compete in ... (more)

Behind the Scenes

By incorporating the SDK library into a game, developers are able to import the DMK head into their game engine at runtime. The DMK data is a compressed, platform independent and proprietary format. Essentially all the SDK does is to decode this data for the developers game engine. The developer passes in the DMK data, the SDK reveals the 3D data. They can then request a DAG with polygon and texture data at whatever resolution suits them. For animation, the heads use influence skinning (bones). This information is then stored by the developer in their own scene-graph. Once all the data is extracted the SDK library can be shut-down (releasing any memory used) and the game can continue without any interference from the SDK.

There are two steps to the Digimask process:

1. Creation. The Digimask Head is created from a front and optionally a side photo of a person’s head. This process happens in what we call the DCP or Digimask Creation Process. The DCP library is integrated into our Launch Pad application (for console use) or installed server-side for fully-automated consumer-convenience.
2. Integration. Once a Digimask Head has been created it is saved into a propriatary (DMK) format. This data can then be passed to the SDK for decoding and integration into your application.