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

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: 

Comments

Comment viewing options

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

I must admit. I'm quite

I must admit. I'm quite confused. VFB+ does not render anything on its own. It merely copies what was already rendered into a display buffer.

Tell me this... while you are rendering, does everything look fine? VFB+ is not active while the render is in progress, and if that part also exhibits this behaviour, then the culprit is 3dsmax or vray.

Furthermore, what I mean by VFB+ working only on 8 bit is that color correction can only be done in an 8-bit spectrum, but whatever is already rendered should look 100% like it does when VFB+ is disabled.

machoman's picture

It's actually a simple scene

It's actually a simple scene with clear blue sky HDRI, default vraySun, VrayphysicalCamera(f#-5.6, SP-200, ISO-100), multiscattered grass blades(the tallest is about 20cm) on 400cm x 400cm square plane. Then I got the camera close to the edge of the grass plane. Since HDRI can't be uploaded on this site I thought simple scene setting would be helpful.

The attached is another shot from a bit above from the same scene. I did bunch of region renders in order to fix the blown out spots and left those regions due to long rendering time but am having no success, maybe because VFB+ works only on 8 bit? Surprisingly enough, though VFB+ is rendering fine other than those spots. After for awhile I got "Runtime error: dotNEt runtime exception: Parameter is not valid." I tried again and didn't get that error this time.

Anyway, VFB+ is not supposed to work with 32bit HDRI?

AttachmentSize
test_grassblades_no_gamma03.jpg 486.5 KB
rotem's picture

This sounds extremely

This sounds extremely bizzare. I can't think of any situation where this might happen.
Is there a chance you could upload a small simplified test scene exhibiting this behaviour?
I am unable to reproduce it.

machoman's picture

just wanna ask

I was test rendering a close-up grass scene using previous VFB+(I believe V1.3, haven't installed the new one yet). The background image is HDRI with vraySun.

When I region rendered, the region area doesn't get blown out but it does when full rendered. I noticed in your previous comment that VFB+ works only 8bit but why the render region is fine?

What if I region render the whole thing?

BTW I reduced the Render mult value for HDRI so the BG sky color is different.

AttachmentSize
test_region_render.jpg 402.6 KB
test_full_render.jpg 447.21 KB
noel_d3's picture

Great script

"The film strip has now been moved above the VFB window."

Thx U very much Rotem.

Léon

rotem's picture

V1.42 Released!

A small stability release for some urgent bug fixes. See main post for bugs fixed.

rotem's picture

I can recreate it here

I can recreate it here without problem, like you said. It happens because the image in index 1 is deleted to make room for the new image, but it is not removed from the 'b image' slot of the display control. What should happen is that the 'b image' should automatically be reassigned if it gets deleted.

edit: I just realized you might have been talking about the GC error. Never mind then.

Vipera's picture

I don't know what was the

I don't know what was the error with the images deleting I got before. I closed max, deleted script from max folder and installed again. It works, so far. I'll let you know if this happens again. Thanks for the script!

rotem's picture

Thanks!

Very useful bug reports! I'll be sure to fix both of these for next release.

Vipera's picture

Some errors with saved images

Error 1 - Image counter doesn't increase if I have in preferences 'Store rendered images when VFB+ is disabled' unchecked.

Error 2 - Set 'Maximum images to store' to 3. Render 2 images. Toogle A/B. Set B as 1 or 2. Keep rendering few more images. You will get 'Missing Image' error instead of image, because previous file was overwritten.

Comment viewing options

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