I’ve just realized that the C4D plug-in for Windows is calling Cinema 4D.exe – am I right that this is calling the 32-bit app, and I need to change it via Configure Plug-ins to make it use the 64-bit version?
After I do that, do I need to restart the slaves or will they automatically pick up that change while they’re running?
–Rob
Yeah, you can just change the plugin config to point to the 64 bit version. When a slave picks up a new C4D job, it will use the updated config, but slaves that are already working on a C4D job won’t notice the change until they move on to a new job. So a restart of all your slave apps ensures that they all use the updated plugin.
Cheers,
Just to clarify –
The slave will notice & use the new executable on its next TASK or only when it switches jobs?
And out of curiosity – why default to 32-bit?
–Rob
When it switches jobs.
I think back when we first added C4D support, it was only 32 bit, and only had Cinema 4D.exe as an option. We never gave it any thought before (mainly because most 32/64 bit apps have the same executable name), and this is the first time someone has actually brought it up. 
We can probably start including the 64 bit ones in the default paths.
Well at least changing the plug-in in one place is easy enough. Our last system, we had to rename the executables on all nodes. That got messy, as you might imagine.
–Rob