Fix reading pixel values from single channel 16 bit image #439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Ian Chen [email protected]
🦟 Bug fix
Summary
Currently the Image class calls
FreeImage_GetPixelIndex
to access pixel values of a single channel image. However, this function does not support reading values from 16 bit images. This PR fixes the issue by implement our ownPixelIndex
function that includes logic for accessing the pixel value of 16 bit image types.Additional info: This is needed for loading 16 bit heightmaps. Currently it floods the console with
Image: Coordinates out of range
error msgs. This happens when theImage::MaxColor
call is looping through the image pixels and callingFreeImage_GetPixelIndex
function that fails on every iteration.Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.