Changelog#
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[1.3.1] - 2026-05-06#
Fixed#
observe_and_dispatchno longer drops repeated no-id messages from legacy clients. The 1.3.0 deduplication step keyed on the messageid; when an older client omitted the id,Nonewas added to the_seen_idsset on the first message and every subsequent no-id message of the same observed event type was treated as a duplicate. Dedupe is now skipped entirely whenid_valueisNone, so no-id requests are processed independently. (NVBug 6134051 / OMPE-92428)
[1.3.0] - 2026-02-19#
Added#
Added
omni.kit.livestream.messaging.largesubpackage for splitting, reassembling, and correlating large messages.Large message handling is active automatically in the base extension — no extra imports or configuration required.
Changed#
All outgoing messages now use a flat envelope where
id,part, andnumPartsare top-level fields alongsideevent_typeandpayload. Single-part messages omitpart/numPartsand carry the application dict directly inpayload; larger payloads are split intoMESSAGE_PART_SIZE_BYTES(≈16 KiB) chunks wherepayloadis a JSON-string chunk of the serialised application payload.Incoming messages carrying
id,part, andnumPartsat the envelope top level are buffered and reassembled before being dispatched; legacy clients that send a plain{ event_type, payload }envelope continue to work unchanged.
[1.2.1] - 2025-11-05#
Changed#
Added major.minor.patch kit lock version.
[1.2.0] - 2025-08-15#
Changed#
Added support for migration to Events 2.0, retaining backward compatibility.
Updated tests
[1.1.1] - 2024-04-17#
Changed#
Added support_level = “Enterprise”.
[1.1.0] - 2023-12-19#
Changed#
Split out webrtc setup to omni.kit.livestream.webrtc.setup
Forward API calls at module-level
[1.0.1] - 2023-12-15#
Added#
Fix resizing app window in USD Composer
[1.0.0] - 2023-12-13#
Added#
Initial version