DR2 - Render node delay

Currently I have just one render node. I’m finding the that a cluster of buckets will remain unrendered as the main workstation finishes. There will be a pause for say 10-20 seconds or so and the render node machine will kick in and finish off the remaining buckets. This is different behaviour than how it used to be. I realise that the scene needs to be transferred to the node, however it seems that a number of buckets are assigned to the node and will remain inactive until it’s ready? Hope that makes sense.

Mind if you show a video of this? Does it happen with a DR1 build?

Hey Aleksandar

I’ve saved a video here: DR2_Scene_Edit.mp4

It’s been edited so you don’t get too bored watching it. As it says in the video, the render process sat idle for more than 2 minutes before the render node finished it off.

I installed the DR1 build on both machines and it’s working again as expected with the old behaviour. The node only kicks in when it’s ready. For anyone reading this - reverting to the DR1 build requires setting the render nodes to use 20204 as the Port instead of 20208.

Would it be fair to say DR2 would not be ideal for a 1 or 2 render node setup?

Cheers

Quite odd. I managed to reproduce it on my end. Will talk to the devs about it and report back.

After discussing the matter with the devs, it seems that the “reservation” of buckets is by design, however, the local dispatcher (“use local host”) should render such buckets if the scene has not yet been transferred. I’ve logged the issue (VMAX-15665) for investigation.

Hey Aleksandar - thanks for the quick response and looking into it.

Hey there, we are also here to report this issue - attaching a screenshot that shows the black buckets that seem to be reserved for the render nodes that will join the job.

Also - if I am not remembering wrongly, in the previous versions the calculation of the GI was visible also on DR mode.

This is no longer the case, is there a way to bring this back? It is quite helpful to have - was there a reason it was removed?

3ds Max 2026.3.2
V-Ray 7.30.04

Cheers :slight_smile:

I tested a fix for this yesterday, and it seemed promising. Will inform you whenever a nightly build is available for testing.

It’s an issue that’s already logged (VMAX-15013).