Show Posts
1
[Max] Bug Reporting / Re: Another :) Corona not using all threads topic
« on: 2023-08-07, 13:20:50 »
Hello Avi :)
Working fine - Correct.
Not working fine - Using Pulze or any other Render manager (for example, Backburner - tested it thoroughly before moving to Pulze).
- I'm using 3DS Max 2024;
- I'm using the latest stable version of Pulze RM;
- When using Corona DR without Pulze, everything is okay (although I didn't have time to test all the scenes with Corona DR only);
- This issue is appearing in every third or fourth scene (sometimes it is a simple scene like a product shot, sometimes is "normal" interior scene, and sometimes it is a large exterior scene);
- When using Pulze RM, the network speed is okay, the scene is being transferred really fast, RAM usage is okay (the system is using the same amount of ram as it is was being used when I tested the scene on standalone rendering on the WS), and Disk usage - I'm not sure what you mean. I have more than enough free disk space on the node (above 250GB of free space);
- Render node power settings are all maxed out, it is not on a power-saving plan;
- I hardly doubt that there is any background process that could be doing some interference (on the Render node, I only have Win 11 WS, 3DS Max 2024, Corona, and Pulze installed).
Regards,
Namik.
PS, I have also tried pasting this "int progressive.boxScramblingPassLimit = 1000" into the dev rollout, and this is the graph (please see the attachment)
Also, upon checking 3ds max process priority, I could see that it has been sat to "below normal" automatically.
PS 2:
I have tried to tweak 3DS Max priority settings with the Process Hacker and managed to leave it automatically at "High", but still, the CPU usage looks jagged, with lots of drops, etc. Please see attachment number 2 (I have marked with red important stuff on the screen: priority, CPU usage, and the estimated rendering time). As for the estimated rendering time, my WS (Ryzen 5950x renders this scene in the same amount of time. Targeted noise threshold is 3%). So, my guess is that the dual Epyc setup should eat this scene in 2-3 minutes at least?
PS 3:
Now, what I did was to only take one asset from the scene and copy/paste it to the new fresh 3DS Max scene, setup the lights, set it to 2000px resolution and 3% noise threshold. Copied the scene directly on the Node and ran in there (double click on the scene file and just press render), and now the results are even weirder. Now the CPU usage is constantly at 100% but the render time estimation is longer (I really can not believe that I'm seeing this). Please see attachment number 3.
Working fine - Correct.
Not working fine - Using Pulze or any other Render manager (for example, Backburner - tested it thoroughly before moving to Pulze).
- I'm using 3DS Max 2024;
- I'm using the latest stable version of Pulze RM;
- When using Corona DR without Pulze, everything is okay (although I didn't have time to test all the scenes with Corona DR only);
- This issue is appearing in every third or fourth scene (sometimes it is a simple scene like a product shot, sometimes is "normal" interior scene, and sometimes it is a large exterior scene);
- When using Pulze RM, the network speed is okay, the scene is being transferred really fast, RAM usage is okay (the system is using the same amount of ram as it is was being used when I tested the scene on standalone rendering on the WS), and Disk usage - I'm not sure what you mean. I have more than enough free disk space on the node (above 250GB of free space);
- Render node power settings are all maxed out, it is not on a power-saving plan;
- I hardly doubt that there is any background process that could be doing some interference (on the Render node, I only have Win 11 WS, 3DS Max 2024, Corona, and Pulze installed).
Regards,
Namik.
PS, I have also tried pasting this "int progressive.boxScramblingPassLimit = 1000" into the dev rollout, and this is the graph (please see the attachment)
Also, upon checking 3ds max process priority, I could see that it has been sat to "below normal" automatically.
PS 2:
I have tried to tweak 3DS Max priority settings with the Process Hacker and managed to leave it automatically at "High", but still, the CPU usage looks jagged, with lots of drops, etc. Please see attachment number 2 (I have marked with red important stuff on the screen: priority, CPU usage, and the estimated rendering time). As for the estimated rendering time, my WS (Ryzen 5950x renders this scene in the same amount of time. Targeted noise threshold is 3%). So, my guess is that the dual Epyc setup should eat this scene in 2-3 minutes at least?
PS 3:
Now, what I did was to only take one asset from the scene and copy/paste it to the new fresh 3DS Max scene, setup the lights, set it to 2000px resolution and 3% noise threshold. Copied the scene directly on the Node and ran in there (double click on the scene file and just press render), and now the results are even weirder. Now the CPU usage is constantly at 100% but the render time estimation is longer (I really can not believe that I'm seeing this). Please see attachment number 3.