What's new in 2.5.0 Unity Package Manager (UPM) support This release fixes an issue where the teleport destination cursor can stick to hand visuals. This resolves the issue of shaders updated for the Universal Render Pipeline (URP) reverting the legacy behavior the next time the project is loaded.
When the Standard Assets package is installed via UPM, the shaders will be copied to the Assets/MRTK/Shaders folder so that they will no longer be immutable. Standard Assets package shaders copied to Assets/MRTK/Shaders Version 2.5.1 also adds an explicit dependency on Text Mesh Pro. This release fixes incorrect inter-package file dependencies (ex: files in Standard Assets no longer incorrectly reference files in Foundation). What's new in 2.5.1 Package dependency errors fixed Support for MSBuild for Unity has been removed as of the 2.5.2 release, to align with Unity's new package guidance. Boundary visualization errors fixedīoundary visualizations, like the floor or walls, will now be properly configured and visible at runtime according to the boundary profile. It also only supports 圆4, ARM, and ARM64 builds. OpenXR in Unity is only supported on Unity 2020.3 and higher. See the MRTK/XRSDK getting started page, Unity's forum post, or Microsoft's documentation for more information. Initial support for Unity's OpenXR preview package and Microsoft's Mixed Reality OpenXR package has been added.
What's new in 2.5.2 Add support for OpenXR What's new in 2.5.3 Fixes a regression with Oculus introduced in 2.5.2Ģ.5.2 introduced a build issue when integrating the Oculus SDK. Existing projects that are upgraded will still need this added manually. Fixes an issue with OpenXR via UPMįixes an issue where the OpenXR providers weren't added to the link.xml by default, causing new projects to fail to run on-device when using OpenXR and MRTK via Unity's Package Manager. This release configures the Device Manager to point to a working set of prefabs on startup. When using UPM, the OculusXRSDKDeviceManagerProfile would always have its prefabs set to None on startup. What's new in 2.5.4 Fixes a bug with Oculus Integration when using UPM Please import the .tools package to apply a workaround. If you are unable to update Visual Studio, This issue is fixed by updating Visual Studio 2019 to version 16.8 or later. There is a known compiler issue that impacts applications built for Microsoft HoloLens 2 usingĪRM64.
0 kommentar(er)
