Vrscenes rendered with V-Ray 5 Standalone will only output files without a preview buffer

[JD3D_CGI]

So is this a deal breaker?

What is "the preview buffer" - do you mean the VFB 2? So does that mean we can;t render jobs using the Vray raw image file option that you want us to do normally?

Could someone please explain what exactly is happening and what steps to take?

Also, can you please make the help files clearer.

People dont use the term "preview buffer" - they say the "vray frame buffer"

The help files says:

For 3ds Max versions above 2018, when you export and render with V-Ray Frame Buffer 2 enabled, the scene analyzer prints the following warning: "Vrscenes rendered with V-Ray 5 Standalone will only output files without a preview buffer".

When you click on the Preview button in the Cloud submitter, the same message is printed, along with a pop up: "Interactive preview is not supported yet, please wait until the end of rendering". Then an auto-saved preview file opens automatically when the rendering is finished.

So does this mean the render wont work, or the previewing wont work?

Because right now all my renders are failing and I don't know if it's because of an exiting problem, or because of that.

The help file really isn't very clear.

[matanov]

The initial V-Ray 5 doesn't have VFB2 in V-Ray Standalone which is used for rendering the preview for Chaos Cloud.

So what is actually happening - when you click on "Preview", the same thing is executed as before - exporting to vrscene and launching a render with V-Ray Standalone, but since there is no VFB2 there, for the sake of keeping all color corrections you did in Max we are not showing the image preview of the rendering process, so they can be saved in the image that was rendered in the background. After that image is ready it will be opened with your default image viewer.

TLDR - the cloud preview function is working as before, you just can't see the image while rendering. The result will be the same.

We already have VFB2 functional in V-Ray Standalone in the nightly builds so you'll see it in the next Update or sooner in the stable nightlies. Then all the above will go away