Hello Everyone, To keep up a higher pace of changes to improve Unity's Windows MR support we are releasing a special build of Release Candidate 2. Please only use this build if you are working on a Windows MR title otherwise use the official RC2 build which will be released soon. Note: The release notes below only cover the custom changes made on-top of RC2. These changes will be included in patch builds once 2017.2 is final. The below releases are for historical reference.

Starting with Unity 2017.2.1 P2 no custom build is required. All fixes made in the previous custom builds have been rolled into this release and all future releases. You can find this 2017.2.1 P2 here: In addition once 2017.2.2 ships you will no longer need a patch release. --------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------- UPDATE 5: Release Notes: • This build incorporates all changes from Unity’s 2017.2.0p2 patch; see for details. • Fixed issue with applications not recovering correctly from tracking loss.

(case 969994) • Fixed a random threading crash. I updated to this build, and now the motion controllers are reporting a different position and rotation via the UnityEngine.XR.InputTracking API. Is this to be expected? The position and orientation in beta 11 and RC1 were much more similar to what oculus motion controllers reported. It is almost like they are reporting the pointer pose instead of the grip pose. Edit: Okay, I know what happened.

Even though the docs for months have been saying UnityEngine.XR.InputTracking uses the Grip pose, it had actually been using the Pointer pose. I updated to using UnityEngine.XR.WSA.Input.InteractionManager.GetCurrentReading and retrieved the pointer pose. Hands are back to where then were when I was on beta 11 and used the UnityEngine.XR.InputTracking API. Click to expand.2017.2 has Vuforia built in and that is why I chose to use it.

Sep 11, 2018 - The Bioscleave House, the culmination of 40 years of scientific and philosophical investigation into how best to sustain human life and how to.

But I found out that 2017.2 has a bug with the holographic emulation in the editor so I have to build to the hololens everytime I needed to test the project. This version has fixed that issue but doesn't support Vuforia which is a main aspect of my application. So my solutions until this is merged into a 2017 version I can use is to either roll back to 2017.1.2 and use the legacy vuforia package. Jasper jack daniels font download. Or continue what I'm currently doing which is developing hololens functionality in this version and when I'm ready for a build port the code back to 2017.2 f2 add my vuforia prefabs into the scene uncomment all my vuforia related code and build. It beats building it for every little test but is still a huge pain. @ too much issues actually. I can build with IL2CPP but a call to InteractionManager throws an exception and I can't to anything.

I've issues on Xbox One too related to the event system. I use this code to ensure it's working standaloneModule.forceModuleActive = true; But it not works all the time. By example if I set the timescale to 0 (for a menu), it doen't work anymore. It works on PC.

I hope that it'll be fixed soon. I compiled my game using the RC2-MRTP which is stable for me. BUT I reported the release of the Xbox One version until this issue is fixed. Click to expand.Could you elaborate? Where did you get the 'regular installer' for UnitySetup-Metro-Support-for-Editor-2017.2.0f3 from? Edit: In case you meant the (installing them regardless the 'Version mismatch' warning), those won't work for me, with, I first have to edit HandsManager and HandGuidance, since they use obsolte events and delegates of InteractionManager (which seems to me I don't use the version I should use), then when building/generating the UWP VS project out of Unity, I get the following error.