To see the issue, enter "0x800" on the hex part of the 16bit/half visualizer at the top -- and see it has the "one" in bit 16 not bit 12 as it should be, so it currently parses 0x800 as 0x8000, not the expected 0x0800.
Workaround for users: enter all leading zeroes completely.
To see the issue, enter "0x800" on the hex part of the 16bit/half visualizer at the top -- and see it has the "one" in bit 16 not bit 12 as it should be, so it currently parses 0x800 as 0x8000, not the expected 0x0800.
Workaround for users: enter all leading zeroes completely.