Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix various bitstream issues #111

Closed
DavidWyand-GG opened this issue Nov 5, 2012 · 2 comments

Comments

Projects
None yet
1 participant
@DavidWyand-GG
Copy link
Member

commented Nov 5, 2012

Originally from THREED-3176, although cannot track down ticket any longer.

From Chris on Subversion check-in:
FIX - Prevent values packed using stream->writeFloat exceeding the expected (-1, 1) range. Add an assertion in BitStream::writeInt to catch when values are sent with insufficient bits. Add explicit bitmasks for integer values that are intended to be truncated by BitStream::writeInt. (THREED-3176)

@ghost ghost assigned DavidWyand-GG Nov 5, 2012

DavidWyand-GG added a commit that referenced this issue Nov 5, 2012

@DavidWyand-GG

This comment has been minimized.

Copy link
Member Author

commented Nov 5, 2012

Fixed merged into development branch.

@DavidWyand-GG

This comment has been minimized.

Copy link
Member Author

commented Nov 5, 2012

Original notes from Chris:

FIX - Prevent values packed using stream->writeFloat exceeding the expected (-1, 1) range. Add an assertion in BitStream::writeInt to catch when values are sent with insufficient bits. Add explicit bitmasks for integer values that are intended to be truncated by BitStream::writeInt. (THREED-3176)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.