Kit 110.2 Release Highlights#
Release Date: July 2026
Kit 110.2 is a feature and stability release delivering expanded point cloud streaming workflows, Gaussian Splat ingestion, RTX rendering parity and correctness improvements, and Sensor Processing Graph API maturation. It also delivers an updated Content Browser that allows unified access to Omniverse Storage, Omniverse Nucleus, and HTTP storage.
Gaussian Splat Converter#
Kit 110.2 ships a new Gaussian Splat Converter extension, enabling developers and artists to bring Gaussian Splat capture data directly into Omniverse workflows without external tooling.
New omni.kit.converter.gsplat Extension#
The new omni.kit.converter.gsplat extension uses the usd-convert-gsplat Python library to ingest .PLY and .SPZ Gaussian Splat files and write USD stages conforming to the Gaussian Splat USD schema. Converted assets render correctly in the Omniverse Viewport and Isaac Sim on both Windows and Linux, and the extension supports drag-and-drop and programmatic import patterns within Kit-based workflows.
For a full list of changes, see the Kit 110.2 Release Notes.
Point Cloud Streaming#
Kit 110.2 delivers a major expansion to point cloud streaming capabilities, targeting factory digital twin and reality capture workflows. New features span multi-site connectivity, spatial filtering with USD-conformant bounding boxes, adjustable render settings, and deeper USD integration for point cloud data management.
Multiple Simultaneous Site Connections#
Point cloud streaming now supports connections to multiple reality scan dataset instances at once. Use Add Pointcloud Source URL in the Content Browser to connect to and stream from multiple NavVis IVION or compatible reality scan sites simultaneously, enabling side-by-side comparison and analysis of complex environments.
Inclusion and Exclusion Bounding Boxes#
Point cloud streaming now supports multiple inclusion and exclusion bounding boxes per prim. Inclusion boxes restrict streaming to selected spatial regions; exclusion boxes suppress streaming within defined areas. Bounding box masks are represented as USD Box prims, so they can be loaded from and saved to the stage using standard selection tools. This reduces data streaming overhead outside defined regions and enables precise spatial editing workflows.
Point Cloud Extraction and USD Representation#
Point cloud operators in Point Cloud Manager now accept USD Points prims and NVSealedUsdArchives (streamed point clouds) as both input and output. Extracted point selections can be represented on the USD stage and co-rendered with the scene, outputting either USD Points prims or new streamed point clouds with the extracted points excluded from the source stream. GeomPoints prims can also be maintained as a separate point cloud streaming instance, with LOD selection boxes that move with their associated LOD prims.
Adjustable Streaming Render Settings#
Streamed point cloud rendering settings — point size, shape, orientation, quality, and global illumination — are now adjustable in the UI and configurable via config file, with changes persisting across sessions. Render quality preset changes take effect immediately, and modified detail values are retained when switching presets.
Fabric Selection for Streamed Point Clouds#
Streamed Potree point clouds now support Fabric selection in omni.pointcloud.streaming.potree, enabling standard viewport selection workflows against streamed point cloud data.
PTS Importer Improvements#
The PTS importer gains large file support via GPU buffer limit scan splitting, FlatPoints MDL material assignment, RTX Point Material and Scan Split Factor UI controls, and drag-and-drop import directly from the Content Browser. Example converter scripts for transforming E57, PTS, and LAS/LAZ point cloud datasets into Potree 2.0 format are also available as part of the Point Cloud Manager tools.
Point Cloud Streaming Stability#
Selection of point cloud prims for sealed USD archive elements now works correctly with the omni.pointcloud.potree2 extension. Application crashes in the Potree2 hierarchy decoder during point cloud streaming on Windows are fixed, and added NavVis servers now persist across Content Browser open/close cycles. OpenSSL is upgraded to 3.5.7 in omni.pointcloud.streaming.potree.
For a full list of changes, see the Kit 110.2 Release Notes.
RTX Rendering#
Kit 110.2 closes several long-standing RTX feature gaps relative to Iray, resolves correctness issues across path tracing and post-processing, and adds developer-facing controls for denoising and anti-aliasing workflows.
OptiX Denoiser Invocation Mode#
A new /rtx/pathtracing/optixDenoiser/invocationMode render setting lets developers toggle the OptiX denoiser between running per-iteration (interactive rendering) and running once per final frame (offline rendering). This reduces overhead when using lower samples-per-pixel counts in offline capture workflows.
Gaussian Splatting in RTX Minimal#
Gaussian Splatting rendering in camera rays is now supported in RTX Minimal mode, including all render modes, sorting modes, and color blending modes.
DLAA as an Execution Mode#
DLAA (Deep Learning Anti-Aliasing) is now available as a named Execution Mode alongside Performance, Balanced, Quality, and Ultra-Performance in RTX render settings, making it straightforward to select and persist the AA mode programmatically or via the settings UI.
Dome Light Iray Parity#
RTX renderer dome light functionality now achieves parity with Iray — including environment dome and implicit ground plane capabilities — so developers migrating applications from Iray to RTX retain full dome light feature support for their users.
Light Path Expressions (LPEs) for AOVs#
RTX renderer now supports Light Path Expressions (LPEs) for AOV outputs, reaching feature parity with Iray for applications that rely on LPE-based render passes. The RTX Path Tracer also supports LPEs as AOVs, enabling per-channel rendering of specular, glossy, and other light transport components equivalent to Iray canvases.
MaterialX Custom Type Definition Support#
MaterialX documents with custom type definitions are now supported, enabling compatibility with MaterialX 1.39.3 and later. MDL modules generated from MaterialX are registered under a dedicated MDL search path, enabling shorter qualified module names and more reliable compilation pipeline hashing.
Curve Opacity in Path Tracing#
Curve transparency now renders correctly in RTX Path Tracing mode. Previously, cutout opacity transmission was missing for curves, causing them to appear fully opaque in PT mode while rendering correctly in RT 2.0.
Renderer Enable/Disable Persistence Fixed#
Disabling the Interactive and Real-Time 2.0 renderers via Settings, CLI arguments (--/persistent/rtx/modes/pt/enabled=false, --/persistent/rtx/modes/rt2/enabled=false), or Foundation.cpp defaults now persists correctly across Kit restarts.
Dome Light Sampling Noise Fixed#
Dome light sampling no longer produces excessive noise in environment map–only mode. The dome light was incorrectly included in next-event estimation sampling; this is now corrected.
Texture Reload After Disk Changes#
Textures now reload automatically after being changed on disk, without requiring re-assignment, scene reload, or removal of all material references — a common friction point in iterative asset workflows.
RTX Lens Distortion Fixes#
Two long-standing issues with OmniLensDistortionLutAPI are resolved: changes to lens distortion LUT settings now appear immediately in the RTX viewport, and the renderer no longer crashes when distortion maps are missing.
Backplate Texture Relative Path Resolution#
Relative paths set for rtx:post:backgroundZeroAlpha:backplateTexture now resolve correctly. Previously, the renderer failed to locate the texture unless an absolute path was provided.
OpenPBR Specular Lobe Fix#
OpenPBR materials now correctly disable the specular lobe when specular weight is set to 0.0 and specular IOR is set to 1.0, resolving incorrect specular highlights in RT2 and Path Tracing modes.
Updated Content Browser#
The new Content Browser unifies access to Omniverse Storage, Omniverse Nucleus, and HTTP-based backends in a single streamlined file browser. You can now easily add an Omniverse Storage deployment, Nucleus server, or HTTP connection with a simple click of the Add {connection-type} buttons. Your connection types are now conveniently grouped so they are easy to find and understand where your data is coming from. The HTTP group now holds your HTTP, S3, and Azure connections all together in one location.