Use the Universal Windows Platform (UWP) Build Settings to configure and build your application for UWP platform. The UWP Build Settings are part of the Build Profiles window.
To build your application for UWP:
Use these settings to configure how Unity builds your application for UWP platform.
| Property | Description | |
|---|---|---|
| Architecture | Select the CPU to build for (only applies to Build And Run). | |
| Intel 64-bit | Use Intel/AMD 64-bit CPU architecture. | |
| Intel 32-bit | Use 32-bit Intel CPU architecture. | |
| ARM 64-bit | Use 64-bit ARM CPU architecture. | |
| ARM 32-bit | Use 32-bit ARM CPU architecture. | |
| Build Type | Select the Visual Studio project or build type to generate. | |
| XAML Project | Integrates Unity within a full XAML environment. This results in some performance loss, but lets you use XAML elements in your application. | |
| D3D Project | Integrates Unity in a basic app window. This results in the best performance. | |
| Executable Only | Hosts the project in a pre-built executable for rapid iteration. This setting has the quickest iteration speed because it doesn’t require you to build the generated project in Visual Studio. It offers the same performance as D3D Project builds. | |
| Target SDK Version | Select the Windows 10 SDK installed on the local PC to build the application against. This setting is relevant only when calling Windows 10 APIs directly from scripts. Note: Unity requires the base Windows 10 SDK version 10.0.10240.0 or higher for building UWP apps, and doesn’t support Windows 8/8.1 SDKs. |
|
| Minimum Platform Version | Select the minimum Windows 10 release version required to run the app. Note: This setting is only relevant if you’re using Windows features or APIs that aren’t available in the base Windows 10 version (10.0.10240). |
|
| Visual Studio Version | Specify the Visual Studio version if you have multiple versions installed. | |
| Build and Run on | Select the target device or transport to deploy and launch the app during Build And Run. | |
| Local Machine | Deploys and launches the app on the local PC. | |
| Remote Device (via Device Portal) | Deploys and launches the app to a connected device over the Device Portal transport. For more information, refer to Windows Device Portal deployment. | |
| Build Configuration | Select the build configuration (only applies to Build And Run). Note: These build configurations are the same as those available in the Visual Studio project that Unity generates. |
|
| Debug | Produces a build that contains additional code you can use for debugging, and enables the ProfilerA window that helps you to optimize your game. It shows how much time is spent in the various areas of your game. For example, it can report the percentage of time spent rendering, animating, or in your game logic. More info See in Glossary for your build. |
|
| Release | Produces a build that has debug code stripped out, and enables the Profiler for your build. | |
| Master | Produces a build that’s fully optimized for release. | |
| Copy References | Disable this setting to allow the generated solution to reference Unity files from Unity’s installation folder instead of copying them to the build folder. This can save up to 10 GB of disk space, but you can’t copy the build folder to another PC. Unity also builds your application faster when you disable this setting. | |
| Copy PDB files | Enable this setting to include Microsoft program database (PDB) files in the built Player. PDB files contain debugging information for your application, but might increase the size of your Player. | |
| Development Build | Include scripting debug symbols and the Profiler in your build. Use this setting when you want to test your application. When you select this option, Unity sets the DEVELOPMENT_BUILD scripting define symbol. Your build then includes preprocessor directives that set DEVELOPMENT_BUILD as a condition.For more information, refer to Platform dependent compilation. |
|
| Autoconnect Profiler | Automatically connect the Unity Profiler to your build. For more information, refer to Profiler. Note: This option is available only if you select Development Build. |
|
| Deep Profiling | Allow the Profiler to process all your script code and record every function call, returning detailed profiling data. For more information, refer to Deep Profiling.
This property is available only if you enable Development Build. Note: Enabling Deep Profiling might slow down script execution. |
|
| Script Debugging | Attach script debuggers to the Player remotely. This property is available only if you enable Development Build. |
|
| Compression Method | Specifies the method Unity uses to compress the data in your Project when it builds the Player. This includes AssetsAny media or data that can be used in your game or project. An asset may come from a file created outside of Unity, such as a 3D Model, an audio file or an image. You can also create some asset types in Unity, such as an Animator Controller, an Audio Mixer or a Render Texture. More info See in Glossary, ScenesA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info See in Glossary, Player settingsSettings that let you set various player-specific options for the final game built by Unity. More info See in Glossary, and GI data. |
|
| Default | On Windows, Mac, Linux Standalone, and iOS, there is no default compression. On Android, the default compression is ZIP, which gives slightly better compression results than LZ4HC. However, ZIP data is slower to decompress. |
|
| LZ4 | A fast compression format that is useful for development builds. For more information, refer to BuildOptions.CompressWithLz4. | |
| LZ4HC | A high compression variant of LZ4 that is slower to build but produces better results for release builds. For more information, refer to BuildOptions.CompressWithLz4HC. | |