VFB+ v2.1 Released

Based extensively on user feedback from v2.0, I am proud to release the first update to VFB+2!

A few nifty features have been added, such as being able to capture images from Render To Texture, or automatically saving the image from VFB+, allowing you for example, to render sequences locally and have VFB+ color correction or stamping already applied.

The core image processing algorithms have also been greatly optimized, resolving a problem in which a very large render could cause the UI to stutter.

A lot of options have been added to the preferences and more hotkeys have been added, giving each user the fine-grained control needed to suit VFB+ to the intricate inner-workings of their specific pipeline.

Check out the Change Log for a complete list.

A big thanks to all the users who have already made VFB+ a part of their workflow!

Cool stuff, thx! As for workflow improments this is in the same league as Outliner, almost can't work without it anymore So give it a try if you haven't already!

Again, thx for developing this!

Can you explain how it works with Render To Texture? One of the problems with the existing RTT workflow is that the image you see in the frame buffer isn't what gets saved. There's no way to cycle through the rendered elements in the VFB. Does your tool do that?

And does it only do it after it's finished rendering? Because that would limit its use a bit. Since you can't see whether it's rendering correctly while it does it with the VFB it means a potentially lengthy render can be wasted as you can't see it being wrong and stop it early.

@JonadB: Thanks for your support



Unfortunately both of the points you made are not solved by VFB+. They are inherent to how RTT operates and as of yet, I have not found a way to expose the relevant data for implementing those features, though I will continue to try.

Ok, thanks for confirming that it probably won't help.

I hope to make progress in this area in a future update.

When the render is saved, ared the color adjustments also saved?

If you email me specific details I will see if I can get you the info you need.

Very impressive work. Thanks a lot!
I will try to convince the team here.

If you can, that would be very useful. Thanks. And if Kelly can help that would also be great.

Although I don't know why it's never been addressed in max directly. You shouldn't really have to work around it.

Either way is possible, there are user options to control exactly what happens.

@Kelly: Thanks, that's very cool of you! I'll be contacting you shortly.

@Akisey: Thanks a lot

The new release of VFB+ (v2.2) solves both these issues (depending on renderer support).

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.