3dsmax Output Gamma problem

Hi,

I can’t manage to make my gamma correction settings to work with deadline max submit script,
it renders too dark…

Here is how I set it up :

I leave input and output to 1.0 in order to set it up manually for each bitmap,
because I leave HDRs to 1.0 and set other bitmaps to 2.2.

For my renders, I leave output to 1.0 when working with EXRs, and 2.2 when working with TGAs, by overriding it like this :

And it seems that deadline don’t consider this parameter.

Any ideas ?

Thanks

We can reproduce the problem. We’ve determined that when Deadline loads max, it recognizes the gamma correction settings saved in the scene, but for whatever reason it doesn’t respect the gamma override in the output options like you mention. We’re still trying to figure out why this is, but in the meantime, you could try using the 3dsCommand plugin instead (we’ve confirmed that it works fine using this plugin).

Setting up the 3dsCommand submission script:
franticfilms.com/software/su … tsetup.php

See the FAQ for the differences between this plugin and the original 3dsmax plugin:
franticfilms.com/software/su … riginal.3F

If we happen to figure out this problem, we’ll let you know.

Cheers,

  • Ryan

Thanks, i’ll try this.

It looks like we’ve figured out why this problem was occurring with the 3dsmax plugin. The fix will be included in the upcoming 3.1 SP1 release.

Cheers,

  • Ryan

Hi,

i did some tests… and here is the results, first my reference test scene localy rendered :

Then the max script renders :

And the cmd script renders :



Strange, isn’t it ?
First thing to notice is that cmd renders don’t keep area shadows and glossy effects.

So, my conclusion about gamma is :
*For the max script
- the only one good render is the max script one with exr output with defaut gamma.
- the tga one shows the gamma correction override not kept problem
*For the cmd script
- the renders are close to reference one only when output gamma is forced, but a little different from each other

I hope it’s clear enough to expose the problem.
It’s easer to compare by stacking pictures in photoshop.

Here is my simple test scene, max 2009 :
http://zoneftp.digital-chalet.com/test/DeadLineTest.zip

Yeah, the forcing of the gamma settings is necessary for the 3dscmd plugin because those values need to be passed to the 3dsmaxcmd.exe renderer. Not sure why max requires them to be forced, since you would assume it would just use the values defined in the scene file by default. In this case, everything is handled by the 3dsmax command line renderer, so there probably isn’t much we can do about the slight difference. It would be interesting to see if you got identical results using backburner…

As mentioned in my previous post though, the gamma bug in the 3dsmax plugin should be fixed in the upcoming 3.1 SP1 release, which we hope to get out mid-June.

Cheers,

  • Ryan

OK, great for the update !

and thanks for your quick answer.

Cheers

so to be clear is there a check box within 3dsmax submission to set gamma on each 3ds max cclient no matter what the setting is within 3ds max preferences?

Not in the 3dsmax submission script. The gamma override settings are only for the 3ds Command submission script, since those are passed to the 3dsmaxcmd.exe command line renderer.

3dsmax submission:
software.primefocusworld.com/sof … 3dsmax.php

3ds Command submission:
software.primefocusworld.com/sof … ommand.php

Hope that clears things up.

Cheers,

  • Ryan