[Custom Build] 2017.2 RC MRTP (Windows Mixed Reality Technical Preview)

So I am using Hololens with vuforia but can't seem to download Vuforia for this version

 

Starting from Unity 2017.2f2 Vuforia is integrated wit hunity, do not need to download plugin, you just download Vuforia support in Download Assistant like a standard component, then enable it in build settings.

 

Yes I know but with this version that has fixes to hololens there is no download for vuforia. When you go to xr settings and click the download for vuforia it goes to a 404 page.

 

Seeing as 2017.1.2 was just released it's probably safe to say you guys aren't going to release for a few more weeks.

Any chance these fixes will make it into the RC instead of Patch Releases?

 

@ScottF 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.

 

2017.2 has Vuforia built in and that is why I chose to use it. 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. 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.

 

SO @ScottF are you saying these fixes WILL be in RC 3? or that this "patch" release just includes RC3 fixes?

 

So did this stuff get put into the actual release?

Says it did in the release notes.

Should we use formal release or MRTP?

 

Doesn't look like it @StephenHodgson-Valorem , Don't see any of the fixes listed above in the release notes.
But I'm happy to be corrected (although I only just installed the F3 MRTP build today :S)
@ScottF ?

 

It's not like Microsoft has pushed the Fall Creator's Update so people running vanilla windows couldn't use the official release anyway.

 

Hello everyone,

Unity 2017.2f3 was released yesterday and I don't see these changes in the release notes. Do I have to use the RC3-MRTP instead of the 2017.2f3 to publish on the Store? I'm ready to publish day one, I just need to know what build to use. Thanks guys!

 

Hello,

The RC3 doesn't work with IL2CPP if I use the InteractionManager class. That's problematic.. I use the post Processing stack v2, so I can't build without IL2CPP. I'll retry with the RC2, or make a dirty fix and patch the game after the release.

 

How is it not working for you? Compile error or runtime issue?

 

Download link for UnitySetup-Metro-Support-for-Editor-2017.2.0f3-MRTP.exe not working.

Anyone has the correct url?

 

@ScottF Is there no way to tell the difference between the two 2017.3.0f3 MRTP updates?

The build numbers are the same.

 

@Barkers-Crest 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.

 

@ScottF That means that the next build will not be official too? If it's the case, please try it on Xbox One and IL2CPP.
The post processing stack v2 is not compatible without IL2CPP with UWP so I don't have other choice to use that. Thanks.

 

Same Question here. Am I missing something?

Edit:
Got it, just use the regular 2017.2.0f3 Installer and set the directory to the "MRTP" Install Folder

 

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 downloaders here (installing them regardless the "Version mismatch" warning), those won't work for me, with Holograms211/Completed/ModelExplorer, 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:

Can anybody please give me some guidance here?

 

Are you using the HoloLens? 2017.2 is a bit broken, even the MRTP build. Stick to 2017.1.2f1 for now until Unity fixes it.

 

@solidsnake530 2017.2 if fine if you're not using the MRTK. We have some compile declarations that make it incompatible for just our library at the moment.

 

Well, I'm getting spammed with "Couldn't find spatial stage - we have to track as though we were stationary for our tracking space type, even though we should be at room-scale!", even with the latest version. Anyone else?

 

"InputTracking.Recenter now works on WindowsMR"

Unfortunately this feature does't work on Acer's Immersive HMD.

Already reported by issuetracker.
https://issuetracker.unity3d.com/is...d-reality-immersive-headset-does-not-recenter

 

Hey there SolidSnake I'm at the end of this rabbit warren I have downloaded most of the Unity archive trying to get through the tutorials in the Microsoft Academy. the way I read your post you can get around the HoloLens deployment issue by running 2017.1.2.f1 but which version of the windows SDK should work? I'm doing the 210-Gaze tutorial which is compiled in Unity 2017.1.2.f3. when I try to start without debugging the build succeeds but the 'deploy' fails at AssemblyConverter.exe are you suggesting we should attempt use VS2015 or 2017?

Any insight would be greatly appreciated.
Cheers
Dion

 

You can use VS2017, you have the right version of Unity for HoloLens. Target SDK 15063 in Unity, but if you edit the manifest in the UWP VS project, you cannot set the minimum SDK version higher than 14393.

 

So now that the first patch release is out, should we be using it or the MRTP 3?

 

Currently, the recommendation is to use the builds listed in this thread. When the recommendation shifts to using the mainline builds, we will update this thread very clearly with that recommendation.

 

