Skip to content

build profile

retro-coder64 edited this page Oct 22, 2026 · 1 revision

The accessible Build Profiles window allows you to configure, build and run Windows games from Unity Access using your keyboard and NVDA.

This version supports Windows standalone builds using Unity's platform profile.

Opening Build Profiles

Open the Build Profiles window in Unity Access.

The window announces the active build target and provides the following options:

  • Target Platform
  • Scene List
  • Windows Platform Settings
  • Development Build
  • Compression Method
  • Build
  • Clean Build
  • Build and Run

Target Platform

Windows standalone is currently the supported platform.

If Windows Build Support is not installed, Unity Access will inform you that the module is missing.

You can install Windows Build Support through Unity Hub.

Changing the active build target may cause Unity to reimport assets or recompile scripts.

Platform Profiles

Build Profiles uses the standard Windows platform profile.

If a custom Build Profile is active, Unity Access identifies it and allows you to return to the Windows platform profile.

Creating and editing custom Build Profiles is not currently supported.

Managing Scenes

The Scene List determines which scenes are included in your game and the order in which they are loaded.

Each scene displays:

  • Scene name
  • Scene path
  • Whether the scene is included or excluded

Adding Scenes

You can add scenes in two ways:

  • Add Open Scenes: Add scenes currently open in Unity.
  • Add Scene: Use the accessible Object Selector to choose a scene from your project.

The same scene cannot be added twice.

Managing Scene Order

Select a scene to perform the following actions:

  • Include Scene
  • Exclude Scene
  • Remove Scene
  • Move Up
  • Move Down

The order of included scenes determines their build order.

For example, if your game has a main menu and a gameplay scene, you would normally place the main menu first.

Windows Platform Settings

Architecture

Choose the architecture for your Windows game:

  • Intel 64-bit: Standard option for most modern Windows computers.
  • Intel 32-bit: For supported 32-bit Windows systems.
  • ARM 64-bit: For compatible Windows ARM devices.

Intel 64-bit is the normal option for Windows development.

Build and Run On

Choose where your game should run:

  • Local Machine: Run the game on your current computer.
  • Remote Device: Available when supported by Unity.

Local Machine is the standard option. Remote device configuration is not currently supported.

Development Build

Enable Development Build to include development and debugging information in your game.

This is useful when testing a project.

For normal distribution, you would typically leave Development Build disabled.

Compression Method

Choose how Unity compresses the build data:

  • Default: Use Unity's default compression settings.
  • LZ4: Prioritises faster compression and decompression.
  • LZ4HC: Uses higher compression, generally taking longer to build.

Your project's existing compression setting is preserved unless you change it.

Building Your Game

Build

Use Build to create a Windows version of your game without launching it automatically.

  1. Ensure Windows is the active target platform.
  2. Add at least one scene to the Scene List and ensure it is included.
  3. Configure the Windows platform settings.
  4. Select Build.
  5. Choose where to save the build.
  6. Unity creates the Windows game files.

Clean Build

Select Clean Build to perform a clean build using Unity's supported clean-build process.

This can be useful when you want Unity to rebuild the project without relying on previously generated build data.

Build and Run

Use Build and Run to build your game and launch it automatically.

  1. Configure your scenes and build settings.
  2. Select Build and Run.
  3. Choose the build output location when prompted.
  4. Unity builds the project.
  5. If the build succeeds, the game launches on the selected target.

For normal Windows development, select Local Machine.

Build Results

After a build finishes, Unity Access announces whether it:

  • Succeeded
  • Failed
  • Was cancelled

Where available, it also provides:

  • Build output location
  • Build duration
  • Build size

If the build fails, check the accessible Unity Access Console for errors.

Current Limitations

This version focuses on Windows standalone development.

The following features are not currently supported:

  • Creating or editing custom Build Profiles
  • Profile-specific settings and overrides
  • Advanced build diagnostics
  • Remote device configuration
  • Building for Android, iOS, macOS, Linux or Web

Clone this wiki locally