New VFB Skin and functionality

[magmatik]

We can't elaborate yet, sorry. What I can say is there are no plans for cryptomatte masks inside the VFB, certainly not for 12 anyway. Beyond that, we have a long list, and we are aiming to see how far (very far, not far at all?)  we get through it, so we don't want to over or under state things by giving a set of plans for now. The main focus is on the UI rework, streamlining, better performance, and then we'll see what features make it in. This will be a "watch the daily builds" scenario by and large. Hope this helps!

Some good things to come!
Can't wait to know more!

[shortcirkuit]

glad im not the only one - ive even spent thousands on updated hardware thinking it would fix the problem.  Its literally been like this since i started using max over 10 years ago.  In fact, i think its gotten a little worse.
@CoronaDevs - i think this needs to be looked at for sure.

For me, this biggest time waster over the years is the UI (material editor) - i know its not a corona thing (or it could have an impact?) - however the material editor, becomes slow and sluggish, mainly in heavier scenes (not really that heavy, fairly detailed interior scenes.  2-3 seconds for things to open.... and i do have the most of the latest hardware/software.... again, not sure if this is solely a autodesk thing or a combination between autodesk and corona materials, however its just so sloowwww and it kills my patience... it sometimes feels like im using a intel pentium from the early 2000's..... its 2024, UI, all of them, should be zipppy and we shouldnt be held back by such nuances.

I get that too: the material editor becomes really so slow sometimes, especially when IPR is running, up to the point that I have to stop the IPR, only then I'm able to tweak my materials in the SME, and only then I start the IPR again to see the results. This isn't how things should be: ideally I wouldn't have to stop the IPR in order to be able to tweak the materials, but if I don't the SME UI is just sooooo slow, it's unbearable.

[pokoy]

If I had a wish, for me it's how the denoiser workflow is implemented:
1. Let us denoise *during* a final render, with whatever the denoiser is set to. I'd love to see if the noise level is good enough while i'm rendering. Sometimes I'll set way too many passes and having a way to preview the denoiser without stopping/cancelling the render would be great.
2. Currently, a denoised render will save to the history only if it was a final render, IR will save to history without the denoiser... This is inconsistent and makes it impossible to compare IR vs final renders since you can't save/view the denoised version from IR.
3. Denoiser checkbox in the VFB is inconsistent - for final rendering it will work only after a render is stopped/finished. For IR it can't be disabled without re-rendering (and has no function there), plus, it has to be disabled in a different place. It just doesn't do what it implies the way it's designed now.

For me it's the small things and consistency between final/IR rendering is not where it should/could be wrt to denoising.

[michaltimko]

I always set IR it to force PT and set some pass limit like 5-7 (depends on the scne). That way you are lag free when it comes to mat editor or max ui. Another option is to use IR in the viewport. Not sure if its just for me but its way more snappy than having it in separate VFB window.

glad im not the only one - ive even spent thousands on updated hardware thinking it would fix the problem.  Its literally been like this since i started using max over 10 years ago.  In fact, i think its gotten a little worse.
@CoronaDevs - i think this needs to be looked at for sure.

For me, this biggest time waster over the years is the UI (material editor) - i know its not a corona thing (or it could have an impact?) - however the material editor, becomes slow and sluggish, mainly in heavier scenes (not really that heavy, fairly detailed interior scenes.  2-3 seconds for things to open.... and i do have the most of the latest hardware/software.... again, not sure if this is solely a autodesk thing or a combination between autodesk and corona materials, however its just so sloowwww and it kills my patience... it sometimes feels like im using a intel pentium from the early 2000's..... its 2024, UI, all of them, should be zipppy and we shouldnt be held back by such nuances.

I get that too: the material editor becomes really so slow sometimes, especially when IPR is running, up to the point that I have to stop the IPR, only then I'm able to tweak my materials in the SME, and only then I start the IPR again to see the results. This isn't how things should be: ideally I wouldn't have to stop the IPR in order to be able to tweak the materials, but if I don't the SME UI is just sooooo slow, it's unbearable.

[Tom]

Thanks for the IR advice @michaltimko, I never paid attention to these settings, but indeed it makes things more responsive.

[zaar]

Can we put suggestions in this thread?

I'm here to raise a hand for custom background or reference image overlay, that maybe works like A/B history so you can compare your render to any image of your choice. Color management here is of course priority otherwise the feature is completely useless.

I want to A/B my current render to either my own renders of the same scene/product or reference images.

[shortcirkuit]

could we PLEASE add a function to FLIP the image horizontally - just to refresh the eyes to look at the render from a new perspective.

[lupaz]

could we PLEASE add a function to FLIP the image horizontally - just to refresh the eyes to look at the render from a new perspective.

+1

[lupaz]

And composition lines please

[Tom]

could we PLEASE add a function to FLIP the image horizontally - just to refresh the eyes to look at the render from a new perspective.

+1

[brr]

It would also be nice to have an option to change the VFB background color in Corona Renderer.
This was discussed previously here: https://forum.corona-renderer.com/index.php?topic=28172.0

It really helps a lot when you need to adjust the overall brightness level of the rendering, because with the current linear RGB 4/4/4 background color, it is easy to miss it.

[maru]

They are logged.
Flip/rotate the VFB content: (Report ID=CMAX-862)
Change VFB background color: (Report ID=CMAX-861)

[Place]

Am I the only one who would like to draw hand free the region zone?
Is it possible to implement?

Thank you,
Manuel

[lupaz]

Am I the only one who would like to draw hand free the region zone?
Is it possible to implement?

Thank you,
Manuel

Since you're bringing this up, it would be great to be able to mark the region in either the viewport or the VFB, not just the VFB.

But yes, a freehand region selection wouldn't be bad if not hard to implement.

[dzintas]

Since you're bringing this up, it would be great to be able to mark the region in either the viewport or the VFB, not just the VFB.

You can already define render region in viewport, or native one from max aren't sufficient enough?