DR nodes load the scene, but don't help with the prepasses

[LQ2]

I'm having a problem with my render nodes on some scenes. When I send the render with distributed turned on, the nodes load the scene but don't start helping with the lighting prepasses. Then usually what happens is that they kick in when the prepasses have finished but then show errors. Why don't the render nodes help with the prepasses?

I'm using V-ray 2.40.04, which is loaded on all the machines, and Max 2014 SP3. As far as I know (I'm 99% sure as I've done the installations) all plugins are loaded on all the machines, and all file and asset paths are correct and UNC.

I hope someone can help.

EDIT: Would it be useful if there was a file to test? I've archived a file up that won't work properly so there is something that I could send to someone for testing, but it's 47,962KB.

Cheers,

Bill

[LQ2]

I've had another thougth, for someone on the technical side of things to consider...

What if some of the files that are x-refs were made using older versions of v-ray, and have not been opened and re-saved using the current version? Would that cause problems?

[LQ2]

So in the meantime I've been doing a LOT of opening references, checking all paths and then saving the files.

For whatever reason, this has fixed my original problem. With all the references (and nested references) saved today, the master file renders correctly. The render starts and then as soon as the files have loaded onto the render nodes they kick in and help with the pre-passes.

I have had this problem with quite a few jobs recently and they have all go the same problem: that they span about 3 versions of Max and V-ray over their lifetime. This means that some files have not been opened and re-saved with the current version of Max. I didn't even know this made any difference.

Anyway, I hope this information is useful to someone else too.

Cheers,

Bill

[svetlozar.draganov]

Glad to hear you sorted it out.

What if some of the files that are x-refs were made using older versions of v-ray, and have not been opened and re-saved using the current version? Would that cause problems?

If they are saved with older version everything should be fine, there might be some issues if they are saved with newer version.

Would it be useful if there was a file to test? I've archived a file up that won't work properly so there is something that I could send to someone for testing, but it's 47,962KB.

It would be useful to test this fine into our environment since it looks like a bug. We could provide our FTP just send us a request at support@chaosgroup.com and include a link to this thread.

[LQ2]

I've sent an email requesting the FTP server details.

It's worth noting that the test should be done without opening or saving any of the reference files. If the x-ref files are opened and saved, the render will work correctly.

Cheers,

Bill

[svetlozar.draganov]

Thanks for the scene - we'll test it now and we'll let know the results afterwards.

[svetlozar.draganov]

Ok - I think I found it.
Check for missing files option is activated and since not all the files are available the slave-machine aborts rendering.
Would it be possible to run one more test on that scene with Check for missing files OFF for confirmation ?

[LQ2]

Hi Svetlozar,

Unfortunately this does not solve the problem with file. I notice that you are using V-Ray 3.00.03, but I am using V-ray 2.40.04. If that solution works for you, perhaps it's solved in the latest version?

It's worth noting that as far as I know, there are no missing maps as when you try with the missing maps button on, there is no error message (perhaps this is an error... not identifying missing maps?). Also when I check the x-refs there are no missing assets.

Any other ideas?

Cheers for looking.

Bill

[svetlozar.draganov]

Yes are right - the scene doesn't work with 2.40.04 - we are investigating it now.
We'll keep you posted.

[LQ2]

Any progress on this?

[tashko.zashev]

Hi Bill,

We did few tests again with your scene using V-Ray version 2.4 and the DR issue seems to be related to missing or not correctly specified X-ref scene in another Xref file (00278-C_Wharf B...)
Please double check the X-Ref scenes paths in your main Max file and open every single X-ref scene to check the paths there too. The status shown in the Asset tracking system should be Network for all of them.


Also we have noticed that one of the Xref scenes was missing at our side, but we are not sure if this is connected to the issue. Please check the file 00278-C_Wharf Bl...max


As soon as we changed all paths to Network for all scenes, DR was successfully running on the render node at the GI stage.


The new option in V-Ray 3.0 for transfer missing maps are very useful for such cases.

[LQ2]

Thanks for looking into this.

I also looked at all the files, and in most cases simply saved the files again, which seemed to sort out the problem. I suspect that some of the files have paths defined by a drive letter (an old setting) and I now have max set to convert paths to UNC. I presume that this sorts out that "found" issue and inputs a UNC path which fixes the files.

Was the missing x-ref turned off in the X-ref scene dialogue? I know there was one like that, but assumed that because it was turned off it didn't factor.

Once again, thanks for looking at this. I have since been through another vast job, saving all the files connected to the master and it too fixed the job and made it render properly on the render nodes.

Cheers,

Bill

[tashko.zashev]

Hi,

Thank you, glad to hare that it works now.

Was the missing x-ref turned off in the X-ref scene dialogue? I know there was one like that, but assumed that because it was turned off it didn't factor.

As far as I remember there was a missing X-ref file, that was removed as soon as we have set all paths to network (UNC). For DR rendering is important to have all external assets properly set, because otherwise different issue are expected to appear.