Release/7.3.0 -> Develop

Packages/Tracking Preview/package.json

@@ -1,12 +1,12 @@
 {
   "name": "com.ultraleap.tracking.preview",
-  "version": "7.2.0",
+  "version": "7.3.0",
   "description": "Ultraleap Tracking Preview, contains code and examples for interactions that are in a preview state and subject to potential breaking changes",
   "displayName": "Ultraleap Tracking Preview",
-  "unity": "2021.3",
+  "unity": "2022.3",
   "license": "Apache-2.0",
   "dependencies": {
-    "com.ultraleap.tracking": "7.2.0",
+    "com.ultraleap.tracking": "7.3.0",
     "com.unity.inputsystem": "1.5.0",
     "com.unity.ugui": "1.0.0"
   },
@@ -38,7 +38,7 @@
     {
       "displayName": "Main Examples",
       "description": "A collection of examples for the Ultraleap Tracking Preview package, which use the Input System Package (New)",
-      "path": "Examples~/Main Preview Examples"
+      "path": "Examples~/Main Examples"
     },
     {
       "displayName": "Unity Input Manager (Old)",

Packages/Tracking/CHANGELOG.md

@@ -6,14 +6,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 [docs-website]: https://docs.ultraleap.com/unity-api/ "Ultraleap Docs"
 
-## [NEXT]
+## [7.3.0] - 25/02/2026
 
 ### Added
 - Experimental Meta compatibility mode for the OpenXR provider
 - Added support to upgrade the plugin's Built In Render Pipeline materials (and as a result the example scenes) to the Universal Render Pipeline. This can be set to automatically prompt when the materials don't match the current render pipeline. It does not support downgrading.
 - Changed LeapC PInvoke signatures to support iOS.
 - Added support for proximity rules in pose detection. Use the attachment hands to generate transforms for the other hand joints that can then be assigned to a proximity rule, if the target should be a joint in the other hand.
-- Added support for a pose detection to require that both hands are in the target pose for the pose to be recognized.
+- Added support for pose detection to require that both hands are in the target pose for the pose to be recognized.
 - Added stencil based variants of the generic hand materials to force a hand to render over another - e.g. when live hands need to match posed hands.
 - Added optional argument to AssignBestLeapProvider in HandUtils to prefer potentially live data LeapProviders vs. HandPoseViewer. Fixes a potential pose detection bug.
 
@@ -33,7 +33,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 - Fixed some warnings around runtime variables that were only used in editor mode
 - Fixed an issue with Physical Hands and Unity 6 due to the physics Contact Generation setting being removed
-- (UI Input Preview) Added explicit missing dependancy on the "Unity UI" package
+- (UI Input Preview) Added explicit missing dependency on the "Unity UI" package
 - Support either input system for all interactions, fixing HandRecorder and CycleHandPairs
 - Clicks on UI elements using indirect interaction now work with the UI Input example scene
 - Text on the toggle button in the UI Input example scene now shows On or Off based on the toggled state
@@ -45,10 +45,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Known Issues
 - Ultraleap tracking with Ultraleap hardware no longer works on a Meta Quest 3 headset running an OS version >76 due to [changes in which permissions are allowed.](https://developers.meta.com/horizon/resources/permissions-prohibited/)
+- On Mac OS only, the client libraries now default to using a different tracking server port. For hand tracking to work, either change the Server Connection Input mode to PORT or set the port in the Server Name Space field to {"tracking_server_port": 12345}
 - Pose detection scene does not illuminate all poses in green if built for mobile headsets when using URP (2022.3), spotlights don't work as intended on Unity 6.
 - Turntable and pullchord scene only works (i.e. the pullchord works) if the physical hands physics settings are used
+- Turntable and pullchord - origin material is pink (error) and only renders in one eye - BiRP and URP - Unity 2022 only
+- Turntable and pullchord - scene produces a couple of 'the referenced script (unknown) on this Behaviour is missing' warnings - unless the tracking preview package/examples are imported
+- A number of .so plugin files are not 16-byte aligned and produce warnings when a build is made (libLeapC.so, libUnityOpenXR.so, libLeapCLegacy.so)
+- Console error on shader Ultraleap/GenericHandShader - Material 'GhostCapsule Hand (Instance)' with Shader 'Ultraleap/GenericHandShader' doesn't have a color property '_MainColor'
+- Certain scenes containing physical interactions produce 'Setting linear velocity of a kinematic body is not supported' warnings (UnityEngine.RigidBody:set_velocity)
+- Text missing on example scene panels in Unity 6.3, need to manually import TextMeshPro Essential Resources - Window > TextMeshPro > Import TMP Essential Resources
+- Warnings about deprecated components when importing plugin into Unity 6.3 - XRStats, Physics.autoSyncTransforms
 - The RuntimeGizmoManager and associated RuntimeGizmo.shader shader are not URP compatible and would require breaking changes to support URP; These remain as BiRP only
 - Support either input system for all interactions, fixing HandRecorder and CycleHandPairs
+- Scene(s) using physical hand interactions will prompt to go to settings to change parameters. One parameter is not being set, when set which is causing this repeated prompting
+- Hand distortion seen on Pico devices using Ultraleap Tracking hardware (large hands, messed up hand rotation vectors)
+
 
 ## [7.2.0] - 17/01/2025
 

Packages/Tracking/package.json

@@ -1,9 +1,9 @@
 {
   "name": "com.ultraleap.tracking",
-  "version": "7.2.0",
+  "version": "7.3.0",
   "description": "Ultraleap's Unity Plugin enables the data produced by Ultraleap tracking hardware to be used by developers inside their Unity projects. It includes various utilities and prefabs that make it as easy as possible to design and use hand tracking in XR projects",
   "displayName": "Ultraleap Tracking",
-  "unity": "2021.3",
+  "unity": "2022.3",
   "license": "Apache-2.0",
   "keywords": [
     "ultraleap",

README.md

@@ -53,9 +53,14 @@ To use this plugin you will need the following:
 
 1. The latest Ultraleap Hand Tracking Software. You can get this [here][developer-site-tracking-software].
 2. An Ultraleap Hand Tracking Camera - follow setup process [here][developer-site-setup-camera].
-3. Unity 2021.3 LTS or newer. UnityPlugin packages have been tested to work against 2022.3 LTS. Light testing has been done with Unity 6. However, there are still issues with the render pipeline switching to URP - many of the materials and sample scenes will not render correctly due to broken shaders.
+3. Unity 2022.3 LTS or newer. UnityPlugin packages have been tested to work against 2022.3 LTS and Unity 6.3 and URP/BiRP. We currently ship the materials for BiRP but the user will be prompted to convert material to URP, if it is detected.
 4. Follow one of the Installation workflows listed below.
 
+There are also some notable known issues in this release, worth mentioning here:
+- Ultraleap tracking with Ultraleap hardware no longer works on a Meta Quest 3 headset running an OS version >76 due to [changes in which permissions are allowed.](https://developers.meta.com/horizon/resources/permissions-prohibited/)
+- On MacOS only, the client libraries now default to using a different tracking server port. For hand tracking to work, either change the Server Connection Input mode to PORT or set the port in the Server Name Space field to {"tracking_server_port": 12345}
+
+
 More detailed Getting Started documentation is available on [our website][documentation]
 
 **Please note:**
@@ -215,7 +220,7 @@ Use of Ultraleap's Unity Plugin is subject to the [Apache V2 License Agreement][
 
 ## Community Support
 
-Our [Discord Server][discord], [Github Discussions][github-discussions] and [Developer Forum][developer-forum] are places where you are actively encouraged to share your questions, insights, ideas, feature requests and projects.
+Our [Discord Server][discord], [Github Discussions][github-discussions] and [Developer Forum][developer-forum] are now read only.
 
 ## Links