Search Unity

  1. We've closed the job boards. If you're looking for work, or looking to hire check out Unity Connect. You can see more information here.
    Dismiss Notice
  2. We're running great holiday deals on subscriptions, swag and Asset Store packages! Take a peek at this blog for more information!
    Dismiss Notice
  3. Check out our Unite Austin 2017 YouTube playlist to catch up on what you missed. More videos coming soon.
    Dismiss Notice
  4. Unity 2017.2 is now released.
    Dismiss Notice
  5. The Unity Gear Store is here to help you look great at your next meetup, user group or conference. With all new Unity apparel, stickers and more!
    Dismiss Notice
  6. Introducing the Unity Essentials Packs! Find out more.
    Dismiss Notice
  7. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice
  8. Unity 2017.3 beta is now available for download.
    Dismiss Notice

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

Discussion in 'AR/VR (XR) Discussion' started by ScottF, Oct 1, 2017.

  1. ScottF

    ScottF

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    67
    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.

    ---------------------------------------------------------------------------------------------------------------------
    UPDATE 5:

    Release Notes:

    • This build incorporates all changes from Unity’s 2017.2.0p2 patch; see release notes here for details.
    • Fixed issue with applications not recovering correctly from tracking loss. (case 969994)
    • Fixed a random threading crash.
    Download URL:
    http://beta.unity3d.com/download/a07ad30bae31/download.html

    ---------------------------------------------------------------------------------------------------------------------

    UPDATE 4:


    Release Notes:
    • MRTP build is now based off 2017.2 Patch 1
    • Fixed incorrect eye position offsets (case 963878)
    • Fixed visual stutter when transitioning from tracking to tracking loss and vice versa
    • Fixed incorrect eye position offsets when in a tracking loss state
    • Fixed calls to UnityEngine.Experimental.XR.Boundary.TryGetGeometry throwing internal exception and the function always failing (case 963315)
    Download URL:
    http://beta.unity3d.com/download/b1565bfe4a0c/download.html

    ---------------------------------------------------------------------------------------------------------------------
    UPDATE 3:

    Below is the fourth and most likely last custom 2017.2 build for Windows MR. 2017.2 Patch 1 will contain almost all fixes from all below patches minus some of the following which will be included in Patch 2 (see release notes for official releases).

    Release Notes:

    • Fixed performance regression on Microsoft HoloLens
    • Fixed several XAML application issues:
      • XAML applications now correctly launch on desktop
      • Applications properly resume when reactivating after blooming to the shell
      • Applications which include the None VR device will fallback to "flat" desktop mode if launched on a machine without an attached HMD
    Known issues:
    • Applications that do not include "None" device will enter a paused state when launched on a machine without an HMD when MRP is not running. This should be addressed by a future OS fix.
    Download URL:
    http://beta.unity3d.com/download/00283454d7e3/download.html

    ---------------------------------------------------------------------------------------------------------------------
    UPDATE 2:

    There is now a third update with additional Windows MR fixes. We recommend only taking these updates if you require the specified fixes below.

    Release Notes:
    • Fixed XAML activation issues
      • Fixed the issue when reactivating a XAML app, the container view would get the activation event instead of the holographic view
      • Fixed template code so it doesn't require a HoloLens
    • Fixed camera-transform popping in and out of tracking loss
      • Camera transform now responds to tracking loss in the same way as other platforms: fall back to rotation-tracking only during tracking loss, then teleport to the tracked position when tracking is recovered
      • The build settings option for pausing on tracking loss now only applies to HoloLens (this will be updated in the future to be a drop-down that lets you still choose to pause during tracking loss on opaque HMDs instead of a checkbox)
    • Fixed issue with reporting the old boundary if a new one had been configured while the app is running
    • InputTracking.Recenter now works on WindowsMR
    • Calling SetTrackingSpaceType with TrackingSpaceType.Stationary will now make the camera behave correctly
    Known Issue:
    • Tracking Type will always return Stationary as the type however the type specified by SetTrackingSpaceType is the one actually being used.
    Download URL:
    http://beta.unity3d.com/download/bf236913e22b/download.html

    ---------------------------------------------------------------------------------------------------------------------
    UPDATE 1:

    We have a second build with additional bug fixes. This build closely mirrors the RC3 build which will be released later this week.

    Release Notes:
    • Fix for XR.InputTracking.disablePositionalTracking
    • Fix for exception getting thrown when calling DateTime.Parse in IL2CPP builds
    • Fix for exception getting thrown when referencing DateTimeOffset in IL2CPP builds
    • Fixes for asserts and broken rendering when using XRSettings.eyeTextureResolutionScale
    • Fix for buttons not working with InputManager when only the left controller is on
    • Fix for respecting different near/far clip plane values when using multiple cameras in one scene
    • Fixed bug which caused Unity to crash on application close.
    Download URL:
    http://beta.unity3d.com/download/edcd66fb22ae/download.html
    ---------------------------------------------------------------------------------------------------------------------
    UPDATE:

    We have a second build with additional bug fixes. This build closely mirrors the RC3 build which will be released later this week.

    Release Notes:
    • Fix for XR.InputTracking.disablePositionalTracking
    • Fix for exception getting thrown when calling DateTime.Parse in IL2CPP builds
    • Fix for exception getting thrown when referencing DateTimeOffset in IL2CPP builds
    • Fixes for asserts and broken rendering when using XRSettings.eyeTextureResolutionScale
    • Fix for buttons not working with InputManager when only the left controller is on
    • Fix for respecting different near/far clip plane values when using multiple cameras in one scene
    • Fixed bug which caused Unity to crash on application close.
    Download URL:
    http://beta.unity3d.com/download/edcd66fb22ae/download.html
    ---------------------------------------------------------------------------------------------------------------------

    Release Notes:
    • Improved CPU/GPU synchronization which can result in significant performance improvements for CPU/GPU bound titles.
    Bug Fixes:
    • Fixed an issue which prevented Holographic Simulation or Remoting from working on Windows Fall Creators Update builds (case 952039)
    • Fixed Asserts triggering when playing a Windows Mixed Reality application in the Editor if the Mixed Reality Portal was not running (case 950519)
    • Fixed an issue that prevented Unity from updating its culling frustum if the Windows API failed to return culling data (case 927404)
    • Guarded against a potential crash if Windows Mixed Reality APIs don't return a valid camera back buffer (case 948814)
    • renderViewportScale fixes
      • Changing renderViewportScale with anti-aliasing causes the app to freeze (case 916194)
      • Viewport scaling changes scale around the bottom-left corner instead of the center when the setting is lower than 1 (case 916192)
    • Tracking-space and tracking-loss fixes
      • Can't set tracking-space type to Stationary (case 946305)
      • Tracking-loss screen renders badly and it shouldn't at all on opaque headsets (case 942154)
      • Tracking loss type is not falling back to stationary when setup has not been configured (case 945163)
    • Windows MR reports incorrect grip-pose rotation (case 949198)
    • You can now correct for controller jitter by updating their poses' information in OnPreRender (case 948954)
    • Fix for crash when toggling XRSettings.enabled off and then on again (case 952997)
    • Fix for incorrect velocity of controllers being reported relative to starting orientation instead of world origin (case 953023)
    • General lifetime and start-up fixes:
      • Fixed an issue which prevented Holographic Simulation or Remoting from working on Windows Fall Creators Update builds (case 952039)
      • Fixed Asserts triggering when playing a Windows Mixed Reality application in the Editor if the Mixed Reality Portal was not running (case 950519)
      • Fixed an issue that prevented Unity from updating its culling frustum if the Windows API failed to return culling data (case 927404)
      • Guarded against a potential crash if Windows Mixed Reality APIs don't return a valid camera back buffer (case 948814)
      • Controllers now picked up and work in play-in-editor. Note: you may still encounter issues . Restarting the controller should fix this. (case 934611)
    Known Issue:
    There was a regression in f2-Custom that resulted in the left and right eye positions being centered on the center, but aligned to the world x-axis, and offset in world space rather than local transform space. That means that they will be incorrect as a function of your starting orientation relative to world space. In the default most common case (looking forward in the space that you set up) you will likely not notice this. The further you are off from that orientation, the more substantial the error. The end result is that for items close to the user, there is a larger visual disparity than there should be. This may be perceived as an object being in the wrong position, and/or appearing as a double image.

    Download URL:

    http://beta.unity3d.com/download/b9a6355603bd/download.html
     
    Last edited: Nov 22, 2017 at 9:48 PM
  2. whitebozo

    whitebozo

    Joined:
    Oct 27, 2014
    Posts:
    24
    So I am using Hololens with vuforia but can't seem to download Vuforia for this version
     
  3. misher

    misher

    Joined:
    Apr 22, 2016
    Posts:
    8
    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.
     
  4. whitebozo

    whitebozo

    Joined:
    Oct 27, 2014
    Posts:
    24
    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.
     
  5. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
    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?
     
  6. Barkers-Crest

    Barkers-Crest

    Joined:
    Jun 19, 2013
    Posts:
    128
    @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.
     
    Last edited: Oct 7, 2017
  7. ScottF

    ScottF

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    67
    This build should ONLY be used for Windows MR (VR) titles. Please continue to use official builds for HoloLens. These special build do not include any other platforms including Vuforia.

    We will have all of these fixes merged into early patches to unblock any issues you may have with HoloLens and Vuforia combination.
     
  8. whitebozo

    whitebozo

    Joined:
    Oct 27, 2014
    Posts:
    24
    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.
     
  9. SimonDarksideJ

    SimonDarksideJ

    Joined:
    Jul 3, 2012
    Posts:
    1,582
    SO @ScottF are you saying these fixes WILL be in RC 3? or that this "patch" release just includes RC3 fixes?
     
  10. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
    So did this stuff get put into the actual release?

    Says it did in the release notes.

    Should we use formal release or MRTP?
     
  11. SimonDarksideJ

    SimonDarksideJ

    Joined:
    Jul 3, 2012
    Posts:
    1,582
    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 ?
     
  12. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
    It's not like Microsoft has pushed the Fall Creator's Update so people running vanilla windows couldn't use the official release anyway.
     
  13. demonixis

    demonixis

    Joined:
    Aug 20, 2013
    Posts:
    48
    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!
     
  14. ScottF

    ScottF

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    67
    Yes, if you need the MRTP fixes you need this custom build. These fixes will all be rolled into mainline builds in p1 and p2. We did not want to introduce additional risk in the final days of RC2 so we opted to use these custom builds.
     
  15. demonixis

    demonixis

    Joined:
    Aug 20, 2013
    Posts:
    48
    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.
     
  16. Barkers-Crest

    Barkers-Crest

    Joined:
    Jun 19, 2013
    Posts:
    128
    How is it not working for you? Compile error or runtime issue?
     
  17. caiojahara

    caiojahara

    Joined:
    May 9, 2017
    Posts:
    15
    Download link for UnitySetup-Metro-Support-for-Editor-2017.2.0f3-MRTP.exe not working.

    Anyone has the correct url?
     
  18. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
    @ScottF Is there no way to tell the difference between the two 2017.3.0f3 MRTP updates?

    The build numbers are the same.
     
    Last edited: Oct 17, 2017
  19. demonixis

    demonixis

    Joined:
    Aug 20, 2013
    Posts:
    48
    @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.
     
  20. ScottF

    ScottF

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    67
    Yes sorry for this :( We will make sure on future spins we increment the MRTP number. In the meantime if you go to the Help -> About, Press Alt and the changeset hash will be shown.
     
  21. demonixis

    demonixis

    Joined:
    Aug 20, 2013
    Posts:
    48
    @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.
     
  22. _Abstiens

    _Abstiens

    Joined:
    Aug 17, 2015
    Posts:
    1
    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
     
    Last edited: Oct 23, 2017
    stechmann likes this.
  23. rAigner

    rAigner

    Joined:
    Sep 27, 2017
    Posts:
    9
    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?
     
    Last edited: Oct 25, 2017
  24. solidsnake530

    solidsnake530

    Joined:
    Feb 9, 2017
    Posts:
    1
    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.
     
  25. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
    @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.
     
  26. Lostlogic

    Lostlogic

    Joined:
    Sep 6, 2009
    Posts:
    646
    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?
     
  27. H-Kuribara

    H-Kuribara

    Joined:
    Jul 14, 2012
    Posts:
    5
  28. DionPurnell

    DionPurnell

    Joined:
    Oct 24, 2017
    Posts:
    1
    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
     
  29. NickLandry

    NickLandry

    Joined:
    Oct 12, 2016
    Posts:
    2
    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.
     
  30. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
  31. ChimeraScorn

    ChimeraScorn

    Official Microsoft Employee

    Joined:
    Apr 20, 2017
    Posts:
    21
    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. :)
     
  32. helenma

    helenma

    Joined:
    Nov 8, 2017
    Posts:
    1
    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?
     
  33. adamz

    adamz

    Joined:
    Jul 18, 2007
    Posts:
    807
    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.
     
  34. HD30

    HD30

    Joined:
    Dec 30, 2015
    Posts:
    4
    I have similair issues, so following...
     
  35. SimonDarksideJ

    SimonDarksideJ

    Joined:
    Jul 3, 2012
    Posts:
    1,582
    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.
     
  36. hellobard

    hellobard

    Joined:
    Sep 26, 2012
    Posts:
    98
    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.
     
  37. adamz

    adamz

    Joined:
    Jul 18, 2007
    Posts:
    807
    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.
     
  38. SimonDarksideJ

    SimonDarksideJ

    Joined:
    Jul 3, 2012
    Posts:
    1,582
    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.
     
  39. adamz

    adamz

    Joined:
    Jul 18, 2007
    Posts:
    807
    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.
     
  40. Skyfly

    Skyfly

    Joined:
    Jan 25, 2014
    Posts:
    87
    btw, has any of you tried your unity project with the steamVR beta (not using this special build)? Any showstopping bugs?
     
  41. tolosaoldfan

    tolosaoldfan

    Joined:
    Sep 14, 2012
    Posts:
    55
    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.
     
  42. JariEligo

    JariEligo

    Joined:
    Oct 26, 2017
    Posts:
    1
    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.
     
    tolosaoldfan likes this.
  43. tolosaoldfan

    tolosaoldfan

    Joined:
    Sep 14, 2012
    Posts:
    55
    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
     
    Last edited: Nov 15, 2017
  44. Skyfly

    Skyfly

    Joined:
    Jan 25, 2014
    Posts:
    87
    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.
     
  45. StephenHodgson-Valorem

    StephenHodgson-Valorem

    Joined:
    Mar 8, 2017
    Posts:
    54
    Can we get an updated MRTP build based on the 2017.2.0p2 release please?
     
  46. adamz

    adamz

    Joined:
    Jul 18, 2007
    Posts:
    807
    @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.
     
  47. ivan20071

    ivan20071

    Joined:
    Nov 15, 2017
    Posts:
    1
    Launch Download Assistant and select Windows Store .NET Scripting Backend
     
    tolosaoldfan likes this.
  48. adamz

    adamz

    Joined:
    Jul 18, 2007
    Posts:
    807
    That worked, thanks.
     
  49. MrMatthias

    MrMatthias

    Joined:
    Sep 18, 2012
    Posts:
    64
    I can haz MRTP 5?
     
  50. SimonDarksideJ

    SimonDarksideJ

    Joined:
    Jul 3, 2012
    Posts:
    1,582
    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.