Maya 2022.3: Redshift 3.0.66 hangs in CMD
Posted: Thu Mar 03, 2022 5:12 pm
Hello,
I have issues with Maya 2022.3 and Redshift 3.0.66. Some clients will render frames and take the next ones. Other clients will render their first frame and get stuck.
In my research, I found out that the issue is caused by the CMD rendering. Redshift will return the license but the command "render.exe" will not quit.
From Maya folder bin I start the following rendering like done in CGRU:
.\render -r file -s 1 -e 1 -b 1 -rd "\dus-pc-0021\fileserver-dus\rendertest\LEGO_Nexo_Knights\images" "\dus-pc-0021\fileserver-dus\rendertest\LEGO_Nexo_Knights\scenes\Nexo_Knight_Macy_v021_CGRU.mb"
On the working clients the rendering will be finished and exit to C:\Program Files\Autodesk\Maya2022\bin>.
On the broken clients, the rendering will be finished without an exit.
I can't find out what is different between the PCs. I also reinstalled everything. Must be a mix between Redshift and Win 10.
The same procedure with Arnold works on all clients.
Conclusion: Looks like a Redshift bug?!
Is there any way to force the exit of the render.exe process by modifying the specific script in CGRU?
Thanks for your help!
I have issues with Maya 2022.3 and Redshift 3.0.66. Some clients will render frames and take the next ones. Other clients will render their first frame and get stuck.
In my research, I found out that the issue is caused by the CMD rendering. Redshift will return the license but the command "render.exe" will not quit.
From Maya folder bin I start the following rendering like done in CGRU:
.\render -r file -s 1 -e 1 -b 1 -rd "\dus-pc-0021\fileserver-dus\rendertest\LEGO_Nexo_Knights\images" "\dus-pc-0021\fileserver-dus\rendertest\LEGO_Nexo_Knights\scenes\Nexo_Knight_Macy_v021_CGRU.mb"
On the working clients the rendering will be finished and exit to C:\Program Files\Autodesk\Maya2022\bin>.
On the broken clients, the rendering will be finished without an exit.
I can't find out what is different between the PCs. I also reinstalled everything. Must be a mix between Redshift and Win 10.
The same procedure with Arnold works on all clients.
Conclusion: Looks like a Redshift bug?!
Is there any way to force the exit of the render.exe process by modifying the specific script in CGRU?
Thanks for your help!