New Framebuffer Issues

[ali_cgi]

Is anyone not feeling the new framebuffer?

I find it clunky and annoying personally, I don't need compositing in front of me whilst doing CG and this framebuffer kind of forces it onto you.
In my opinion, it distracts artists "including myself" from the job at hand.
Yes, you can hide stuff but it's just not as nice as simple exposure control and soft clip. Nothing else obscuring the view.

Also, where are the scrollbars? This is incredibly useful for panning when using remote desktop to see a renders progression.

I tried the environment variable to re-activate the superior old framebuffer, but have noticed some issues, crashes etc, I'm also not keen on staying in the past. I just don't like where the development has gone.

Over-engineered comes to mind, functionally frustrating.

Why is "W" mapped to a shortcut for wipe ??? this is the move tool in Maya "BAD DECISION" sorry to shout but my fingers constantly hover over "w" this is massively frustrating.

[SonyBoy]

I'm not a huge fan of the new VFB either. It doesn't really seem to have improved anything, TBH, and has only hidden previous features and complicated everything else. I'm in agreement that this window should have only some basic tools that are render-centric, and not try to be a whole compositing package in and of itself which is where it seems to be going.

[yolov]

Hey, regarding hotkeys - we're adding an option to edit the hotkeys that should be out soon.
If you have a repro case for any issues/crashes - please report them, so we can fix them.

[BenWall]

- Hotkeys will be a must have, for now switching color channels is a bit tedious.
- Lens effect should not be activated by default, for now we have to deactivate it in VFB after every render
- I also sometimes have a strange bug with the RGB color pass, which turns completly black in VFB once a render is finished (saving the image still works and all aov are still visible except for RGB color).

Appart from that, lightmix is so powerfull and time saving for look dev that I would'nt go back to the older VFB version.

[yolov]

[QUOTE=BenWall;n1103208]- Hotkeys will be a must have, for now switching color channels is a bit tedious.
--> The next update will also have hotkeys for switching color channels.

- Lens effect should not be activated by default, for now we have to deactivate it in VFB after every render
--> That's odd. Lens effects are not ON by default. The lens effects layer is always added and 'visible', but they are not enabled by default. Can you double-check?

- I also sometimes have a strange bug with the RGB color pass, which turns completly black in VFB once a render is finished (saving the image still works and all aov are still visible except for RGB color).

--> If you can get us some repro steps, we'll be able to look at this.

Appart from that, lightmix is so powerfull and time saving for look dev that I would'nt go back to the older VFB version.

--> Nice to hear that!

[BenWall]

yolov : I had the disappearing RGB on scenes with elements rendered as matte alpha -1 using a vray object property.
I didn't save the scene and didn't try to reproduce the bug, so I don't have any exemple to share.

I'll double check my setup for lens effect as on per default, but from the doc page it seems the only place to deactivate it is in the VFB, right?

And yeah, light mix is absolutely awesome! It woule be great to be able to automatically separate different LPE in them (direct / indirect difffuse, direct /indirect spec etc) like on the light choser render elements.

[yolov]

the doc page it seems the only place to deactivate it is in the VFB, right?

I believe this has always been the case - including in previous versions of V-Ray.

It woule be great to be able to automatically separate different LPE in them (direct / indirect difffuse, direct /indirect spec etc) like on the light choser render elements.

This would increase memory usage and render times if it's built-in, especially if you rarely use it. Light Mix is equivalent to using the FULL light select mode. Using the direct/indirect types for now requires manually setting up the light selects. But if you go for a manual setup, then you can use the Composite mode in VFB2.

[seandunderdale]

- I also sometimes have a strange bug with the RGB color pass, which turns completly black in VFB once a render is finished (saving the image still works and all aov are still visible except for RGB color).

I used to get this a lot in Vray next when rendering with denoiser and having a backplate loaded in the framebuffer. The render looked fine until the denoiser ran and everything crunched and went black.

I have only been using Vray 5 for a few weeks but so far Im loving it. I love being able to layer and order framebuffer tonemap controls and I find I can get a decent minimal grade out of Vray and to a client without having to take the image into post. This helps the client visualize the intended final look better, and saves me time. It also bakes into the renders which is great and gets me half way there for my final high res image.

I also love the new drop down for selecting other files in the same folder, which makes trying LUTs and swapping backplates much faster. Great addition!

[^Lele^]

In case a composite was selected as source (or a b2b AoV was added) then the VFB will keep defaulting to composite view, which may result in black render progress, depending on what is going on.
Ensure you're viewing the RGB source: if it goes black with that selected, we'd be keen to reproduce it!