So try this code:
global pPBitmap = "D:\\pivotPlacer.png"
rollout test_bitmaps "Testing Bitmap" (
bitmap the_bmp fileName:pPBitmap
)
createDialog test_bitmaps
with attached bitmap. In max 2014, it displays correctly, in max 2016, its too bright. Gamma correction is turned on in both programs, display gamma 2.2, affect color selectors and affect bitmaps on.
Anyone know what has changed between the two versions?
- Neil
Looks like display gamma is applied to UI bitmaps in Max 2016. Pretty sure this is totally undesired ? A workaround is setting it to 1.0 before rollout/bitmap creation and restoring the original value right after that
so something like this fixes it :
global pPBitmap = "D:\\pivotPlacer.png"
rollout test_bitmaps "Testing Bitmap"
(
bitmap the_bmp fileName:pPBitmap
)
oldGamma=displayGamma
displayGamma=1
createDialog test_bitmaps
displayGamma=oldGamma
EDIT: best to do a max version check, otherwise you will get dark bitmap displays in earlier/later Max versions. Would be a good candidate for a SP fix …
Yes this has definitely changed, I’m seeing a host of color issues in 2016 that I hadn’t previously seen. Max is overriding the gamma property of the bitmap. If you call display pPBitmap to see, it is correct in the bitmap but the UI element has been adjusted.
Thanks for the info guys. I have logged this as an official bug.
- Neil