Skip to content

Commit 737b4c7

Browse files
committed
Add debugging HL2 remoting steps
1 parent 4ee0b4f commit 737b4c7

File tree

1 file changed

+19
-3
lines changed

1 file changed

+19
-3
lines changed

Documentation/Tools/HolographicRemoting.md

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ To enable remoting to a HoloLens, it is important to ensure that the project is
1010
- Verify that latest version of the **Windows Mixed Reality** package is installed.
1111
1. Ensure the latest Holographic Remoting application is installed, on the HoloLens, via the Microsoft Store.
1212

13+
### HoloLens 2
14+
1315
When using a HoloLens 2, support for remoting articulated hand and eye tracking data has been added to MRTK. To enable these features,
1416
configure the project using the following steps.
1517

@@ -21,6 +23,20 @@ configure the project using the following steps.
2123
1. Ensure that **Enable MSBuild for Unity** is selected
2224
1. Click **Apply**
2325

26+
### Debugging HoloLens 2 remoting via Unity package import
27+
28+
If HoloLens 2 hand joints and eye tracking aren't working over remoting, there are really three main potential points of failure:
29+
30+
- MSBuildForUnity package import via writing into the package.manifest
31+
- DotNetWinRT NuGet package resolution
32+
- DOTNETWINRT_PRESENT #define written into player settings
33+
34+
For the first, the best way to check is to open Window -> Package Manager and make sure MSBuild for Unity shows up in the packages list. If it's there, you can assume this step succeeded. If it's not there, try running Mixed Reality Toolkit -> Utilities -> Configure Unity repeat the stops above for running the MRTK Configurator.
35+
For the second, the best way to check is to search your Assets for DotNetWinRT.dll. If this doesn't exist, you'll want to navigate to MixedRealityToolkit.Providers / WindowsMixedReality / Shared / DotNetAdapter in your Project view and select DotNetAdapter.csproj. Assuming part 1 did succeed, you should see a custom inspector with Build, Rebuild, and Clean buttons. Try clicking Build or Rebuild, and then re-search for DotNetWinRT.dll. If that DLL now exists, this step succeeded.
36+
For the third, you'll want to navigate to your Unity Player Settings. From there, under the UWP tab, check under Other Settings for the Scripting Define Symbols. You'll want to make sure DOTNETWINRT_PRESENT is properly written in that list. If that's there, this step succeeded.
37+
38+
If you're through all three of those, hand joints over remoting should be working! If not, there might be something mis-set in your profiles for general hand joints on-device. In that case, ask a question on StackOverflow or file an issue on the GitHub repo for help.
39+
2440
## Connecting to the HoloLens
2541

2642
Once the project has been configured, a connection can be established to the HoloLens.
@@ -44,17 +60,17 @@ Once the project has been configured, a connection can be established to the Hol
4460
![Enter IP Address](../Images/Tools/Remoting/EnterIPAddress.png)
4561

4662
1. Click **Connect**.
47-
> [!Note]
48-
> If you cannot connect, make sure your HoloLens2 is not plugged in and restart Unity.
4963

64+
> [!NOTE]
65+
> If you cannot connect, make sure your HoloLens 2 is not plugged in to your PC and restart Unity.
5066
5167
## Starting a remoting session
5268

5369
With Unity connected to the HoloLens, enter play mode in the editor.
5470

5571
When the session is complete, exit play mode.
5672

57-
> [!Note]
73+
> [!NOTE]
5874
> There is a known issue with some versions of Unity where the editor may hang upon entering play mode during a remoting session. This issue may manifest if the Holographic window is open when the project is loaded. To ensure this issue does not occur, always close the Holographic dialog prior to exiting Unity.
5975
6076
## See also

0 commit comments

Comments
 (0)