Announcement

Collapse
No announcement yet.

Color Correction and DR problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Color Correction and DR problem

    I've come across a strange bug( i think ) that affects distributed rendering.

    When adjusting a background plate material using the color correction map in max2009x64 the rendernodes don't seem to respect the gamma correction setting I specify in the advanced lightness rollout(buckets coming back un gamma corrected). If I return the gamma to 1 and then set the gamma from within the file dialog in the bitmap itself, the rendernodes do respect the gamma-correction. This sees to suggest that the problem lies specifically in the color-correction map rather than any other gamma setting specific to the render nodes. This may be a max bug rather than a vray bug, but its definately a frustrating problem.
    Can anyone replicate this issue? I have a feeling it can be intermittant as I don't always have this problem.
    Patrick Macdonald
    Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/




  • #2
    No replies? This bug is killing me!
    I've restarted my rendernode, replaced all the ini files in the rendernode to match the files on my workstation, removed any color correction, and still, my render node is getting the gamma setting wrong.
    I know I must have messed up a setting somewhere... any suggestions?
    Patrick Macdonald
    Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



    Comment


    • #3
      hmm... think I'll just crawl into a dark hole now...

      For some reason save enabled states in my gamma wasn't set, even through I'm sure I checked it was enabled in the ini files ....

      problem solved.

      doh!

      seems the bug is in my brain.
      Patrick Macdonald
      Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



      Comment


      • #4
        Glad you resolved this

        Best regards,
        Vlado
        I only act like I know everything, Rogers.

        Comment


        • #5
          Out of interest - what line do you add, and to where? I need to set this up on my nodes too!

          Comment


          • #6
            Originally posted by duke2 View Post
            Out of interest - what line do you add, and to where? I need to set this up on my nodes too!
            Isn't this just a check box in the preferences panel called "Load enabled state with max files"? So by leaving it off, the machines allways use whatever they were set up to use?

            Am I missing something here?
            Signing out,
            Christian

            Comment


            • #7
              Originally posted by duke2 View Post
              Out of interest - what line do you add, and to where? I need to set this up on my nodes too!

              Do a search on your node’s hard drive for “max.ini” (make sure you include hidden files and folders in your search). It used to be in the Max directory in program files but since Max2008 it’s hidden in something like:
              C:\Documents and Settings\Supervisor\Local Settings\Application Data\Autodesk\3dsmax\2009 - 64bit\enu

              Then add the LoadEnableState=1 line under [Gamma], mine looks like:
              Code:
              [FONT=Verdana][Gamma][/FONT]
              [FONT=Verdana]LoadEnableState=1[/FONT]
              [FONT=Verdana]CorrectColorPickerState=1[/FONT]
              [FONT=Verdana]CorrectMtlEditorState=1[/FONT]
              [FONT=Verdana]InputGamma=2.200000[/FONT]
              [FONT=Verdana]OutputGamma=1.000000[/FONT]
              [FONT=Verdana]LUTFileName=[/FONT]
              Originally posted by trixian View Post
              Isn't this just a check box in the preferences panel called "Load enabled state with max files"? So by leaving it off, the machines allways use whatever they were set up to use?
              Originally posted by trixian View Post
              Am I missing something here?
              Our render nodes don’t have a Max license so it’s quicker to change the ini file than to use the PLU thingy to export a workstation’s license to every node.

              Dan
              Dan Brew

              Comment


              • #8
                Hmm... think I jumped the gun.

                My max.ini file matches the values you quote above, yet when I set a material gamma (through the file dialog) to "use system gamma", the rendernodes are not applying the correct gamma.

                If I set the gamma (through the image file dialog) to "override" then the node appears to respect the new gamma.... but I don't want to have to manually over-ride every map!

                So, with my gamma settings in the max.ini file being correct, what other reason can there be for the nodes using the wrong gamma? and what steps can I take to avoid this problem?
                Patrick Macdonald
                Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



                Comment


                • #9
                  Sending the file to backburner to render on the node alone causes a "An unexpected error..." on the node.

                  I merged the objects into a clean maxfile and resent it to the rendernode. Same problem.

                  Something is not right...
                  Patrick Macdonald
                  Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



                  Comment


                  • #10
                    Strange. I remerged the file into a clean maxfile and it seems to be behaving again.
                    I wonder what was corrupting the gamma settings...
                    Patrick Macdonald
                    Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



                    Comment


                    • #11
                      I'm having a bad day...
                      Gamma problem is back. Can someone open the file below and see if they have the same issue when rendering on DR? Gamma is wrong for DR buckets.


                      http://www.reformstudios.com/03-reso...ma_corrupt.zip
                      Patrick Macdonald
                      Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



                      Comment


                      • #12
                        Hi, patrick !

                        I'm working exactly on that bug ! Actually working on the new solidrocks 0.75 version, i've exactly the same problem...

                        I've made a tool named "Share Lightcache".. It permits to prerender the lightcache (and only the lightcache) on your main PC, save it, then launching immediatly a slave rendering, with all slaves in "from file" mode with the saved file. With this method, slaves starts immediatly the render, without having to calculate a useless lightcache.

                        But, while testing this tool, some beta testers and myself have encountered the same problem, with different gamm-ized buckets problem..

                        A beta tester told me that it happends when it modify the color mapping (!??)

                        we can discuss around this problem with pleasure until we'll find a way

                        Regards,
                        Jérôme Prévost.
                        SolidRocks, the V-Ray Wizard.
                        http://solidrocks.subburb.com

                        Comment


                        • #13
                          I've not noticed any pattern to the cause of the problem. It's weird that merging the elements into a new file fixes the problem. The question is; is it a bug with vray or with 3dsmax?
                          I've reported it to my reseller and they have raised a support tag with aDesk... it will be interested to hear their take on it. I assume they can dig into a maxfile in more detail to find any corrupted data.

                          Your lightcache tool sounds interesting, although I didn't realise the slaves calculated redundant lightcache data.
                          Patrick Macdonald
                          Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



                          Comment


                          • #14
                            i'm still working on it i tell you informed of any news on it. As SR manages deeply all gamma stuff in max, i'm deep inside

                            about ShareLC tool, yes, many users uses the faster PC as main pc, and slower ones as slaves... with this kindof configuration, slaves takes more time to render the useless lightcache than main pc.. so they starts late the second pass with a lag. SolidRocks just automates the avoinding of this problem, doing that for you
                            Jérôme Prévost.
                            SolidRocks, the V-Ray Wizard.
                            http://solidrocks.subburb.com

                            Comment


                            • #15
                              Originally posted by re:FORM View Post
                              I'm having a bad day...
                              Gamma problem is back. Can someone open the file below and see if they have the same issue when rendering on DR? Gamma is wrong for DR buckets.


                              http://www.reformstudios.com/03-reso...ma_corrupt.zip
                              For this scene you might as well disable the 3ds Max gamma correction altogether; the settings you have chosen don't have any effect on the scene bitmaps or output.

                              Best regards,
                              Vlado
                              I only act like I know everything, Rogers.

                              Comment

                              Working...
                              X