Search Unity

We are pleased to announce the full support for Windows Phone 8.1 and Universal Windows Applications with the release of Unity 4.5.3. We’ve been working very hard to put our finishing touches on it since its beta program announcement back in April. It is available for download today!

What is it all about?

With the help of Universal Windows Applications, you can now build your Unity game once and target all Windows devices – desktops, laptops, tablets and phones running Windows/Windows Phone 8.1 or higher. On Windows devices, Universal Apps behave identically to Windows 8.1 apps, which Unity has supported since 4.3. On Windows Phone devices, Universal Apps run as Windows Phone 8.1 apps, which is a new feature of Unity 4.5.3.

Figure 1. Universal Applications build window

 

 

What does Windows Phone 8.1 bring to table?

If you worked on Windows Phone 8 and Windows Store games in the past, you know that even though the two platforms are similar, they still have their differences. With Windows Phone 8.1, that changes. There are no longer two separate platforms; they have converged to a single one. To reflect that, building for Windows Phone 8.1 is located under Windows Store platform in our Editor.

Other features of Windows Phone 8.1 player include:

  • Access the full power of .NET 4.5.1 in your C# scripts (Windows Runtime APIs, async/await, etc.);
  • Efficient multithreaded renderer – up to 33% less time per frame (measured on Angry Bots on Nokia Lumia 520 running Windows Phone build 8.10.12359.845);
  • GPU profiling is now available thanks to a new graphics driver for Windows Phone 8.1 (On devices which received the driver update).

Figure 2. GPU profiler running on Windows Phone 8.1

 

 

How do Universal applications work?

Universal app Visual Studio solution

Figure 3. Universal app Visual Studio solution

 

 

So what does the name “Universal” mean? When you press build, Unity will generate a Universal app Visual Studio solution, which will contain 3 projects: ProjectName.Windows, ProjectName.WindowsPhone and ProjectName.Shared (as illustrated in Figure 3).

The shared project, as its name implies, contains all the shared elements: XAML layout, Unity data and asset files.

Target specific projects (ProjectName.Windows and ProjectName.WindowsPhone) contain platform specific files: application manifests, icons, splash screen and tile images. Since Windows 8.1 and Windows Phone 8.1 aren’t binary compatible, each project will also contain their own set of DLLs. Fear not – Unity will automatically make your managed plugins compatible with either target.

When you press the deploy button in Visual Studio, only the necessary files will get copied to the target device (or local machine, if you prefer), thus minimizing the application size which the user would have to download from the Windows Store.

Great, what do I need to get started?

You will need:

  • Unity 4.5.3 or later;
  • Windows 8.1 (any edition);
  • Visual Studio 2013 with Update 2 installed (Express for Windows, Professional, Premium or Ultimate edition).

If you want to test your application on Windows Phone 8.1 emulator (rather than a physical phone), you’ll also need:

  • Windows 8.1 Pro;
  • At least 4 GB RAM;
  • CPU that supports Second Level Address Translation (SLAT) and Data Execution Prevention (DEP).

As always, before updating Unity, backup your project and don’t forget to read the docs:

http://docs.unity3d.com/Manual/WP8-1.html http://docs.unity3d.com/Manual/WindowsUniversalApps.html

Have fun!

17 replies on “Introducing Universal Windows Applications in Unity”

[…] the Universal Windows project in Unity to create a new game for Windows and Windows Phone. Step […]

How does the access from .NET 4.5 to Unity MonoBehaviours work? And can it be modified to somehow allow .NET 4.5 on regular Windows standalone apps?

How does the access from .NET 4.5 to Unity MonoBehaviours work? And can it be modified to somehow allow .NET 4.5 on regular Windows standalone apps?

[…] Universal Apps in Unity – Unity Blog […]

[…] Universal Apps in Unity – Unity Blog […]

[…] Universal Apps in Unity – Unity Blog […]

[…] the recent release of Unity version 4.5.3, Unity now supports universal Windows apps, allowing developers to leverage much of the same code to deliver games for both Windows and […]

[…] and how Universal Windows Applications work, believe me, you’re better off with this blog post, than having me attempt to paraphrase […]

[…] a big day in the Windows world, with Microsoft rolling out a grip of security patches, updates for Surface tablets, and new […]

Access the full power of .NET 4.5.1 in your C# scripts (Windows Runtime APIs, async/await, etc.);

Add access to .Net 4.5.1 features for Linux and Mac standalone builds

Because of errors when running the certification test kit i upgraded to the latest VS version wich is unfortunatly the update 3 and incompatible with the project type generated by Unity :/

Finally!, couple of questions:
-Do we need only one archive built in VS (xap or whatever) or we need to build both the windows solution and the phone solution?
-What about the windows phone sdk requirements?

Comments are closed.