DR Bug with Film Offset attribute

[snivlem]

Hi,

Sometimes regardless of scene I notice that V-Ray DR slaves fail with this Film Offset parameter. Probably like about 5% of the time but when it happens it's annoying.



For here, I only have one slave activated and it seems to be ignoring the attribute. However if I resubmit the job and render again it will probably work. Regardless of scene sometimes I think V-Ray forgets to check this???

[t.petrov]

Hi,

What version of V-Ray are you using?
Are all machines using the same version?

/Teodor

[snivlem]

Hi Teodor,

Yes all machines running same version and all on Win 7x64.

[2012/Aug/31|09:30:21] V-Ray: V-Ray for Maya version 2.25.01, revision 22329 from Aug 21 2012, 02:00:31
[2012/Aug/31|09:30:21] V-Ray: V-Ray core version is 2.00.02

There is nothing special with the scene or camera, just a standard phys cam, sun+sky setup with camera attr - verticalFilmOffset 0.05;

[t.petrov]

Hi,

And sorry for the delay.
Is this problem happening very often?
Also does it happen again, if you retry to render the whole animation?

We've tried to reproduce it, but we couldn't. I guess it is something
related to your setup or network (if it is not scene dependent).

/Teodor

[snivlem]

Hi Teodor, I have the same problem this time with a completely different scene.

Once it uploads (72mb), I'll send a link to the scene to vraymaya@chaosgroup.com.

[yolov]

Hi snivlem,

We've been trying to reproduce this but we've had no luck with it so far. Could you give us more info that will hopefully point us in the right direction, for instance - how many machines you're using, what OS they are running, how many CPU/cores they have / memory etc.
Also, if you happen to come across this issue again, would you please send us the logs and the vrscene files from the network machines, they might be of use for solving the problem. We'll keep on looking into this, of course.

Best regards,
yolov

[snivlem]

Hi Yolov, I ended up sending in the scene and I promptly received an email from support yesterday that the problem had been found and forwarded to developers.

Thanks for the help, I appreciate it.

[tashko.zashev]

Hi again,

Most probably this issue is related to the "Candle" reference object in the scene, so you can try to hide it and make a test render in your environment.
Note that it is added to our bug tracking system and when we have any update on this, we will let you know.

[snivlem]

Thanks for the update.

[everythinghasfresnel]

I have been encountering this exact same problem frequently.

I'm on Mac OS 10.6.8 with Maya 2013 SP2 and V-Ray 2.25.01. I'm currently using one slave machine, both machines are matching Mac Pros. The master machine respects the Film Offset, but the slave ignores it. It appears that the first couple irradiance and indirect illumination passes render fine, but that last pass where everything resolves is where all the buckets get scrambled. The render logs don't appear to report anything unusual, but maybe I'm looking at the wrong ones.

This happens inconsistently. If I cancel the render, it may or may not happen again... 50/50 I suppose. Restarting Maya or disabling/reenabling DR rendering doesn't seem to fix it every time. At this time, it's not reliable enough to use both Film Offset and Distributed Rendering. A solution would be much appreciated.

[yolov]

Hi,

Can you give us the exact build number (revision) from the log in the terminal?

We had an issue with this, but it was fixed some time ago and it should be working properly in the more recent nightlies.

Best regards,
yolov

[everythinghasfresnel]

I do believe we are running a recent nightly, though not sure how recent. This is what comes up when I run vrayslave on the slave machine via Terminal. If you're looking for a different number, I'm not sure where to find it.

[2013/Mar/5|12:19:03] Reading configuration from "/Applications/Autodesk/maya2013/vray/bin//vrayconfig.xml"
[2013/Mar/5|12:19:03] ===============================================
[2013/Mar/5|12:19:03] V-Ray Standalone, version 2.25.01 for x64
[2013/Mar/5|12:19:03] Copyright (C) 2000-2012 Chaos Group Ltd. All rights reserved.
[2013/Mar/5|12:19:03] Use -credits option for additional third-party copyright notices.
[2013/Mar/5|12:19:03]
[2013/Mar/5|12:19:03] Build 22637 from Jan 8 2013, 15:22:41
[2013/Mar/5|12:19:03] Compiled with GCC-compatible compiler, version 4.2
[2013/Mar/5|12:19:03] Operating system is Mac OS X
[2013/Mar/5|12:19:03]
[2013/Mar/5|12:19:03] V-Ray core version is 2.00.02
[2013/Mar/5|12:19:03] ===============================================

[yolov]

Ok, it's a pretty recent one, I just wanted to make sure. One more question - are you by chance rendering in batch mode? And if so - have you tried a regular render via Render view / VFB to see if the problem is still there in this case?

[everythinghasfresnel]

Sorry, I meant to specify that. I haven't tried to replicate this problem by using Terminal batch render (Render -r vray ...). So far I think I've only had this problem with the V-Ray frame buffer, but I'll try to run some tests to see if it pops up elsewhere. It's not the first time this has happened, but I thought it was a problem with switching back and forth between render cameras.

[yolov]

Hi again,

I'm sorry I didn't notice this earlier. You're using a build from Jan 8 and we've fixed this some days after that date. Please try again with build 22717 from Feb 7. Hopefully, you shouldn't run into this with it.