Image Output

V-Ray V-Ray GPU Issues
1

Hi,

i recently started test out vray rt GPU as a production renderer.

Some how i am not able to save images through vray frame buffer.

Is this normal behaviour that i can only save images through common max output or

am I getting something wrong here ?

My problem is that i want to save images as full 32bit exr through Vray raw image output.

Any help would be great

Best regards

Björn

2

anyone ? :face_with_spiral_eyes:

3

Hello there,

Thank you very much for your feedback.
It looks like a bug - saving with native Max Frame Buffer works correctly but with VFB something is wrong - I’ll report it immediately.
As a workaround please use MaxFB for now - I’ll inform you as soon as we got this fixed.

Edit: With more in depth test we found out that this is working correctly - the problem is that when you save the image from VFB , Vray continue to write in that image until RT is running - in other words the image is locked until RT is working. Once you close RT session - you will be able to open the image, and you will have all refinement from RT even if the image is saved long before RT is closed.

4

Well there are no images saved in my Folder even if i render only a single frame, and since i am rendering an animation of around 200 frames RT doesnt stop working and will never save out the image, maybe the last one.
Also my RT settings are set to 48 max paths per pixel for test purpose to prevent it from endless refining.

I am kind of stuck here !

As i said it only autosaves files throug max output. Neither Vray raw image file or Split render channels is saved out.

5

Hello again,

It works from VFB window - but it seams that it doesn’t work from VFB rollout.
I already made a note about in in our system - and I’ll inform you as soon as we have it fixed.

Thank you very much for your feedback.

6

Any news on solving that output problem ? Last nightly seems to still to be broken in that case.

Best regards

Björn

7

Unfortunately not yet.
We’ll post here when we have this fixed.

8

Hello Björn Radler

We just want to inform you that this issue has been fixed in version 3.x
Thank you very much for your collaboration.

9

Will be testing as soon as i have updated to 3.0… hopefully this month

thx for the headup so far

regards Björn