VFB+ : A Feature-rich Extension to the 3dsmax Frame Buffer
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.
Comments
Save the render time stamp with the file feature
It would be nice to have a checkbox to save the render time stamp with image file when click on Save Image button.
Hey guys, If u, just like me,
Hey guys,
If u, just like me, think that this is a great alternative to the old and limited max VFB, and that Rotem, here is doing a great work, feel free to give ur vote for a full integration of VFB+ straight inside max:
http://autodesk.uservoice.com/forums/80695-publicgeneralfeaturerequests/...
Thank you
Glad to hear :)
I am not sure but maybe more
This sounds like it would be pretty confusing to the user, don't you think? It's built so 'A' is the master image that is currently in view.
This happens for two different reasons:
1) when clearing the history or discarding all the images: there are no more images to display so the toolbar closes... do you think it would be better to keep the toolbar visible, and show a black screen in the image panel?
2) when rendering: the toolbar hides itself before rendering because it is 'locked' during rendering so it would be useless, and if you wanted to use the original vfb's 'alpha' button you wouldn't be able to.
I love it man. Great job
I love it man. Great job
You are so fast
I am not sure but maybe more logical is to have in A/B mode the first image the older one and second the new one by default.
In situation when I see only one render and left click on the image, would it be possible to auto set the A/B mode and instantly can move the line?
If I clear images history or start render, the bar with icons is hiding themselves (after render goes back), is this correct?
Sorry
Thank you, I've updated the version to 1.31 to fix this bug.
Bug in version 1.3
There is a bug in version 1.3. When I click Save Image button I have error message "-- Unable to convert: undefined to type: FileName" and script stops on deleteFile tempBMPPathF.
fn saveImage =
(
local thePath = selectSaveBitMap caption:"Save Image"
if thePath!=undefined do
(
.....
deleteFile tempBMPPathF
)
),
I have changed temp folder for saved images to c:\Temp and I try to save to .JPG and .TGA. I do not have any problems with version 1.2.
Thanks, I will add your
Thanks, I will add your suggestion to the feature request list.
Great work,I like It.Thanks
Great work,I like It.Thanks
a possibility to compare twice Rendered (current render and last render) as a whole,or compare forth Rendered as a whole,
I think It will be very useful.