forestivy Slave rendering

[WeiweuiAn]

Hello, my 3dmax scene using forestlvy for slave rendering caused a batch of slave computers to crash and fail to render, what needs to be set up for the new version of forest, or how to solve this problem.

[Michal Karmazín]

Hi,

I’ve performed some quick tests rendering ForestIvy using the command line (3dsmaxcmd.exe) without a license, and it worked without any issues. Could you please provide more details, particularly on how the render process is being handled on these nodes, as well as the rendering log? Thanks in advance for any additional information.

Best regards,

[WeiweuiAn]

I've  tested that the slave machine without permission can render normally when it is opened separately, and the rendering will fail when the task is published in deadline
This is the test scene, and when you open it alone, you can see that the rendering is completed in one minute, and the memory usage is only 7GB, while the machine crashes when the rendering is opened for more than 30 minutes and the memory usage is too large

[iToo]

What render engine do you use ?

[WeiweuiAn]

Hello, I'm using vray 6
I tried testing it on other cloud rendering platforms and they had a similar situation, my computer only took up 7 GB of rendering and then sent to the cloud for rendering, which took up to 50 GB of memory, and my slave machine had less memory, causing the computer to crash

[iToo]

We're trying to replicate the problem using Deadline 10, FP 9.1.2, Max 2024 and V-Ray 6, but everything seems correct. Render doesn't take more than 3 Gb. RAM

Please, would you send us a simplificated scene ?
What Max version do you use ?

Thanks,

[WeiweuiAn]

3dmax2022,I'll send the scene later



                Thank you

[WeiweuiAn]

I reopened a scene and had the same issue, didn't use lvy, the problem doesn't exist, I recorded a video and hopefully it will be resolved, I've sent the file

I have sent the document to your email
Thank you     Hope that helps

[iToo]

Thanks for the files. We could identify the problem: it's caused by the Quick-Mesh mode.
It seems when running as render mode, Max deactivates the Nitrous driver and ForestIvy cannot use the Quick-Mesh mode. Instead it generates a standard mesh for the viewport, which takes a lot of RAM.

We'll fix it. Meanwhile, we suggest to set Point-cloud mode, before sending the job to the render queue. That solves the problem.

[WeiweuiAn]

Thank you, I'm going to test it out, thanks for your help