What's New in Holoscan 4.3: Easier Operators, Safer Holoviz, and Runtime Fixes

Written May 28, 2026

Holoscan SDK 4.3 is a focused release that smooths the developer path after the larger GPU-resident graph and production-stack updates in Holoscan 4.2. The headline changes are small in surface area but meaningful in day-to-day application work: less boilerplate when customizing operators, clearer Holoviz behavior on production displays, and fixes in the message and metadata path that matter for distributed and multi-operator applications.

You can grab it today as a Docker container (v4.3.0-cuda13, v4.3.0-cuda12-dgpu, v4.3.0-cuda12-igpu), a Python wheel for CUDA 12 (holoscan, pip install holoscan==4.3.0) or CUDA 13 (holoscan-cu13, pip install holoscan-cu13==4.3.0), or as Debian packages (4.3.0.1-1).

Operator Initialization Is Simpler

Custom operators no longer need to explicitly call Operator::initialize() from their own initialize() override. The framework now runs the required framework-level initialization after the user override returns, including GXF codelet registration, port unique-ID assignment, and execution-context creation.

This removes an easy-to-miss step from operator authoring, especially for teams building larger internal operator libraries. Existing operators that already call Operator::initialize() do not need to change: the call remains safe and idempotent.

void MyOperator::initialize() {
  // Custom setup can live here.
  // Calling Operator::initialize() is optional in Holoscan 4.3 and later.
}

Holoviz Fails More Clearly

The 4.2 release notes called out a known issue with PresentDoneCondition on platforms where the VK_KHR_present_wait Vulkan extension is not available. In 4.3, PresentDoneCondition now catches that missing-extension path, logs a clear error, and stops fragment execution cleanly instead of terminating from its background thread.

For applications that need display-paced execution on platforms such as NVIDIA IGX Thor or Jetson Orin configurations without VK_KHR_present_wait, FirstPixelOutCondition remains the recommended alternative.

Better Guidance for 10-Bit Visualization

Holoviz now emits a startup warning when the selected swapchain surface format is 8-bit and an application uses 10-bit input formats such as A2B10G10R10_UNORM_PACK32 or A2R10G10B10_UNORM_PACK32.

That warning makes display-path behavior explicit: those 10-bit inputs will be quantized to 8-bit unless the output path is configured for 10-bit presentation. For video, medical imaging, and sensor applications where visual fidelity is part of system validation, this makes a subtle configuration issue easier to catch during bring-up.

GXF 5.7 Under the Hood

Holoscan 4.3 pulls in GXF 5.7, continuing the runtime alignment work from 4.2. Most developers should experience this as a compatibility and stability update rather than an API-level change, but it is an important part of keeping the Holoscan execution substrate current for long-lived edge deployments.

Metadata Emit Crash Fixed

This release fixes a crash when emitting a GXF Entity that already contains a MetadataDictionary component. Metadata is central to multi-stage pipelines that need to carry timing, provenance, and other side-channel context across operators, so this fix is especially useful for applications that forward existing entities rather than rebuilding messages at each stage.

Getting Started

The fastest way to try 4.3 is pip install holoscan==4.3.0 (CUDA 12) or pip install holoscan-cu13==4.3.0 (CUDA 13), or pull the container from NGC. Full details, including platform compatibility and the complete release notes, are in the Holoscan SDK User Guide and the Holoscan SDK release notes. Join the conversation on the NVIDIA Developer Forum or Discord, and explore the source on GitHub.