Announcement

Collapse
No announcement yet.

FrameBuffer - Composition layer tab

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

  • #16
    Originally posted by kosso_olli View Post
    You mean navigating a high res image inside the new VFB will be slower then before?
    And to add to what the excellent Vlado said, i purely meant that if you process (even panning without any CC) 1 MPx, and you process 100MPx, you can't expect performance to stay constant, it will have to degrade.
    The "proxy" trick is to essentially keep processing 1MPx in a 100MPx image (purely a figure of speech, yes?), by taking into account only what is actually visible, or the canvas, rather than the image, resolution.
    Simple to say, not so simple to properly implement.
    Lele
    Trouble Stirrer in RnD @ Chaos
    ----------------------
    emanuele.lecchi@chaos.com

    Disclaimer:
    The views and opinions expressed here are my own and do not represent those of Chaos Group, unless otherwise stated.

    Comment


    • #17
      This!! Awesome. Would be even better with either vector or paint-able masks! But very cool as it is.

      Comment


      • #18
        OMG! TY Vlado

        Archviz Designer. 2x 2990wx + 4x 1950x + 3x 1800x / Nvidia RTX GPU.
        3dsmax / maya / vray / corona / redshift / unreal / fstorm / arnold

        Comment


        • #19
          Hope we can select by mask (wirecolor, objectid)...in VBF and we will don't need photoshop for simple post production
          P/s: Can we have viggeting in VBF ? Because we can't adjustment it after render with camera viggeting.

          Comment

          Working...
          X