Skip to content

Troubleshooting & FAQ

SuperSolo works on the selection — select at least one object first. If the licence window appeared and you closed it, SuperSolo isn’t licensed yet; see Licensing & support.

Look on the Chroma menu, or type SuperSolo into Commander (Shift + C). If it isn’t in either, Cinema 4D didn’t load it: check it is installed for the version of Cinema 4D you are running (2024.2 or later), restart Cinema 4D, and look in Extensions ▸ Console for lines starting [SuperSolo].

Give it the Ignore tag — on the top of its hierarchy, with Include Children ticked if it is a rig. Then un-solo and solo again.

In a full solo, everything outside the solo is switched off, not just hidden. If a soloed object depends on something outside the solo — a MoGraph effector, a deformer that isn’t its child, a target for a tag, a field — that thing stops working until you un-solo. Add it to the selection when you solo, or give it the Ignore tag.

A viewport-only solo (Shift + click) only hides things in the viewport, so it doesn’t have this effect.

While a solo is on, Shift + click takes the selected objects out of the solo. To start a viewport-only solo instead, un-solo first, then Shift + click.

Ctrl + click or Alt + click says “Camera Active”

Section titled “Ctrl + click or Alt + click says “Camera Active””

The viewport is looking through a scene camera, which framing can’t move. Switch the viewport to the default camera and try again — see Frame and zero.

The tint comes from the Chroma Preferences plugin. If it isn’t installed, or no colour has been set, SuperSolo shows the solo with the outline, button and status bar only. See Preferences.

SuperSolo puts your background colour back on its own — when you un-solo, when you switch to a document that isn’t soloed, or the next time it runs after Cinema 4D closed mid-solo. If the colour is still wrong, solo any object and un-solo it again.

There are “ChromaSolo” layers in my Layer Manager

Section titled “There are “ChromaSolo” layers in my Layer Manager”

They belong to the active solo and are removed when you un-solo. Leave them alone while soloed — see Hierarchies and materials.

End a solo by clicking SuperSolo again — that is what puts every object back exactly. Use Undo for the changes you make inside a solo, such as an Alt + click move to the origin.

Yes, but un-solo first if you are handing the file to someone else, so they open the scene as you built it rather than with most of it hidden.

A full solo does: hidden objects are left out of renders until you un-solo. A viewport-only solo doesn’t. See Soloing.

Open a support ticket — see Licensing & support. Copy any lines starting [SuperSolo] from Extensions ▸ Console into your ticket.