VFB+ : A Feature-rich Extension to the 3dsmax Frame Buffer
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
Comments
Thank you
Thank you for the fast implementation. Works great.
1.52 Reuploaded
There was a typo in the 1.52 MZP from yesterday. This has been fixed now. Thanks to Dom for reporting it.
WOW!
It works!
Thank you very much!!
v1.52 Released
Another small update, details at the top.
Great!
Thank you!
Ok I've managed to recreate
Ok I've managed to recreate your error and explain the situation:
Usually max runs vfbplus.ms as a startup script, and vfbplus.ms loads vfbplus.dll manually.
Because you put it as a plugin.ini path, max is trying to load not only vfbplus.ms, but vfbplus.dll by itself at startup, which triggers the security exception.
I'll update it to a new version sometime this week, I will simply refactor vfbplus.dll to vfbplus.dat or something like that to avoid this problem.
Yes, I tried running the
Yes, I tried running the files from a network drive in max2012 and had no problem.
Let's try this experiment:
After you load max, if you do Maxscript -> Run Script -> run vfbplus.ms from network path manually... does it work?
Do you put your files on network drive?
hmm, I cannot find "unlock" button on dll file properties.
So, all machines get this error message when I put files on network drive(actually this is my file server) and write this path in plugin.ini.
It was the same result, even if I change a server to put files.
I can't reproduce this
I can't reproduce this behaviour in max 2012. Try this:
When you go to the file properties of the vfbplus.dll - do you have a little button 'unlock' at the bottom?
network drive
I get exception error on max2012, when I put vfbplus.* files on network drive. This problem didn't happen on max2011.
I want to share this script(and version) all machines in my office.
Can you avoid this problem?