Replies: 1 comment 1 reply
-
Problems I encountered when moving from MRTK2 to MRTK3: 1.How can I capture the global click event and then draw a line in the apace? 2.How to close the hand ray ? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are very happy to announce the release of preview 18 under the new Mixed Reality Toolkit organization. This new organization brings together affiliated corporations across the mixed reality industry to help build future versions of the Mixed Reality Toolkit (MRTK). For more information about this new organization, please visit the Microsoft Tech Community Mixed Reality blog post.
With the new organization comes some breaking changes. The first being the removal of the Microsoft prefix from all namespaces, which now start with MixedReality.Toolkit. Second, packages have been renamed from
com.microsoft.*
toorg.mixedrealitytoolkit.*
. The old packages still exist but are deprecated. Applications should switch to the new packages as soon as possible. Next, the new version of MRTK has been relicensed under BSD 3-Clause. This permissive license is somewhat like the previously used MIT License, with an additional non-endorsement clause. Developers should review the new license before incorporating these latest changes.The final breaking change is a new repository. Going forward a new repository will be used for MRTK development. The new repository is located at https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity. The old repository, https://github.com/microsoft/MixedRealityToolkit-Unity, is remaining under Microsoft's management. Microsoft is committed to the next version of MRTK, and recommends applications move to MRTK3. However, Microsoft will continue to support and address critical MRTK2 issues, until MRTK2 is deprecated.
Along with the breaking changes, this preview release contains additional fixes and minor additions. As always, we welcome your feedback on these changes and look forward to releasing MRTK3 GA this September.
Changelog for MRTK3 pre.18
[pre.18] - 2023-8-21 -
a194901
The format is based on Keep a Changelog. The content is mirrored at the changelog page of the Microsoft docs website, for now.
Added
ComponentCache<T>
class has been added to help cache commonly queries scene components. (11686)UnboundedTrackingMode
component was added to replace the soon-to-be deprecatedMicrosoft.MixedReality.OpenXR.EyeLevelSceneOrigin
in Microsoft's Mixed Reality OpenXR Plugin. (11750)Changed
com.unity.inputsystem
version 1.6.1 to address mouse input issues on HoloLens. (11661)CameraSettingsManager
component is now on the MRTK XR Rig prefab. This component auto configures the main camera's settings based on the device's display type (Transparent
orOpaque
). (11684, 11685)LocateTargetHitPoint
methods to a common, shared location. (11699)UnboundedTrackingMode
component was added to the MRTK XR Rig prefab. This change only impacts HoloLens 2 applications. (11750)Microsoft
removed, so to align with new MRTK organization. (1)Deprecated
com.microsoft.*
packages are now deprecated. Switch to theorg.mixedrealitytoolkit.*
packages instead. (#31, #32, #34)Removed
SpatializationMixer
property from MRTK3 settings. This property wasn't used in the MRTK3 packages, so was removed for now. This property can be added later, once it has a well-defined use within the MRTK3 packages. (11681, 11694)IVariableReticle
and replaced withIReticleVisual
andIVariableProgressReticle
. Depending on the scenario, applications should implement one or both of the new interfaces. (11758, 9)Fixed
This discussion was created from the release MRTK v3.0.0 Preview 18 Release & New Mixed Reality Toolkit Organization.
Beta Was this translation helpful? Give feedback.
All reactions