MaxScript - Major Double GAMMA issues - Reset to default?!?

[Morne]

Hi all

I already posted this on CGTalk and Area, but since there's a also a bunch of smart people here...

I'm busy with a script, to RESET all gamma values to default. However, I'm have major intermittant issues and struggling to get to the bottom of it. Sometimes it works and simetimes it doesn't. Then suddenly, after running it a couple of times, modifying and essentially going back to the beginning, code that didn't work 5 minutes ago, suddenly works.

I'm getting double GAMMA issues, sometimes in the viewport AND in the material editor for bitmaps. Other times JUST the viewport. Then suddenly for no reason it starts to work. I tried with various different versions of Max at different offices (2014-2016), with the same results in each.

FreeSceneBitmaps()
gc light:true
IDisplayGamma.gamma = 2.2
IDisplayGamma.affectColorPickers = true
IDisplayGamma.affectMEdit = true
fileingamma = 2.2
IDisplayGamma.colorCorrectionPrefMode = #gamma
IDisplayGamma.colorCorrectionMode = #gamma
fileoutgamma = 2.2

I also tried using ONLY IDisplayGamma.colorCorrectionPrefMode = #gamma or only IDisplayGamma.colorCorrectionMode = #gamma
I also tried freeing bitmaps between each command.
I also tried using code and setting all gamma to 1 and then this code. Same result

I tried on a simple scene with a box and 2 bitmaps applied to different faces.
I also tried switching between realistic and shaded viewports, same story

What am I missing here?

[Bathyscaph]

Sorry I can't really offer any help so I will just commiserate with you.

I have a couple of scripts that use bitmaps and I never really found a clean, reliable way to deal with gamma issues over several different versions of max. I mostly gave up. 2017, so far, seems much better in this regard. I haven't tested it extensively but it seems like it does the right thing.