Wrong frames being rendered with mayabatch

[Fredrik Averpil]

We noticed something with the 3.60.03 official release for Maya 2018.1. We are guessing that when you're specifying -s (startframe) and -e (endframe), the wrong frames are being rendered - but only on Linux. Windows renders the correct frames.

Example arguments to Render.exe/Render:

-r vray -x 1920 -y 1080 -s 4 -e 6 -rl Film2NoWall -cam renderCam -proj //192.168.0.226/prod/proj255/maya -rd //192.168.0.226/prod/proj255/maya/images/scene3 -im <Scene>_<Layer>_<Camera>. //192.168.0.226/prod/proj255/maya/scenes/scene3.mb

I'm sending the full log to support@chaosgroup.com

Cheers,

[Fredrik Averpil]

The artist who had these issues found a stray Render Setup collection inside of another collection which he didn't recognize. Upon removing that, saving and re-rendering, the issue is now gone.

I'm sending the scene file to support@chaosgroup.com.

[Fredrik Averpil]

We are hitting this issue mid-production and tried changing the renderer to Maya Software to see if the problem persisted, and it went away once rendering with Maya Software. So at least when viewing this issue at a glance, it seems like a V-Ray issue.

The artist experiencing the issue downgraded to V-Ray 3.60.02 but the issue is still being hit.

We don't quite understand what exactly might be causing this.

[Fredrik Averpil]

I think we found the core issue. When we remove render setup layer overrides on startframe, endframe, the correct frames are being rendered. For some reason, V-Ray acts up when you have overrides on these attributes.

We actually wish to be able to set this, so this is a bit problematic for us. Would it be possible for you to have a look at this for an upcoming stable build?

EDIT: To sum it up:
- We specify the commandline arguments -s (startframe) and -e (endframe) when rendering on our render farm.
- When render setup layer overrides are in effect on the startframe, endframe (as in the file sent to support), V-Ray won't render just the frames specified on the commandline.
- I believe this issue is only being hit on Linux (but honestly not entirely sure)

[tashko.zashev]

Thanks for the file Fredrik! We are going to check that out and send a bug report if need.