[HOU-1440] farm rendering forces frame 0000

[jurweer]

hi guys,

our farm is rendering a standalone job with deadline which is forcing the slaves to write frame 0000. This seems strange, as the frame range goes from 1-500. the slaves then error out cos of some permission issue which we cant really locate.
it shouldn't render frame 0000 in the first place though. can you see something in the vrscene that is odd?


hou 17.5.293
vray Build number:5763 hash:565d8ca from 15 Nov 2019 04:16
standalone 4.12

[chakarov]

I've tried to render some of the vrscenes with standalone form 27.September and they where saved successfully, of course in different directory. Is this happen with all of your scenes or just with this one.

[jurweer]

It seems to happen only with vrscene sequence exports...
With single file vrscenes everything renders correctly

[chakarov]

Hello jurweer, I've spoken with some colleagues and appear that the error message contains wrong image file name, the frame is not printed correctly. I've reported this. But the bigger problem with "Permission Denied" is not reproducible here and I am not sure how reproduce it.

[benfox]

I just wanted to +1 this issue. It is something I am running into with VRay jobs submitted from Houdini to Deadline 10.1.3 as batch jobs. It is tough to reproduce, because the Permission denied issue only seems to happen when multiple workers are at the same point in the render task and seem to try to access/write frame 0000. I never see the file show up on the file server, though if I load the sequence in Nuke as it is renders, Nuke seems to be finding an empty frame number 0000 even if the start frame is far from that. I only get the issue when I use batches greater than 1. (which is ideal) Since it doesn't throw a full error, it is a bit involved to get a list of the missing frames and resubmit.

[Gosho.Genchev]

Hey benfox , jurweer ,

are you guys still having those issues? If so, we'll try again to catch this on our side.

[benfox]

Thanks for checking in on this. We've decided to hold off working with Vray Houdini this semester (We are education license users) since we were having a bunch of issues that were cutting into our limited time. Looking forward to digging into the latest version once the semester is over.

[Gosho.Genchev]

I see. Would you mind clarifying what those issues were - are we talking deadline/render farm management or workflow blockers with the Houdini integration itself ?

Thank you!

[ronald_a]

I just like to add that we also have quite a few issues. With us they are mainly with the integration.itself. We are trying to move completly to houdini for all of our 3D work and we keep on stumbling over very basic issues that do not exist in vray/maya or in houdini/mantra. Looking back at all the projects we did using houdini/vray (and we have been using that combo for about 1,5 years now), I can say, that almost none of them had no issues. As a result of that , some of our projects (especially the easier/smaller ones) took a consideralbe amount of time longer to finish because we had to identify the issues and either get them fixed (if we had the time to wait for the fix) or work around the issues.

Sorry if this sounds like a rant, but I just want to make sure you are aware that there are still problems that keep use from using the houdini/vray combo the way we would like to. That beeing said, I do appreciate all the super fast fixes and improvements over the last couple of months and hope that things continue to stabilize going forward.