.vrscene export bug?

[TheScope]

Hi,
I think I found a nasty little bug when rendering with V-Ray Standalone.

I noticed that sometimes the images rendered on our farm look different than what I see when rendering locally with Maya. Sometimes objects or the camera change position slightly.
This only happens when using the option "Each frame in separate file" is turned off when exporting the vrscene file. When exporting one .vrscene file per frame, everything looks correct.
This also happens if the keyframes are bakes.

Here is a link to a zip containing a Maya scene, the exported .vrscene files and the rendered result showing the error.

Specs:
Windows 10
V-Ray 3.52.03
Maya 2017 Update 3

.vrscene files where rendered via Deadline 8.0.14.1 on Windows rendernodes.

Cheers, Florian

[Svetlozar Draganov]

Thanks for the detailed explanation and the attached files, there were very helpful.
I managed to replicate the issue, it looks like a bug so I am going to report it into our system and I'll see if there is a workaround about it.

[Svetlozar Draganov]

The correct result should be the one exported with Each Frame in Separate File enabled, its result is the same as the one rendered in the UA.

[Svetlozar Draganov]

I think I narrow it down to the U/V size animation of the V-Ray lights, those are either not exported properly or V-Ray Standalone doesn't handle them properly.

[TheScope]

Great to hear.
yes, the correct result is the one from the vrscene files per frame.
I also had this error in another scene but there the camera position changes slightly depending on the export method.

My current workaround is to export one vrscene file per frame.

Cheers, Florian

[TheScope]

Is there any news on this bug? Maybe a fix that is already in the nightly builds?

Cheers, Florian