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
I think there might be an issue with some of the fields being read out / unmarshaled using .readShort(), as this results in high end shorts (>32k) being negative. This could cause a few issues with lookups of enumerations - if they were populated that high.
So far in various simulation tools, I've encountered issues with ElectronicEmitterPdu, EntityStatePdu and the classes used within (EntityID, etc) but I'm sure any part of the standard that references 2-bytes needs to be unsigned, so probably stored internally as an int that's masked (0xFFFF). Some are, but some aren't. Unsure on the lack of uniformity.
Raising this for further discussion on resolution or my use-case. :-)
The text was updated successfully, but these errors were encountered:
@austinarrowsmith, looking through the EntityID and EE PDU classes, I'm seeing the proper masking during unmarshalling (& 0xFFFF) occurring for unsignedShorts in the src. Do you have another a specific reference in the src for where this is not occurring?
I think there might be an issue with some of the fields being read out / unmarshaled using .readShort(), as this results in high end shorts (>32k) being negative. This could cause a few issues with lookups of enumerations - if they were populated that high.
So far in various simulation tools, I've encountered issues with
ElectronicEmitterPdu
,EntityStatePdu
and the classes used within (EntityID
, etc) but I'm sure any part of the standard that references 2-bytes needs to be unsigned, so probably stored internally as anint
that's masked (0xFFFF
). Some are, but some aren't. Unsure on the lack of uniformity.Raising this for further discussion on resolution or my use-case. :-)
The text was updated successfully, but these errors were encountered: