When you render in Max with Vray-Camera, everything is fine.
When you submit the scene to Backburner, the vrayCamera renders as zoomed in or out. And there’s no way I can match them.
If I use the normal Max Camera, it renders fine both in Max and Backburner.
But the Max Camera is useless with Vray as there are no exposure controls.
This is definitely a bug.
In the past 3 weeks I have discovered several bugs… so if I am to buy Vray(i’m on the trial version now), do i have to buy it with those bugs ? (rethorical question)
Thank you.
Cool.
For now I have worked it around with Batch rendering because I have several cameras in one scene(out of several other scenes), but when you have multiple scenes, Backburner is needed.
Looking forward to see it fixed in the next build.
Thanks.
I have also noticed that if I render through Batch renderer(not Backburner) and I try to save the renders as .hdr, it saves the image as black.
If I save the image manually, using the VFB save button, it saves ok, but if it’s saved through Batch rendering, it saves black.
The OpenEXR is fine.
The .hdr is not.
I haven’t tried other file formats. I think you can replicate this with a very simple scene - just try to render and save with Batch rendering.
I can replicate this issue only if I use the native 3DS max save option.
Saving from Render settings > V-Ray frame buffer > Separate render channels to HDR file works fine in my test. Could you use this as a workaround?
When you save to HDR, 3ds Max puts up a dialog box asking if you want to use non-clamped (realpixel) color channel, or use standard RGB channel. Which option did you select? The first one will not work.
The RT engine also has an option to generate a floating-point image buffer, which you might need to enable.
@Vlado:
The floating point buffer option(“Use 32 bit frame buffer”?) for the frame buffer is checked.
For HDR, i use the non-clamped (realpixel) color channel because I need the whole 32 bit range of the image to alter it in compositing. The standard RGB channel is just an 8bit image if i’m not mistaken.
@Tashko:
If I use the save “separate render channels” then all my batched renders will have the same path that was set in “separate render channels”.
Saving from Render settings > V-Ray frame buffer > Separate render channels to HDR file works fine, indeed but then I can’t have different multiple saving paths as Batch rendering allows you to so that’s why i need to save through Batch rendering(which uses the standard max saving option).
I could create a different “Scene State” for each of my renders so in that case, each camera will have it’s own scene state with its own render settings(including “Separate render channels”) and then I can assign the corresponding render state in Batch rendering, but this is not feasible at all.
I was rendering today with Batch rendering as a workaround for Backburner and I have noticed the cropping(or zoom factor) occurs with Batch rendering as well this time. I had 2 batch render entries(2 cameras): the first one rendered correctly, the second one rendered cropped/zoomed.
But it worked fine for other scenes before.
That is very strange.
Can’t reproduce it in my tests with simple setup with two V-Ray physical cameras. Would it be possible to send us your scene file or a simplified version of it? Probably only cameras and a box.
The scene has been sent to Vlado so I suppose you guys are aware of it now.
Unfortunately, Batch rendering was not a work around to Backburner after all, because Batch rendering uses Scene States(you can selects which scene state to be used in a certain Batch rendering render), while I need to make use of the State Sets which can not be used in Batch rendering but only if I submit the scene(each state set) to Backburner.
We would like to inform you that our developers have made some improvements to the latest nightly builds and the discrepancy between the V-ray adv. and RT camera filed of view should be solved.
Please let me know if any issues arise again.
