Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Feature Requests => Topic started by: Dan Rodgers on 2017-07-21, 06:52:09
-
Restart CoronaDR on render end - same as V-Ray default DR option. We are currently having a few problems with DR where jobs pick up but don't actually start, they load 5-6gb into ram then just stall indefinutly. Restarting CoronaDR fixes it straight away. This is across multiple scenes, generally when they are quite heavy or if the previous scene was quite heavy. So would be nice to have a 'fresh' CoronaDR running after each render.
Use localhost option would also be nice, so we can DR but not use the local machine and continue to work/render.
-
Restart CoronaDR on render end - same as V-Ray default DR option. We are currently having a few problems with DR where jobs pick up but don't actually start, they load 5-6gb into ram then just stall indefinutly. Restarting CoronaDR fixes it straight away. This is across multiple scenes, generally when they are quite heavy or if the previous scene was quite heavy. So would be nice to have a 'fresh' CoronaDR running after each render.
Use localhost option would also be nice, so we can DR but not use the local machine and continue to work/render render.
+1
-
+ 2
-
+3
-
having same issue as OP where dr jobs dont actually start and restarting drserver seems to fix it.
A 'restart dr on render end' feature would probably help. i used to have a postrender script that killed the max process on the dr nodes but something changed from 1.5 to 1.6 with the drserver so that method doesnt work anymore. It just kills the process constantly.
-
having same issue as OP where dr jobs dont actually start and restarting drserver seems to fix it.
A 'restart dr on render end' feature would probably help. i used to have a postrender script that killed the max process on the dr nodes but something changed from 1.5 to 1.6 with the drserver so that method doesnt work anymore. It just kills the process constantly.
I have the same problem often
-
I don't think that introducing some kind of auto-restart "feature" is the right approach here. It would be infinitely better just to try and fix the underlying issue. Unfortunately we were never able to reproduce this. You can definitely help us by generating minidump from both DR server and 3ds Max on slave (+ DR logs) when this issue happens.
Please see following help page on how to generate minidump without 3ds Max crashing:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-3ds-max (https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-3ds-max)
Gathering DR logs:
https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065 (https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065)
-
I don't think that introducing some kind of auto-restart "feature" is the right approach here. It would be infinitely better just to try and fix the underlying issue. Unfortunately we were never able to reproduce this. You can definitely help us by generating minidump from both DR server and 3ds Max on slave (+ DR logs) when this issue happens.
Please see following help page on how to generate minidump without 3ds Max crashing:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-3ds-max (https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006-how-to-report-issues-3ds-max)
Gathering DR logs:
https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065 (https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065)
Should I send a minidump if my issue is that the DR machine is still running CPUs at 100% even once the render had completed? When I log into the node I see the CPU drops back down to normal. Sorry if this is hijacking but the OP suggestion would remedy my problem too.
-
I don't think that introducing some kind of auto-restart "feature" is the right approach here. It would be infinitely better just to try and fix the underlying issue.
This attention to detail is what attracts me to Corona.
-
Should I send a minidump if my issue is that the DR machine is still running CPUs at 100% even once the render had completed? When I log into the node I see the CPU drops back down to normal. Sorry if this is hijacking but the OP suggestion would remedy my problem too.
If you're somehow able to generate minidump in the situation where the CPU utilization still sits at 100%, that might be helpful.
-
We have released a new daily build yesterday (V3 RC2) which has various DR bugfixes included, and also a "Restart 3ds Max after render" checkbox in the DR server window.
If you have the time, and if you are able to install the experimental daily builds, please test it, and let me know whether there is an improvement with the "Restart 3ds Max" checkbox enabled and without it. It is very important for us to gather information about the performance of the DR server with this checkbox enabled and disabled.
Please note that the newest daily build has to be installed on all computers taking part in distributed rendering, and the newest DR server has to be launched on the render nodes.
More information:
Dedicated forum thread - https://forum.corona-renderer.com/index.php?topic=22160.0
Daily builds - https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015
-
We have just released RC5, which includes yet another DR fix ("Fixed DR server sometimes getting stuck when restarting slave 3ds Max").
If possible, please try it with the "restart 3ds Max" option on and off, and let me know about the results.
The RC5 can be downloaded from https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015