[MetinSeven_com]

What happens if you don't use IBL? Does it also happen with emitter-only illumination?

Yep, same issue:



The first image I showed, with the toy figure, also had only scene lights.

[tom]

So, when you save the image from maxwell.exe and open in PS, does it still come overburn?

[MetinSeven_com]

Yes, after rendering I see exactly the same image in Photoshop and XnView. The oversaturation and overexposure is really rendered into the image. It's not a matter of adjusting some parameters in Photoshop in order to get the render as it should. The only workaround right now is to set the burn value to 0.2 and rendering to 32 bit TIFF, so I can really adjust the image in Photoshop afterwards.

There's another recent hardware change, maybe that might have anything to do with this? Next to my new Dell monitor I also changed my CPU to a Hexa Core.

[tom]

Very interesting because I just can't reproduce it, yet. Probably, you should share this scene and everybody can check.

[MetinSeven_com]

No problem, here's the simple scene (3ds Max 2011).

I hope the issue can be reproduced on a system other than mine.

There are three possible suspects in this matter that I can think of:

- Color management using the freeware color calibration tool Calibrize. But I've been using this for quite some time now. Worked fine with previous Maxwell versions.
- Dell UltraSharp U2711 monitor (and/or its drivers).
- Intel Core i7 970 Hexa Core processor (3.2 GHz, 12 MB cache)

The monitor and CPU are the only recent hardware changes in my machine. The only other thing that's changed around the same time is the installation of the latest Maxwell version with Fire.

[tom]

Yep. I exported it as an MXS, opened that in Maxwell Studio and rendered the scene in the Maxwell Studio viewport. Exactly the same oversaturated and overexposed result as in the Maxwell Render window.

Yes, same here but I must say what you see in maxwell.exe or studio.exe viewport is *the correct* output. I'm not sure why ActiveShade in 3dsmax renders it different/wrong. Moving this to 3dsmax plugin section. Thanks Metin!

[MetinSeven_com]

Thank you too Tom, much appreciated.

[Bubbaloo]

Maybe Max's Fire window (AS) is affected by Max's gamma settings. Do you have gamma correction enabled in Max?

[MetinSeven_com]

Nope, I don't have the Max gamma enabled. We already discussed that in this thread.

Or do you mean the gamma should be on in stead of off? Haven't tried that yet.

[Bubbaloo]

No, I always keep mine off.

[Bogdan Coroi]

This is a plug-in issue and will be fixed in the next update. Everything is darker with RS0 now (maxwell material previews and ActivaShade) due to this issue.

@Metin: Did you have this problem (ActiveShade having darker shades then maxwell) only with the latest plugin update or do you also have it in 2.5.3?

[MetinSeven_com]

Hi Bogdan,

Ok, good to know this. I was about to question my sanity.

I suspect the problem has been there since the first release of Maxwell with Fire (and the corresponding 3ds Max plug-in update), but I don't know that for sure.

Good luck fixing the issue. If you want me to test anything, just let me know.

Thanks!

[MetinSeven_com]

Hi Bogdan,

Do you have any idea when we can expect the Maxwell 3ds Max plug-in update with corrected color brightness? The current situation interferes with the workflow. When a material looks ok in the material editor, it is much brighter in the Maxwell renderer.

Thanks,

Metin

[Bogdan Coroi]

There will be an update available in a couple of days.

[MetinSeven_com]

Cool, thanks!