![]() ![]() ![]() 10:08:36: 2: Executing plugin command of type ‘Initialize Plugin’ 10:08:36: 2: Done executing plugin command of type ‘Sync Files for Job’ 10:08:36: 2: Plugin Cinema4DBatch was already synchronized. 10:08:36: 2: All job files are already synchronized 10:08:36: 2: Executing plugin command of type ‘Sync Files for Job’ 10:08:34: 2: Loading Job’s Plugin timeout is Disabled I am on Deadline 10.0.17.7 now, maybe this is why the plugin isn’t reporting stdout from redshift anymore? = No more info about Buckets rendering and the like. The Task Reports though have now become very short. Thank you this seems to be working! I rendered with GPUs per Task = 1 and concurrent tasks = 1 and checked it with gpu-z and there only is one gpu rendering. I seems like Deadline does not override the Redshift Cinema 4D settings at all? Now when I deselect one GPU in the Redshift Cinema 4D Options inside of Cinema 4D, now it only uses one GPU no matter what GPUs per task or Affinity I set. Out of curiosity I tried setting the GPU Affinity in the Slave properties to 1. Instead it renders 2 tasks on 2 GPUs simultaneously, clogging the VRAM and ultimately crashing the renderer on heavy scenes. This should now render 2 tasks, one on each GPU. And I set the Concurrent tasks from 1 to 2. What I do is I set the GPUs per task from 0 to 1. Cinema 4D r18, Redshift 2.6.14, Batch Plugin ![]() The GPUs per task or the GPU Affinity does not seem to change anything about this. ![]() Or maybe I am doing something wrong?īatch submitting a Cinema 4D Job render with redshift always uses GPUs that are selected in the Redshift options inside of Cinema 4d. I just wanted ask if this is a known issue, bug or a limitation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |