Distributed rendering clients can't find the output image?

[Ihno]

This is what I'm getting in the console of the workstaion. I.e the one that started the render.



The file thats complained about is the output image that 1. doesent exist yet and 2. all clients have acess to the path of.
Also I'm kinda confused, why would they need acess at all? Isn't that file safed from the master computer?
I'm on Vray7 Hotfix1/Max 2023 im using Progressive image sampler and the "sent missing assets to Client Copmputers" option from the distributed rendering dialogue.
The two clients I'm using are ideling arount 3% on the CPU and actually slow down the render insterad of seeding it up.

[hermit.crab]

Servers most likely need it because Resumable rendering is active. Do they actually have access to the output folder?

[Ihno]

Yes they do have access

[hermit.crab]

Actually, when resumable rendering with progressive, a .vrprog is created, so it's not that. Do they have folder permissions? Are you certain this path is not used for anything else in the scene? Most importantly, are you able to render?

[kosso_olli]

Servers most likely need it because Resumable rendering is active. Do they actually have access to the output folder?

No.
Disabling Transfer missing assets fixed the issue, might be worth a try. Somehow that feature treats the output image (which of course is not there at the beginning of the render), as an asset to transfer, causing the error.
I reported the same issue around 3 years ago:

https://forums.chaos.com/forum/v-ray...missing-assets

[hermit.crab]

It sounds like it's the same issue. Ihno Mind if you send the scene in question so we can troubleshoot? I can't seem to reproduce it on a fresh scene.

[Ihno]

Its rather big, I'd need somewhere to upload it.

[hermit.crab]

Use the contact form.

[Ihno]

I'm uploading it.
My problem occured while starting the rendering locally not via Backburner.
Also it seemed the "The two clients I'm using are ideling arount 3% on the CPU" isn't related to the erros in the log.
It also didn't really work if I turned off the sent missing assets thing. Both in progresive and bucked mode. It didn't seem to be related to the clients RAM.
But I didn't really spent enough time investigating. In the end I gave up on DR and rendered it frame by frame (its only 3) via backburner.
So I'm done with the scene, you dont have to hurry

Edit: the ticked number is: 373070.

[hermit.crab]

Thanks for the provided file. I managed to reproduce the issue on a simple scene, and it is bizarre: you only need DR with active "Transfer Assets", an output path, and... an Atmospheric Effect (regardless of whether it is enabled or disabled). Delete the Atmospheric effect (happens with fog, aerial perspective, toon, etc.), and the error disappears. The error doesn't seem to affect the rendering itself, however, surely it slows down the loading process. I've logged the issue (internal tracker ID: VMAX-14888 ) for dev investigation.

[kosso_olli]

That's a strange bug.
I do believe we had some atmospheric effects turned on when we had the issue back then...

[Ihno]

I'm glad you where able to reproduce it. Bizarre indeed. I would never have thought of that. Especially because the atmospheric effect was turned off in my case.