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

Version: 
2.5
Date Updated: 
10/20/2014

VFB+ 2.5 Released

Click for Change Log

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

VFB+ works with any renderer which uses the 3dsmax frame buffer, such as Scanline, Mental Ray, Final Render, IRay, VRay (when not using the VRay 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.5 is faster, supports any bit depth, and packs a multitude of new features. It works with any renderer, provided it is using the 3dsmax frame buffer (e.g. - V-Ray render will work when not using the V-Ray VFB).

A partial list of features:

  • Support for 16-bit and 32-bit per channel (HDR) images and color correction.
  • Various correction controls including exposure, gamma, multi-channel curves, vignette, chromatic aberration, bloom, blur/sharpen, speckle reduction, noise reduction, etc.
  • 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 graphics stamping system with virtually any imaginable variable including arbitrary MAXScript expressions.
  • Fully documented.
  • Customizable interoperability options.
  • MAXScript interface provides access to almost all features.

A 30-day fully functional trial version is available for download.

See the link for complete details.

Version Requirement: 
3dsmax 2009-2015
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

Confirmed & will be fixed.

Thanks, Not sure how that one slipped by for so long.

dub73's picture

delte all images in frame buffer

Hi Rotem, when I delete the complete history in the vfb, I don't get an image when I hit render again? At first I have to do a screenshot, then I get an image again and works fine

max 2012

thx

robobear510's picture

sort of works, but not really

octane has it's own octane preview window, which can be ported to max frame buffer, but it doesn't defult to vfb, like standard render does..
- and also it can be rendered via standard render button *which I almost never use..

rotem's picture

Hi It should work with any

Hi
It should work with any renderer which uses the 3dsmax frame buffer. Does Octane use its own frame buffer?

robobear510's picture

can it work with Octane render?

- it doesn't really work with octane render.. there are things here that would be much appreciated in octane community I would guess - I like what it does, but I don't use vray or standard render at all

kanenas's picture

Thank you Rotem. MaxScript

Thank you Rotem.

MaxScript returns a single line:
"G:\Program Files\Autodesk\3ds Max 2014\scripts\startup"
No subfolders in it.

I'll have a look later with Process Monitor and try to figure out what folders it's getting mixed up with.
I'll post back if I discover the reason.

Thanks for your time.

rotem's picture

Path too long

Hi Kanenas

According to the error code, VFB+ is trying to determine is a previous version of VFB+ is installed (v1.52 and lower, script based), in order to remove it before initializing v2.XX.

The exact method that is failing, is Directory.GetFiles ( http://msdn.microsoft.com/en-us/library/ms143316(v=vs.110).aspx ). The error is an OS error, and has nothing to do with VFB+ or 3dsmax. As far as I can tell, it also has nothing to do with the PATH environment variable.
VFB+ is basically searching for the file VFBPlus.ms in the path returned by calling "getDir #startupScripts" from MAXScript, and all it's subdirectories.
You may have a very big hierarchy of subfolders inside that directory, resulting in a very long path.

In any case, VFB+ should handle this gracefully instead of raising an exception, and I will make sure it does so in future releases, but taking a look at that folder may fix problems you're having with other tools.

Regards,
Rotem

kanenas's picture

Fails to initialize -- path too long

I just tried 2.41 with 3ds Max 2014 on Windows 7.
I get a 'failed to initialize' MaxScript error and a popup that refers to path length being too long.

Failed to initialize VFB+. Errocode: 3010
Error:
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

I doubt it came across such a long file name/path in the filesystem.
But I suspect the problem is that the system's PATH is near its limit.
Not much I can do about it (I keep juggling it to get various dev tools to load up, though they are the ones that should know better how to set themselves up).

Assuming the long PATH is the reason, why is it so?
Why does the plugin need to modify/add to the path since it's already in Max's default folder?

Sorry but I get apprehensive when I see this. I got many systems messed up because some program tried to add to a full path, failed, and cleaned the PATH in the process. VFB+ is more careful and doesn't do that but once burned...

Thanks.

rotem's picture

v2.41

I've updated the release to v2.41, fixing the bugs that Shawn reported. Thanks again!

rotem's picture

Hi Shawn You're absolutely

Hi Shawn

You're absolutely right on both accounts! Sorry, I'll put out a fix as soon as possible. Thanks!

Comment viewing options

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