Graphics 2.0 Migration Guide

Updated: 2013.11.18


This guide is intended for those of you who have existing projects from the Graphics 1.0 engine (builds prior to 2013.2000).

The Graphics 2.0 engine enables a new class of graphics capabilities and features. While we have made every attempt to maximize backward compatibility, we had to make a few changes to graphics behavior that require a break from the past.

Migration Options

For those of you who have existing projects or are nearly finished with one, you have two options:

1. Graphics 1.0 Compatibility Mode

Graphics 1.0 compatibility mode allows you to run your existing project. In many cases, you will be able to run this with no modification (or very little modification). The main caveat is that Graphics 2.0 features will not be supported in this mode (i.e. even if they seem to work, your mileage will vary).

2. Migrating from Graphics 1.0 to 2.0

Porting your existing 1.0-based project requires handling a few behavior changes introduced in 2.0, but doing so allows you to take full advantage of the new graphics features.

Legacy Builds and Documentation

Moving forward, all future daily builds will be based on Graphics 2.0, including new features and improvements. This will also include support for future devices and platforms (i.e. Windows Phone 8).

We understand that many of you may not be able to migrate to Graphics 2.0 immediately. In this case, you can use a 1.0-based public release like 2013.1202. If you're a Pro or Enterprise subscriber, you can also continue to use older Graphics 1.0 Daily Builds.

Legacy Build Numbers

Anything prior to 2013.2000 is a legacy (Graphics 1.0) build. For example, the last public release featuring the Graphics 1.0 engine is 2013.1202.

Legacy documentation for Graphics 1.0 is available here.