WEIRD GAMA RESULTS IN NET RENDERING

attached are two images. one was rendered on my local machine through SR and the other through net rendering (I did save the settings of SR before sending). I think this has to do with a gamma setting somewhere but can not figure it out.

from SR on local machine... ripplecg.com/Client-Development/testing/scrnsht/test-91.jpg
From SR rendered to network... ripplecg.com/Client-Development/testing/scrnsht/test-92.jpg
Please help.

Any comments to this? I would like some support if possible.

Thank you!

I have some simular problem. I originaly thouht it was a gamma problem but after a lot of research I found out the HDRI map didn't load on the rendernodes using backburner. Now I just don't use HDRI lighting with netrendering and everything is ok. Maybe it's something simular?

That did not seem to make difference for me. Here are the issues...

1. Using distributed rendering - the Gamma is set to 2.2 in the render window on my local machine. This blows the image out. Once the rendering has finished, I close it and click on the "show Last" button in SR and the rendering shows up with the correct gamma of 1.

2. If I save the settings from SR, close it and use backburner for network rendering, the gamma remains at 2.2 on the output file and the images are rendered at 2.2 (blown out). I finsally figured out that I have to manually set the gamma back to 1 after saving the SR settings before I use back burner on the network.

to say the least I am very confused as to how SR handles Gamma and quite frankly, in the beginning, my test render results were misleading using distributed rendering. I need to know if this is a bug or if I need to set something up differently.

thank you.

To answer your question, I have tried both the Vray Frame Buffer and the Max standard Frame Buffer. When I used the Vray VFB, my results always came out correct however I cannot use the Vray VFB in SR as it defaults to the Max standard VFB. It seems that Max’s VFB needs another setting to control the gamma in the material editor only. For SR, one possible solution could be to set SR gamma to 1.0 at render time and then back to 2.2 once the VFB is closed. Another why might be to close the VFB and reopen it through the “show last” command – I am not sure why this works, but it does.
In my testing these were the results I found…

Max Frame Buffer with SR off:
1. Max Gamma set to 2.2 with bitmap files at "input-2.2" and "output-1.0"
a. Max VFB = image displays at gamma 2.2 and saves at gamma 1.0 (material editor= 2.2).
2. Max Gamma set to 1 with bitmap files at input-2.2 and output-1.0
a. Max VFB = image displays at gamma 1.0 and saves at gamma 1.0 (material editor= 1.0)

Max Frame Buffer with SR on:
1. By default Max Gamma is set to 2.2 with bitmap files at "input-2.2" and "output-1.0"
a. Max VFB = image displays at gamma 2.2 and saves at gamma 1.0 (material editor= 2.2).
note, if I close the frame buffer and click on the "show last" button from SR, the VFB displays at 1.0.

Vray Frame Buffer with SR off:
1. Max Gamma set to 2.2 with bitmap files at input-2.2 and output-1.0
a. Vray VFB = image displays at gamma 1.0 and saves at gamma 1.0 (material editor= 2.2)IDEAL
2. Max Gamma set to 1 with bitmap files at input-2.2 and output-1.0
a. Vray VFB = image displays at gamma 1.0 and saves at gamma 1.0 (material editor= 1.0)
Note, SR does not use Vray Frame buffer so the results in the frame buffer will be misleading when rendered at gamma 2.2.

SR Gamma:
By default SR is set to the Max VFB. I think this standard is important to keep for network rendering. Moving to the Vray VFB could be problematic. It would be nice to have a choice though.

Please give me your thoughts on this