Batchrender renderregion bug

[colorbleed]

Hi there,

When submitting a maya batchrender while I have (not purposely) a render region selected in the vray framebuffer, it acts as a render mask. Even if render mask is disabled.

Vray_adv_50020_maya2020_x64 maya 2020.2

Thanks

[hermit.crab]

Render region does not work directly with Maya batch (it requires the -reg flag), so the issue may be caused by something else. Does this happen on every scene? From where do you start the Maya batch (Maya or cmd; do share your command-line options)? If it affects a specific scene, send it to suppot@chaosgroup.com so we can take a look. Mention this thread in the e-mail.

[colorbleed]

Hi Alex,
It happens to every scene I submit to Deadline, directly from Maya.
We are using our own submitter, so I'd have to check if it happens anywhere else too.

Thanks

[colorbleed]

To be more explicit. This is about the V-Ray Frame Buffer's setting for a Region render. Whenever that is enabled in the V-Ray Frame Buffer and we submit the render to Deadline for batch rendering then it will also output the renders as if rendered with that region render.

Note that in our Render Settings the "Render View" > "Disable Region Rendering in batch mode" is ENABLED but it looks like V-Ray doesn't care too much about that as our Deadline Slaves render. Whenever I run the batch render directly in Maya the problem does *not* occur.

from maya import cmds

region = cmds.vray("vfbControl", "-getregion")
region_enabled = any(int(x) != 0 for x in region)   # check whether region is enabled
if region_enabled:
    print("Detected region rendering: %s" % " ".join(region))
    print("Disabling region rendering in V-Ray frame buffer")
    cmds.vray("vfbControl", "-setregionenabled", "0")

Currently we quickly wrote this so we could force disable it through code on submitting to Deadline. Nevertheless, we're very curious to figure out where this is coming from and why the deadline batch render fails to ignore the setting.

[SonyBoy]

I just posted about the same thing. I assumed it was something to do with exporting to vrscene first, as it's the first time I've worked that way and also the first time I've had this problem. Sounds like it's nothing to do with it though?

[SonyBoy]

It would be great if this could get looked at ASAP. This continues to affect our renders.

[Ivo Bakker]

I noticed the same thing. When i rendered a region in the viewport and then render the same image on my render farm it comes out with the same region.

[hermit.crab]

I managed to reproduce the issue when saving single-channel .exrs. Is that the case with you? Setting the Data Window (Image format options>Data Window) to Whole Image resolves the issue and can be used as a workaround. Otherwise, I'll notify the developers about the matter.

EDIT: Logged the issue (internal bug-tracker id: VMAYA-9939) for developer analysis.