Gamma and Backburner

[Blake Warner]

Check job details in the backburner monitor to see what the gamma setting is.

[Mark Cronin]

Backburner is reporting 2.2 input and 2.2 output, but not what overide settings are applied at the save file stage.

[Matt McDonald]

Mark: Did you ever get this fixed? I'm having a nearly identical problem. One machine (out of a bunch) that just won't behave like the others. If you figured something out, I'd love to hear it. I can correct the gamma of my bad images but I'm using a lens effect glare shader which renders differently in the two gammas.

Thanks for your help
Matt

[Mark Cronin]

Hi Matt,

No, I never got to the bottom of it. I can't really remember now (it was a while ago) but I did some digging at the Area, and I came accross something about a known backburner error being the cause. It may be worth doing a quick search on their forums for an update though.

I didn't find a soultion, but my work around was to divide the animation up, sending a set number of frames to the problem PCs (with a different gamma overide on save setting changed), and render the remaining frames on the rest of the farm as usual. Annoying.

I'd be interested if you do find the cause! Good luck.

[Matt McDonald]

I seem to have had some success on this one. In my situation I was running backburner server under using an admin account. The machine has a daily user who logs in using a different account. I found the MAX.ini file for the admin account and deleted it. Viola! No more gamma problems.

I can't guarantee this will work for everyone but its sure did for me.

[Mark Cronin]

Cheers for the update. Good to know you got it sorted.

Hopefully I won't come accross the problem again, but if I do at least I'll know what to do to sort it!

Thanks.

[Justin Hunt]

designmule is correct, the gamma settings are save at a user level

I had a situation where all the machines were set up correctly then someone else logged in as a different user and every other frame came out wrong.

A real pain when your rendering 8000 frames AAAAAAAAAAAAAAAAAAAAGGGGGGGGGGGGGHHHHHHHHHHH

jhv

[Andrew Milford]

I had the same problem, but I overcame it by adding the following to each render node PC's 3dsmax.ini (assuming your own gamma is set to 2.2)

[Gamma]
LoadEnableState=1
CorrectColorPickerState=1
CorrectMtlEditorState=1
InputGamma=2.200000
OutputGamma=2.200000
LUTFileName=

I have a small batch file to update all the render nodes on startup with identical 3dsmax.ini, plugin.ini and installsettings.ini files. Setting useUserProfiles=0 in the installsettings.ini file ensures that 3dsmax.ini is read from the install location, not the user profile.

Regards

AM

[viks more]

I have scene setup with several objects with camera animation.

I am using FG and GI as indirect lighting. My FG and GI maps (already rendered after each 3 Frames). For single machine with my FG and GI maps everything is alright. But with the same maps I am rendering with Backburner (multiple machines) there are some gamma and flickering issues (I think FG and GI maps not read properly) appear within render frames. What's the problem actual is? any solution Please.

Thanks

[G Parmar]

justin i agree with you i was using vray with 2.2 gamma and have no problem before but now i got very dark render every time i render. just going to do some digging in this..

yaa but this is real paiiiiiiiiiiiiiiiinnnnnnnnnnnn