UDK New Build Workflow

Document Summary: This page informs you on what needs to be done to move your files over to a newer build.

Steps to migrate content:

    1. Install new UDK build

    2. Copy all the content you've created or changed from the old build to the new build

    3. Run the new UDK build

    4. Test new UDK build

Tips

We suggest using a diff program to help you out. Diffing is an automated way to tell which content has changed from one folder to the next. It is explained in detail here - http://en.wikipedia.org/wiki/Diff.

There are several applications to do this such as Beyond Compare (http://www.scootersoftware.com/) and free ones such as http://meld.sourceforge.net/ or http://sourceforge.net/projects/tkdiff/.

When installing the new build you will want to make sure you are placing it into a different directory than the previous build. New UDK builds will have a default install directory that is named the same month it was made for (for example: The November 2009 UDK build default directory would be C:\UDK\UDK-2009-11).

In development you will reach a point where you will want to stay on the same build. This is perfectly ok. Anything you create from the UDK will be a stand-alone install and will not require anyone else to have the latest UDK, or even have the UDK at all.

Do not uninstall the older build until you made sure the new build works. Check new build thoroughly before making a commitment to it.

When moving files over make sure to place your content into the same folder structure as they were in the previous build.

You can keep older UDK builds around as well.

Stay up to date on the latest UDK build by signing up for the email list.