Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more..
    Dismiss Notice
  3. Dismiss Notice

HL2 Holographic Emulation - Hands tracking not working

Discussion in 'VR' started by AmirBarak51, Jul 14, 2020.

  1. AmirBarak51

    AmirBarak51

    Joined:
    Jul 14, 2020
    Posts:
    9
    Unity 2019.4.3f1 (LTS)
    MRTK 2.4.0 installed

    Trying to set up HL2 with holographic emulation; works nicely with the deprecated framework but I'm not getting the articulated hands - I can see a gameobject created for the hand (right/left) but no movement. And when I switch to the new XR SDK I'm getting hands but remote window disconnects every time I stop playmode and I'm getting some strange exceptions (null reference on something called _unity_self and memory leak on native collections - with a crash every once in a while). I'd love to work with the new SDK obviously but if not then how do I get articulated hands from the deprecated holographic emulation?
     
  2. AmirBarak51

    AmirBarak51

    Joined:
    Jul 14, 2020
    Posts:
    9
    For anyone interested; I've not managed to get the new holographic remoting to work properly (or even stably) with the HoloLens 2 device. So I've reverted back to the deprecated version. That said, there seems to be an issue with the MSBuild for Unity package in Unity 2019.4 so I had to download a nuget client designed for Unity and manually get the required DotNetWinRT.dll dependency. Can follow the instructions here: https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/Tools/HolographicRemoting.html
     
  3. JasonCostanza

    JasonCostanza

    Unity Technologies

    Joined:
    May 23, 2017
    Posts:
    400
    Hello,

    Which version of the Windows SDK did you install? The only thing we can think of at the moment is perhaps you have the wrong version of the SDK installed. To our understanding, DotNetWinRT.dll is shipped with Windows so you should not have to add this manually. Have you brought up this issue to Microsoft as well?