If you are waiting for it, it is finally released…
no, thanks. :roll:
Indeed…
Yes, thanks. 
No, please not again!
This is the worst piece of code ever to be written for max.
Its got everthing to bring your farm to a grinding halt:
memory leaks, stopping max from closing between jobs, missing versions,
everything you could possibly do wrong in a plugin, this has it all.
Someone even wrote a script to remove this from scenes.
It cost me so many work hours that i even started to hate the programmer on a personal level.
Hehehe…that seems a tad harsh given it was free 
Some people saying that MAX color correction is a shit compared to this, then the inverse…so what should i believe? 
I installed recently and uninstalled due to some freezes but really dont know if is worth having the max a native map…
We’re currently switching to something in-house. The main issue with ColorCorrect has been that you never new if a fix, a recompile for a new version etc. would be coming or not. So that could really be a showstopper for upgrading.
Regards,
Thorsten
I don’t blame the developer. After all it’s a free plugin. The problem is how a single corrupt plugin can ruin whole scenes files and material trees in max.
I pretty much stopped using 3rd party map plugins and modifiers (except vray’s of course) because of the color correct fiasco.
whats wrong with using maxes native colorcorrection map? i use it quite extensively with no error…there is no need for thisrd party plug anymore IMO
Thanks a lot !
I use this plugin and like it a lot. Even when buggy, I couldn’t stop using it and now feel happy to learn new version is there 
i think there were some limitations with original max color correct like clamping of the output or something. But now its all resolved and I personally don’t see a reason or need to have this plugin, provided how unstable it can be.
It is still wit a bug, even more serious.
I am on 3dsMax 2011 and every second time I click on the ColorCorrect in material editor, max crashes.
But I must state that the problem can be because of old material-map browser; I am using this instead of Autodesk one.
I switched back to the old beta version and the problem disappeared.