I have updated the unity version from 2017.1.1 to 2017.2.0f3 yesterday. When I launched a previous project, unity asked an obsolete API and I have no idea about it...And some scripts didn't work and the console gave the warning and errors. For example: warning CS0618: `UnityEngine.XR.WSA.Input.GestureRecognizer.NavigationCompletedEvent' is obsolete: `NavigationCompletedEvent is deprecated, and will be removed in a future release. Use OnNavigationCompletedEvent instead.' So what should I do? Go back to the version 2017.1.1 and wait for a more stable 2017.2?

 

I'm trying to get a Samsung Mixed Reality HMD working in Unity with the motion controllers.

I've downloaded the MRTP4 build, installed the Dev.2017.2.1 unity packages into my project, and ran one of the examples scenes after the Cliff House portal is running. When I Play the scene, it doesn't send any data to the HMD. When I try to enable "Target Occluded Devices" under the "Mixed Reality Toolkit > Apply Mixed Reality Project Settings" I get an error: "Switching to Universal Windows Platform:MetroSupport is disabled". Thoughts?

I'm able to have the HMD working in 2017.2.0f3, but I can't get the motion controllers to show.

Any help would be appreciated. Thanks.

 

I have similair issues, so following...

 

Can you try the MRTK (mixed reality toolkit) asset, it has options to setup your project correctly, just in case you missed anything.
If it works, then more likely it's your project/scene setup rather than Unity.
https://github.com/Microsoft/MixedRealityToolkit-Unity

For MR, it shouldn't matter which headset you are using, they are share the same SDK.

 

Is anyone having issues with scene changes with the latest -MRTP4 build? When I do a SceneManager.LoadScene(levelToLoad, LoadSceneMode.Single); the editor crashes. Might be specific to my scenes, just wanted to check if it's a known issue.

 

So I downloaded the GitHub project from the link you provided, and loaded it into Unity 2017.2.0p1-MRTP4. Playing the scene did not sync my HMD. Under the PlayerSettings > XR Settings > Virtual Reality Supported was un-checked. When I checked the box it defaulted to Oculus. If I hit the + it does not give me a Mixed Reality option. If I try to re-apply the Mixed Reality Toolkit > Configure > Apply Mixed Reality Project Settings I get an error:
"Switching to Universal Windows Platform:MetroSupport is disabled"

I also get the same error if I create a new Project in 2017.2.0p1-MRTP4, import the HoloToolkit and holoToolkit-Examples assets, and the configure the ToolKit like above.

The only time Im able to Apply Mixed Reality Project Settings without getting that error is in Unity 2017.2.0f3. When I play the example scene I am able to see it load in the HMD, but the controllers do not show, although I can hear the "click" sound when pressing the trigger on the controller. Under the PlayerSettings > XR Settings > Virtual Reality Supported is checked and also lists Windows Mixed Reality.

Do I need to anything in the Build Settings, or is that only when I need to build my scene?

Thanks for your help.

 

That error suggests you don't have the UWP modules / SDK's installed.

For MR to "work" you need:

• Windows 10 fall creators update
• VS2017 with UWP development enabled and SDK 16299
• Unity 2017.2.0p1-MRTP4
• Unity UWP module support, preferably .NET, although the IL2CPP does "work"
• Platform set to Windows Universal Platform
• XR settings enabled and set for "Mixed Reality"

Hope that helps.

 

I can't set my build to "set to Windows Universal Platform"

My build settings says "No Universal Windows Platform module loaded"
Where I can download that? I didn't see any options to choose from when installing Unity 2017.2.0p1-MRTP4.

Thanks.

 

btw, has any of you tried your unity project with the steamVR beta (not using this special build)? Any showstopping bugs?

 

Same thing for me with the 2017.2.-MRTP1.
I've got a "normal" 2017.2 beside on the same computer with the UWP available in the list but the item is missing in the MRTP1.

 

Did you install using the UnityDownloadAssistant.exe? That should let you install the UWP components, while I assume using just the editor installer doesn't.

 

Thanks, I will check it. I don't remember.
=> download the MPR4, from the UnityDownloadAssistant.exe and it works now, the UWP is present.
Thanks for your help

 

I am just asking because my unreal projects work out of the box as SteamVR (tested on Alienware 17 R4 and Dell Visor), without changing anything. I wonder if it is always needed to setup my unity projects as UWP or if it just works as SteamVR.

 

Can we get an updated MRTP build based on the 2017.2.0p2 release please?

 

@ScottF

I can't set my build to "set to Windows Universal Platform"

My build settings says "No Universal Windows Platform module loaded"
Where I can download that? I didn't see any options to choose from when installing MRTP3 or MRTP4 using the DownloadAssistant.

Thanks.

 

Launch Download Assistant and select Windows Store .NET Scripting Backend

 

That worked, thanks.

 

I can haz MRTP 5?

 

So @ScottF does the latest 2017.2.0p2 build now include all the fixes needed for Mixed Reality? Or do we need a newer MTRP build? Hoping for the former, saw a load of fixes for XR but not the issues listed above.