Skip to main content

Using Team Render and command line rendering with Cargo

How your Greyscalegorilla plugins behave on Team Render and command line render nodes, what to install on each one, and what happens to your projects if you don't renew.

Written by Steven Chen

If you render across multiple machines using Team Render or the command line, this article covers what you need on each machine and how your plugins behave there.

Will my plugins work on Team Render and command line nodes?

Yes. Greyscalegorilla plugins are supported on Team Render clients and command line renders, and your render nodes don't need anyone signed into Cargo.

Each node does need the Cargo C4D Connector installed alongside your plugins. The Connector is what allows your plugins to load on that machine. Without it, the plugins won't register and your renders won't include their effects.

Setting up your render nodes

Three things to know if you're on Cargo:

  • Where those guides refer to the HUB plugin folder, copy the KitBashCargoC4D folder for your Cinema 4D version instead — for example KitBashCargoC4D2026. You'll find it alongside the Greyscalegorilla folder in your plugins directory. Everything else in the steps is the same.

  • Team Render client preferences folders end in _c. Command line folders end in _x. Make sure you're pasting into the right one for the kind of node you're setting up.

  • Cargo's installer sets up your main Cinema 4D installation only, so render node setup is a manual copy. Repeat it after you update your plugins, since render nodes don't update on their own.

What happens to my projects if I don't renew?

Plugins and assets behave differently here, so it's worth reading both.

Your assets keep working. Materials, HDRIs, and models you've already downloaded are files on your drive. Your old projects will still find them, as long as you haven't deleted your Studio or Plus library source files.

Your plugins stop loading. Greyscalegorilla plugins require an active subscription. Without one, the plugins won't load in Cinema 4D. Your projects will still open and your assets will still be there, but anything a plugin generates at render time will not work properly.

What if I renew and switch from the HUB to Cargo?

Everything keeps working. Your Team Render setup is unaffected, and your old projects will open with their assets and plugin effects intact, assuming you still have the source assets on disk.

Keeping your license active on your workstation

Keep Cargo open while you're working in Cinema 4D so your plugin licenses stay current. This applies to your workstation, not your render nodes.

Still have questions?

Contact us at support@greyscalegorilla.com and we'll help you sort out your render setup.

Did this answer your question?