VFB+ : A Feature-rich Extension to the 3dsmax Frame Buffer

Submitted by rotem on Fri, 2011-08-19 08:15
63 votes
Version: 
2.81
Date Updated: 
07/14/2017

VFB+ v2.81 is now completely free!

Click for Change Log

 Introducing VFB+ v2.81, the advanced virtual frame buffer for Autodesk 3dsmax.

VFB+ works with any renderer which uses the native 3dsmax frame buffer, such as Scanline, Mental Ray, Final Render, IRay, VRay, Corona (when not using the renderer's custom VFB).

The frame buffer has been designed and heavily tested to fit smoothly into any production pipeline, and to streamline the rendering workflow for anyone who renders in 3dsmax.

Version 2.8 is the most powerful and feature packed release yet!

A partial list of features:

  • 32-bit per channel color correction.
  • Various correction controls including exposure, gamma, multi-channel curves, vignette, chromatic aberration, bloom, glare, blur/sharpen, speckle reduction, noise reduction, etc.
  • Depth of Field based on Z-Depth.
  • VFB+ is active while rendering, including tweaking of color correction and stamping.
  • Captures Render Elements, G-Buffer channels, and RTT elements as well as the main pass.
  • Composition guides help you tweak your image.
  • Pixel Aspect Ratio correction display.
  • 4 different A|B comparison modes.
  • Display modes for all channels.
  • Support for 3D color LUTs.
  • Realtime RGB Histogram.
  • Rich WYSIWYG stamping system with virtually any imaginable variable including arbitrary MAXScript expressions.
  • Fully documented.
  • Customizable interoperability options.
  • MAXScript interface provides access to almost all features.

See the link for download and complete details.

Version Requirement: 
3dsmax 2009-2018
Video URL: 
Links
Homepage URL: 
http://www.monotoneminimal.com
Download URL: 
http://www.monotoneminimal.com/vfb

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
moulder6's picture
Submitted by moulder6 on Tue, 2011-11-01 17:51.

"Frame B changes to (current

"Frame B changes to (current frame)-1 frame."

I wouldn't call that a bug. It's actually expected and needed behavior. When u tweak the render u normally want to compare the last changes to the previous situation in a progressive manner, not to something u rendered a month ago...

In the best case it could be optional as i mentioned back when this was discussed:

- just as it is now, which on my side is the desired behavior;
- fixed "b" as Vipera suggests.

@ Vipera: "how about if frame B is image 1 (the earliest image) it will simply discard image 2 instead?"

Set the limit to 3 and VFB+ to discard the last rendered image. Then set "B" to image 1. Now, when u render, u have A-2, B-1... Next time u render u have A-3, B-1... Next time u render 2 is discarded, 3 is moved to 2, and u have the new render as 3 again, displayed in "A". U have "fixed" "B" that never gets discarded, and A that's the last render.

Vipera's picture
Submitted by Vipera on Tue, 2011-11-01 15:30.

Frame B

"how about if frame B is image 1 (the earliest image) it will simply discard image 2 instead?"
I'm not sure what you mean. The easiest way to lock frame B will be in coping current image in frame B as a new file, which we prevent from deleting in any case until we unlock frame B. We can even keep this frame to new the max session.
If we unlock frame B, then we show (current image)-1 by default or current image if have rendered only one image.

rotem's picture
Submitted by rotem on Tue, 2011-11-01 13:31.

I see... how about if frame B

I see... how about if frame B is image 1 (the earliest image) it will simply discard image 2 instead?

Vipera's picture
Submitted by Vipera on Tue, 2011-11-01 09:58.

Need frame B to be sticked.

As I said, I need a checkbox to have frame B sticked. So, frame B will stay in this place even if I reach maximum stored images. I set maximum as 3 just for example. Usually I use 20-30 images to store but this maximum I can also reach very fast and I will lose frame B in this case.
Solution for sticked frame B could be a situation when we copy(or rename, what is better) frame B as a new file with the different name. In this case this file will not be overwritten or deleted when we reach maximum stored images.

rotem's picture
Submitted by rotem on Mon, 2011-10-31 13:18.

Thanks for the detailed

Thanks for the detailed repros.
What your are describing is actually two different situations:

Repro 1: Image B is discarded due to the 3 image limit, this is the intended behavior. You have an option to discard the latest image, instead of the earliest, if that helps. Do you have a suggestion for a better solution?

Repro 2: This is a bug, and will be fixed.

Thanks again.

Vipera's picture
Submitted by Vipera on Mon, 2011-10-31 09:55.

Repro 2

Repro 2: Set maximum images to store to 3. Render 3 images. Toggle A/B ON and set B frame to 1. Toggle A/B OFF and again ON. Frame B changes to (current frame)-1 frame.

Vipera's picture
Submitted by Vipera on Mon, 2011-10-31 09:54.

Repro 1

Repro 1: Set maximum images to store to 3. Render 3 images. Toggle A/B ON and set B frame to 1. Render one more image. Frame B will go away.

rotem's picture
Submitted by rotem on Sat, 2011-10-29 03:03.

glad to hear :)

glad to hear :)

rotem's picture
Submitted by rotem on Sat, 2011-10-29 03:03.

That doesn't happen for me,

That doesn't happen for me, frame B does not change on its own... can you give reproduction steps?

mustafa mamdouh's picture
Submitted by mustafa mamdouh on Fri, 2011-10-28 21:03.

Working Great!!

Thank you rotem =)

thanks to scriptspot community

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.