You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2024. It is now read-only.
The World Locking Tools are a great resource and provide an impressive improvement to image stability on multiple platforms, but given what has happened with the MRTK and other XR-related teams at Microsoft I'm curious as to this project's status. Is it still supported by Microsoft or any external developers? And how about the Frozen Engine itself?
We were able to update the WLT to work with Unity 2022 and AR Foundation 5.n as well as with the XROrigin and related changes from Unity and can probably continue to migrate, but without continued development or access to the Frozen Engine source it feels like this increasingly risky.
Does anyone have any visibility into this project's status or, alternately, any other open source tools that do something similar?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The World Locking Tools are a great resource and provide an impressive improvement to image stability on multiple platforms, but given what has happened with the MRTK and other XR-related teams at Microsoft I'm curious as to this project's status. Is it still supported by Microsoft or any external developers? And how about the Frozen Engine itself?
We were able to update the WLT to work with Unity 2022 and AR Foundation 5.n as well as with the XROrigin and related changes from Unity and can probably continue to migrate, but without continued development or access to the Frozen Engine source it feels like this increasingly risky.
Does anyone have any visibility into this project's status or, alternately, any other open source tools that do something similar?
The text was updated successfully, but these errors were encountered: