We have published a new release (0.5.0) with the following changes:
- Polyspatial project Settings are now reorganized and are presented in a cleaner form.
- PolySpatial now supports two distinct particle rendering modes, with a corresponding tradeoff between quality and performance. Particle rendering mode is currently set globally across a project via the PolySpatial project settings. In the future, we hope to allow users to specify mode on a per-system basis:
- ReplicateProperties aka Legacy mode. Particle features are limited to capabilities provided by native RealityKit particles, and custom shaders aren’t supported. In practice, this means appearance may diverge significantly between Unity and visionOS, but this mode introduces minimal performance overhead.
- BakeToMesh: This mode offers improved quality and includes support for custom shaders, but imposes additional performance overhead.
- VR gaze input Support
- VisionOSSpatialPointerDevice exposes gaze/pinch through the input system package.
- Users can bind to ‘primarySpatialPointer’ control and its sub-controls, similar to the SpatialPointerDevice in the PolySpatial package.
- Template update and bugfix for VR
- Virtual Reality builds no longer fail if PolySpatial packages are in the project.
- URP settings in template updated to fix issues causing VR rendering to fail.
- A range of additional shader graph nodes are now supported, and several existing nodes have been improved. Please consult the package documentation for specifics, but changes include seven previously unsupported nodes relating to channels and colors: Channel Mixer, Replace Color, White Balance, Fade Transition, Channel Mask, Color Mask, and Channel Flip.
- We have resolved an error where MeshColliders with the isTrigger property set resulted in an error in play mode: “Triggers on concave MeshColliders are not supported”. A collider unit test has also been added to catch the issue.
- Our beta users have requested a way to completely omit objects from tracking for performance purposes. This release adds a “Disable Tracking Mask” to the settings and it also removes the now-unused MaterialXExtensionNamespace property).
- This release adds support for Fixed the shader validation warning appearing for supported shaders.
- Warning: The PolySpatialARProfileTest profile(s) do not fully support the shaders in the following materials: Universal Render Pipeline/Unlit.
- Fixed index buffer overruns.
- Beta users reported getting incorrect output from the shader graph world position node as transformed by the PolySpatial Volume to World node. This release fixes our offset.
- Previously, our support for the Colorspace Conversion node didn’t encompass linear/RGB conversions. In this release we changed it to use parsed expressions based on the source code/reference for the node.
- A number of performance improvements have been made to Unity UI and Sprite support that should help with complex UI or scenes with multiple, animated sprites.
For those who are testing on devices at Apple’s developer labs or via a developer kit, you should only be using the following configuration.
- Apple Silicon Mac for development
- Unity 2022 LTS (2022.3.11f1 to 2022.3.12f)
- Xcode 15.1 beta 1
- The Xcode 15 Release Candidate will not work
- visionOS beta 4 (21N5259k) - SDK
- This release was not extensively tested against visionOS beta 5 SDK.
To learn more about Unity’s visionOS beta program, please refer to this post. These release notes apply to the suite of packages released as part of Unity’s visionOS beta program:
- com.unity.polyspatial (0.5.0)
- com.unity.xr.visionos (0.5.0)
- com.unity.polyspatial.visionos (0.5.0)
- com.unity.polyspatial.xr (0.5.0)
Known 0.5.0 Issues
- When importing Samples and running ProjectLauncher in both editor PlayMode and visionOS player, the ProjectLauncher text for each Scene + description renders in low quality.
- When upgrading visionOSTemplate 0.4.3 to 0.5.0 packages, an error logged in the console for SampleSceneUnbounded: “Couldn’t create Convex Mesh from source mesh “” within the maximum polygons limit (256) …”
- When running in editor PlayMode, exceptions are thrown when navigating through the SampleScenes via ProjectLauncher.
- Slider component no longer crashes when the exception gets thrown, but ongoing issues with functionality, including the audio getting garbled, persist.
- VisionOS Template SampleScene shows pink material in PlayMode
- To work around this, please disable the XR simulator loader.
For additional information please visit the General Release Notes.
