In Nuke the Afanasy node has an option to set tickets. But the Afanasy plugin for Blender - which is provided with CGRU - has very limited set of options:
OK, now I have it working. The default md5 sums in config files are incorrect. I generated the default password myself - the md5 sum is different - and now it works.
Yes, sorry, I meant AfWatch - there is no password field to type in the password. Typing it just in the AfWatch window doesn't do anything.
I have already changed the password in the config file.
The afrender processes were run by the same user. Nuke is started from central location, so it's always the same version on all machines. For now I had to go back to 3.2 as I'm in a middle of a project, so I can't do more tests for now. My main reason for updating CGRU was to also upgrade Ubuntu to ...
Yes, this path is the same when using both CGRU versions. Works without any problems in 3.2
Strangly I also sent a Blender test render on CGRU 3.3, and that worked fine. The errors showed up only for Nuke renders.
Hi, I've just upraded all machines to CGRU 3.3 and everything seemed fine until I started a Nuke render, which renturned this: Nuke 13.2v4, 64 bit, built Sep 5 2022. Copyright (c) 2022 The Foundry Visionmongers Ltd. All Rights Reserved. Starting CGRU Nuke add-ons from: /opt/cgru/plugins/nuke Temp di...
Hi, Should a client with CGRU 3.3 be able to connect with 3.2 server? Or do they all need to have the same version? I've just updated one workstation/render node to 3.3 (for Ubuntu 22.04) and the server (Ubuntu 20.04) doesn't see it anymore. Also I can't open Watch on that workstation anymore, altho...