New VFB Skin and functionality

[simtub]

Is it me or the UI in Corona 12 is using a bit more pixel space? Everything seems a bit more spread out especially the top part of the window. Just feels like a lot of wasted screen real estate and those buttons on the top row don't need to be so big (It looks like the UI you would use for basic software like enscape/twinmotion or something...)

[simtub]

Upon further investigation, yes the new VFB is using twice as many vertical pixels on the top horizontal menu bar and the RHS menu is super spaced out...

Not sure why this change is necessary, we need all the screen space we can get - viewing renders, changing settings etc and especially in interactive rendering mode (the interactive view especially since a full 100% preview is limited by the pixel height of our monitors without zoom) We also have multiple menus open in max at the same time during production.

For now I've gone into Corona system settings and reverted back to the last VFB instead of VFB 2.0

[dj_buckley]

It looks like the UI you would use for basic software like enscape/twinmotion or something...

Haha the first thing I thought was "this feels like Sketchup"

[LorenzoS]

Hi,
is planned to have a real zoom-pan directly on VFB?

[maru]

I found another "bug" in VFB2
If you start the IR and zoom in on the image in the framebuffer using the mouse wheel, then when you make changes to the scene, the zoom is automatically reset to 100%. This is a very undesirable behavior, I sometimes need to correct small details pixel by pixel, and the size of the monitor does not allow me to use 100% zoom for comfortable viewing.
Please return the previous behavior of this function if possible.

We will look into this. Thanks for reporting.

Hi,
is planned to have a real zoom-pan directly on VFB?

Yes, it is planned. (Report ID=CMAX-1078)

[arqrenderz]

Totally agree with the bad layout of the Ui, too much wasted space..

[Tom]

+1

[marchik]

Totally agree with the bad layout of the Ui, too much wasted space..

I wish it to be possible to dock a VFB2 window, as it can now be done with the Material Editor after max 2024, then we would get rid of the need to run IR in the viewport via "extended viewports"

[Avi]

I found another "bug" in VFB2
If you start the IR and zoom in on the image in the framebuffer using the mouse wheel, then when you make changes to the scene, the zoom is automatically reset to 100%. This is a very undesirable behavior, I sometimes need to correct small details pixel by pixel, and the size of the monitor does not allow me to use 100% zoom for comfortable viewing.
Please return the previous behavior of this function if possible.

This is now reported in our system.

(Report ID=CMAX-1159)

[danduya]

+ 1 For the wasted space of the VFB, legacy was better.

Also, you can't scroll between passes with the mouse scroll wheel anymore.

[Aram Avetisyan]

+ 1 For the wasted space of the VFB, legacy was better.

Also, you can't scroll between passes with the mouse scroll wheel anymore.

Hi,

You cannot scroll render elements, until you click/open it, and then it works.
This can actually be the more desired behavior, as in case of scrolling right-away you may change it accidentally.

[Neil Cross]

Hi. Would it be possible to stretch the post sliders? I find them quite narrow. See attached.

[kino_unico]

In general, I don't like everything to look bigger and disproportionate.
A function that I personally dislike is that the zoom can only be 25% 50% 100% of the render. I would like to have the option of having the render fit my window as happens with vray, where by pressing the "F" key it fits my window.

I really prefer the other virtualframebuffer much more,
I thought that the update was going to be that the multilight could be activated with a box and that the lights would be updated automatically or new functionalities. I really don't see the point in this change, it's a step backwards

[Frood]

now, apart from the noise of the fans, it is difficult to understand whether the interactive is running. (Play/stop indicators are made in b&w gamma, which does not have a very good effect on readability)

Psssst...

throw this into any scripts\startup directory (or execute manually). If you want to play around, type "ccri.help()" in the maxscript listener ;)


Good Luck

[marchik]

now, apart from the noise of the fans, it is difficult to understand whether the interactive is running. (Play/stop indicators are made in b&w gamma, which does not have a very good effect on readability)

Psssst...

throw this into any scripts\startup directory (or execute manually). If you want to play around, type "ccri.help()" in the maxscript listener ;)


Good Luck

:D works just fine, big thanks!