Announcement

Collapse
No announcement yet.

DR - Recall Bucket Names

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

  • DR - Recall Bucket Names

    It would be good to have the option to recall the buckets' names after a frame has finished in the VFB.

    Recently, I walked away from a render only to find a couple buckets 'lighter' than the others. I'd like to know if it was one computer in particular that is having issues instead of having to dig through each system and troubleshoot.
    LunarStudio Architectural Renderings
    HDRSource HDR & sIBL Libraries
    Lunarlog - LunarStudio and HDRSource Blog

  • #2
    I was just about to post this same wish. as i'm looking at a render with 2 buckets clearly darker than the rest.

    I was thinking it might be a good thing to have it in the form of a g-buffer layer, an option to save and write teh bucket names into this layer for later overlay for debugging purposes.
    Dave Buchhofer. // Vsaiwrk

    Comment


    • #3
      Looking at the vraylogs for the various machines i used in the DR you can tell which machines had problems. (In my case)

      Log excerpt of a problem machine.. 2 out of the 6 machines have this in the log.

      [2006/Nov/21|10:04:04] Calling prePassDone() on irradiance maps
      [2006/Nov/21|10:04:04] Image prepass completed.
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 0
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 1
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 2
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 3
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 4
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 5
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 6
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 7
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 8
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 9
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 10
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 11
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 12
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 13
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 14
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 15
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 16
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 17
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 18
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 19
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 20
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 21
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 22
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 23
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 24
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 25
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 26
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 27
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 28
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 29
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 30
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 31
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 32
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 33
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 34
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 35
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 36
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 37
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 38
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 39
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 40
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 41
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 42
      [2006/Nov/21|10:04:04] warning: Error receiving irradiance map 43
      [2006/Nov/21|10:04:04] Rendering image.
      [2006/Nov/21|10:04:04] Setting up 2 thread(s)
      [2006/Nov/21|10:04:04] Threads completed

      ! it continues to render even though it wasn't able to recieve the irradiance map from the host machine.. why would that possibly be a good idea? Shouldn't it sleep for a few seconds, and try sending again?
      Dave Buchhofer. // Vsaiwrk

      Comment


      • #4
        Yeah - doesn't seem too hard to implement since it's already on screen for a brief period of time - but then again, what the hell do I know. I know nothing - that much I do know. I guess the bucket names are really controlled by Max itself and it is just 'enabled' in Vray now. I hope the can work some miracles here.

        As for that problem Dave, I've had this with other GI methods and mentioned this before. If you set up a fairly simple scene with camera animation then try to render it frame by frame over DR, it can do the same thing. The buckets can skip before it's loaded.

        My latest issue turned out to be a referencing a different material with duplicate name - so that wouldn't have been much help in this particular situation.
        LunarStudio Architectural Renderings
        HDRSource HDR & sIBL Libraries
        Lunarlog - LunarStudio and HDRSource Blog

        Comment


        • #5
          Wow Dave - that was your 666th post.
          LunarStudio Architectural Renderings
          HDRSource HDR & sIBL Libraries
          Lunarlog - LunarStudio and HDRSource Blog

          Comment


          • #6
            i actually had to ditch DR in favor of 'getting the job done' sadly. it may have been a problem loading a bitmap over the network, but there isn't any real way to find out whats going on. the fact that it will just continue to render if it fails to load an asset is probably good, but there needs to be some sort of log of it so as to make these '4 buckets are brighter' thing less of an issue.

            it was also btw, having the same problem without posting anything to the log most of the time.

            and poof. 667.
            Dave Buchhofer. // Vsaiwrk

            Comment


            • #7
              My issue was duplicate material names so the buckets were completely random - it would be nice to have a check/script that could detect if they're referencing same names with either different file sizes or dates modified over the network.

              Chances are if you were experiencing solid renders in the past on the same setup, then it's a bitmaps conflict.
              LunarStudio Architectural Renderings
              HDRSource HDR & sIBL Libraries
              Lunarlog - LunarStudio and HDRSource Blog

              Comment


              • #8
                I just wanted to re-post this as its coming up again.
                Dave Buchhofer. // Vsaiwrk

                Comment


                • #9


                  Possible?

                  And yea, i know what the problem was here, my license server crashed after the job had started.. but its just a case of 'Which slave couldn't get a license?!
                  Last edited by dbuchhofer; 17-06-2009, 01:41 PM.
                  Dave Buchhofer. // Vsaiwrk

                  Comment

                  Working...
                  X