You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In November 2025 a change was merged to open-dis-python which changed the "entityID" in EntityStatePDU from an "EntityID" type to an "EntityIdentifier" type. Doesn't this fundamentally break compatibility with the DIS standards? Also, it breaks compatibility with the other open-dis implementations (I'm seeing it on Python->Javascript). Am I missing something?
I'll note here that the packet format was never affected — both spellings serialize the same 6-byte Entity Identifier record (§6.2.28: site u16 + application u16 + entity number u16), so network interoperability with the other open-dis implementations is unchanged.
You're right, though, that the in-memory object shape changed, which breaks application-level code like your Python→JS glue that used the flat siteID/applicationID/entityID names.
Filing a PR for backward compatibility: #91 restores EntityID as an alias of EntityIdentifier, with property setters.
Activity
ngjunsiang commentedon Oct 18, 2026
I'll note here that the packet format was never affected — both spellings serialize the same 6-byte Entity Identifier record (§6.2.28: site u16 + application u16 + entity number u16), so network interoperability with the other open-dis implementations is unchanged.
You're right, though, that the in-memory object shape changed, which breaks application-level code like your Python→JS glue that used the flat
siteID/applicationID/entityIDnames.Filing a PR for backward compatibility: #91 restores
EntityIDas an alias ofEntityIdentifier, with property setters.fix(dis7): restore EntityID alias and legacy flat field names