M_remoteContext.Connect(m_hostname, m_port) ĭebugLog(L'Connect failed with hr = 0x%08X', e.code()) The port used by the Holographic Remoting Player is 8265. To establish a connection from the remote app to the player device, call the Connect method on the remote context specifying the hostname and port. The player running on the device connects to the remote app.

The remote app connects to the player running on the device.When the remote app is ready for rendering content, a connection to the player device can be established.Ĭonnection can be done in one of two ways. m_holographicSpace = winrt::Windows::Graphics::Holographic::HolographicSpace::CreateForCoreWindow(nullptr) Desktop apps that don't have a CoreWindow can just pass a nullptr. Next the holographic space needs to be created. Never mix objects created or retrieved through any Windows Mixed Reality API before the call to CreateRemoteContext with objects created or retrieved afterwards. The recommended approach is to create the remote context as early as possible before interaction with any Mixed Reality API. For that reason any call on any Windows Mixed Reality API before creating the remote context can result in unexpected behavior. This is done during the creation of the remote context. Holographic Remoting works by replacing the Windows Mixed Reality runtime which is part of Windows with a remoting specific runtime. The C++ holographic project template is a good starting point. For details, see DirectX development overview. PrerequisitesĪ good starting point is a working DirectX-based Desktop or UWP app that targets the Windows Mixed Reality API. The player app can report the latency in real time.Īll code on this page and working projects can be found in the Holographic Remoting samples github repository. A typical remoting connection will have as low as 50 ms of latency. Additional code is required which handles the connection and renders in an immersive view. Holographic Remoting is added to a desktop or UWP app via a NuGet packet. The connection is made using standard Wi-Fi. A remote app receives an input data stream from HoloLens 2, renders content in a virtual immersive view, and streams content frames back to HoloLens 2. You can also access more system resources and integrate remote immersive views into existing desktop PC software. Holographic Remoting apps can stream remotely rendered content to HoloLens 2 and Windows Mixed Reality immersive headsets. The documentation for HoloLens 1 can be found here. This implies that remote applications written for HoloLens 2 are not compatible with HoloLens 1 and vice versa. Remote applications for HoloLens (1st gen) must use NuGet package version 1.x.x. This document describes the creation of a remote application for HoloLens 2 using the HolographicSpace API.

Microsoft desktop remote resources busy