Hololight Stream release notes - v2025.0.3.0

NOTE

Documentation for all features, including upgrade guides, are available in the “Docs" folder in the Hololight Stream package. Most features also come with examples for how to use a given feature in a project. To import an example, import the “Hololight Stream Examples" package into your Unity project and load from the “Samples" section in the “Package Manager" window. Unity will then copy the example into the “Assets" folder.

Improvements

  • Fixed issue where a second, duplicate window would appear when using Hololight Stream Client for Apple Vision Pro. This could happen when using the Apple Vision Pro Digital Crown after connecting to a Hololight Stream server session. The duplicate window now won’t appear.

  • Fixed issue where enabling depth buffer when using Hololight Stream Client for Apple Vision Pro would automatically double the value of the bandwidth setting. The bandwidth is now unaffected by the depth buffer setting.

  • Fixed issue where the following error would appear when entering Play mode while using Hololight Stream in the Unity Editor:

    NullReferenceException: Object reference not set to an instance of an object
at (wrapper managed-to-native)HoloLight.Isar.Native.IsarServerApi.Create(HoloLight.Isar.Native.IsarServerApi&)
at HoloLight.Isar.BaseIsarLoader.Initialize () [0x000d2] in.\Library\PackageCache\com.hololight.stream@1f3aeb1eb731\Runtime\BaseIsarLoader.cs:320

Known issues and workarounds

  • Microphone capture can stop working as expected if it wasn’t actively turned off before disconnection. When this happens, the microphone capture is still enabled but has invalid data.

Unity

  • Hololight Stream does not officially support Unity 6. Using Hololight Stream with Unity 6 may work, but only after updating examples and dependencies.

  • Unity 2021.3 (LTS) and Unity 2022.3 (LTS) render visuals differently. Keep this in mind when upgrading to a newer version of Unity. This is a Unity issue and not related to Hololight Stream.

  • Exporting spatial anchors can fail. If this happens, retry the export. Most of the time this solves the problem.

  • Speech recognition does not allow updating keywords at runtime. Doing so can crash the Unity application. Instead, register all keywords on startup until this issue is resolved.

  • When initializing the Hololight Stream loader late, Hololight Stream Extensions cannot get the data channels correctly and some features do not work (For example, touchscreen support). We recommend setting the “Initialize XR on Startup" setting to true under “XR Plugin Management" inside the Unity project settings.

  • When viewing an application, either in the Unity Editor or through the application itself, there is visible culling of 3D objects when using single-pass instanced rendering.

  • Enabling debugging with DirectX 12 through the DirectX Control Panel will cause Unity to crash with DirectX 12 enabled in the project.

  • Single-pass instanced rendering in DirectX 12 is not supported in all Unity versions. In those cases, you might need to use multi-pass rendering instead, which is less efficient.

  • When using the camera stream feature and DirectX 12, Unity will show the following warning:

    d3d12: Creating a default shader resource view with dxgi-fmt=29 for a texture that uses dxgi-fmt=28

    We reported this issue to Unity, because the issue requires a fix on their side.

  • The Logitech MX Ink Stylus example does not support hands and controllers.

  • Changing settings may not work in the camera stream example when changing and applying those settings multiple times very quickly.

Unreal Engine

Using RenderDoc and D3D12 will lead to a locked state when connecting Hololight Stream Client to the server. When this happens you will only see a black image. Other graphical debuggers could potentially have similar effects on the Hololight Stream plugin.

Hololight Stream Client

  • Entered IP addresses will reset to their original value when switching between tabs.

  • On Hololight Stream Client for HTC VIVE, when connecting to the server application, the “Establishing connection" prompt is not visible. This does not affect the connection process and is purely cosmetic.

  • On Hololight Stream Client for Microsoft HoloLens 2, using the camera stream significantly impacts performance. The Microsoft HoloLens 2 itself also heats up significantly.

  • On Hololight Stream Client for Windows, there is visible screen tearing when using a faster refresh rate on the server than on the client. For example, screen tearing occurs when the server output is 240 Hz, but the display that Hololight Stream Client is using has a refresh rate of 60 Hz.

  • Using Hololight Stream Client for web browsers with certain versions of Safari, can result in connection issues under certain circumstances. Safari 26.1 and newer on macOS blocks WebSocket connections to private IP addresses like 192.168.x.x, 10.x.x.x, or 172.16-31.x.x. when connecting to WebGL applications built with Unity. However connecting using DNS addresses still works.

Meta Quest devices

  • When restarting a Meta Quest device in Meta Quest for Business mode, user data for Hololight Stream Client like connection history and bookmarks won’t be saved.

  • On Hololight Stream Client for Meta Quest 2 and Meta Quest 3s, the Hololight Stream trial version watermark appears correctly only when setting the optics to the minimal eye distance. Other eye distances will render the trial version watermark incorrectly shifted for the left and right eye.

  • The Hololight Stream trial version watermark of older Hololight Stream server versions will render twice when using the newest version of Hololight Stream Client for Meta Quest 3. We always recommend using the same server and client version.