We have published a new release (0.2.2) that provides support for Xcode 15 beta 5 and visionOS beta 2 SDK. For those who are testing on device at Apple’s developer labs or via a developer kit, make sure you’re using the right configuration outlined in the “Requirements” section.
To learn more about Unity’s visionOS beta program, please refer to this post. The following release notes apply to the suite of packages released as part of Unity’s visionOS beta program:
- com.unity.polyspatial (0.2.2)
- com.unity.xr.visionos (0.2.0)
- com.unity.polyspatial.visionos (0.2.2)
- com.unity.polyspatial.xr (0.2.2)
- Apple Silicon Mac for development
- Unity 2022 LTS (2022.3.5f1 only)
- There is a known issue with IL2CPP on newer versions of 22 LTS.
- Xcode 15 beta 5
- visionOS beta 2 SDK
- Redeem your coupon code to unlock the Apple VisionOS Beta subscription. This is a prepaid subscription used to manage access to our packages during the beta program. No payment is required to participate in the program.
- Launch the Unity Hub, or restart the Unity Hub if it is already open.
- Create a new Unity project using Unity 2022.3.5f1, and make sure visionOS Build Support (experimental) and iOS Build Support are installed.
- Please note that visionOS Build Support (experimental) is only supported on Mac devices.
- Open the Package Manager (Window > Package Manager) and make sure Packages: Unity Registry is selected.
- Open the “+” dropdown and select “Add package by name…”
- Add the following packages:
As a reminder, experimental releases are not supported for production, but they provide early access for those who want to start testing our solutions for the visionOS platform. This also helps us make progress on development through your feedback.
Template and Samples
- Download the visionOS Project Template here.
- Unzip the file to your desired project location.
- Open the project with Unity 2022.3.5f1 using the Unity Hub > Open Project
- Further information is provided with In-Editor Tutorials in the Template, and the template documentation.
Unity PolySpatial Samples
The PolySpatial Samples are built with the Universal Render Pipeline. If you are not starting with the template project referenced above, please create a new project using the Universal Render Pipeline, or manually add and configure URP to your project. Without this, materials from the samples will appear pink in the editor.
- Once you have installed our Unity packages, go to the Package Manager (Window > Package Manager) and select the Unity PolySpatial package.
- Under the Samples tab, select Import on the Unity PolySpatial Samples.
- Once the samples are installed, open the Scenes folder and add all the scenes to your build settings (File > Build Settings…). Make sure the ProjectLauncher scene is the first one.
- Open Project Settings (Edit > Project Settings…), select XR Plug-in Management, and make sure Apple visionOS is selected under the visionOS tab (the furthest on the right).
- Select the Apple visionOS setting under XR Plug-in Management and set the Volume Mode to Bounded.
- Build your project for the visionOS (experimental) platform.
- Open the Xcode project and target the Apple Vision Pro simulator to launch the project launcher scene. From here, you can use the arrows to select and click Play to load a scene.
Please note that the samples included in version 0.1.0 of the PolySpatial package will overwrite your XR project settings, and may introduce issues with builds and XR Management project settings.
To fix this, close the Editor, delete the Assets/XR folder (or revert using version control), and restart the Editor. Everything in this folder should get regenerated with default values. You may need to re-enable loaders and restore settings you had previously.
- The samples have been updated to work in play mode in the editor.
- The template has been updated with an In Editor Tutorial and interactive content for a bounded mode app.
- [New Known Issue] The SampleScene is the only supported scene in the template project. The Expand View button in SampleScene is not functional.
- [New Known Issue] When using the visionOS Simulator, you may experience visual issues with any object that has upward facing normals.
- [New Known Issue] The SampleScene in the visionOS Template project has a camera component that is not tagged as Main Camera causing log spam related to Poly Spatial Host Camera
- [New Known Issue] XR management has a visual bug with visionOS being enabled after importing the PolySpatial samples. To work around this, uncheck and recheck Apple visionOS on the visionOS tab (far right) of XR Plug-in management before making a build.
- [New Known Issue] Interacting with the Slider component in the SpatialUI scene of the samples will crash the app
- Please note that when running apps in visionOS Simulator, the result may be different than the Vision Pro headset. Check out Apple’s guide on running your app in the simulator to learn more.
- On build, the resulting project is still called “Unity-iPhone.xcodeproj”. (Fix in progress)
- Only Apple Silicon machines are supported. Support for the x86-64 simulator is coming in a future release.
- When running in the Simulator, you may need to disable Metal API Validation via Xcode’s scheme menu (Edit Scheme > Run > Diagnostics > uncheck Metal API Validation). (Fix in progress)
- Some visionOS/iOS player settings are ignored or improperly applied. (Fix in progress)
- The PolySpatial project validations are under the Standalone, Android and iOS tabs in the Project Validation window (Edit > Project Settings > XR Plug-in Management) (Fix in progress)
Windowed Apps / Virtual Reality
- Crashes may be seen when some pixel formats are used. (Fix in progress)
- To receive controller input, you’ll need to use a prerelease version of the Input System package. In your project’s Packages/manifest.json, include:
"com.unity.inputsystem": "[ https://github.com/Unity-Technologies/InputSystem.git?path=/Packages/com.unity.inputsystem](https://github.com/Unity-Technologies/InputSystem.git?path=/Packages/com.unity.inputsystem)"
visionOS Shared Space / PolySpatial
- Objects may flicker in and out of visibility, especially when using a bounded volume. (Platform issue)
- An application cannot have more than one volume at this time. (Platform issue)
- Volume camera dimensions cannot be changed dynamically. (Platform issue)
- Canvas / UGUI can consume lots of CPU and be very slow. (Fix in progress)
- Unity Particle System effects may not function or look correct. (Fix in progress)
- Input sometimes does not work, due to input colliders not being created on the RealityKit side. (Fix in progress – enable collision shape visualization in Xcode to see if this is your issue)
- When using an Unbounded Volume Scene, an empty 2D window appears at app launch (Fix in progress)
Frequently asked questions
Q: My input code is not working and I’m not getting the correct touch phases
A: Make sure you are using the correct touchphase
using TouchPhase = UnityEngine.InputSystem.TouchPhase;
Q: Everytime I launch my app the home menu icons will appear in front of it.
A: This is a known issue. (Platform issue)
Q: Hover component shows up differently depending on the object geometry.
A: This is a known issue. (Platform issue)
Q: My app is not responsive or updating slowly.
A: Check the performance tab in Xcode and see if the usage percentages are near or over 100%. If your app is not hitting performance, the simulator and passthrough video will not slow down or stutter but the objects in your app might.
Tips for getting started
- Use XCode visualizations to see information about objects in your app
- Make sure you have the leftmost icon selected in the simulator for interacting with content. Other icons are for navigating the simulator and do not register input.