In Character Animator (v3.4), it is sometimes difficult to tell which latch-mode triggers are active.

This makes it hard to get the puppet back into its default mode, especially when multiple latch triggers are active simultaneously.

It would be very useful if activated latch triggers in the Trigger Panel could visually indicate their state (by changing color for instance).

In addition, currently buttons in the Controls Panel flash briefly when clicked. For latch triggers, it would make sense for them to remain highlighted (or some other visual indication, like a highlighted border) for the entire time the trigger is active.

That would give users the ability to identify active latch triggers and return them to default state as required.

Repro steps:

1. Think like a user/newbie.
2. Create a new project and import Blank.
3. Go into rig mode.
4. Add a trigger to any body part.
5. Add a behaviour to that same part.
6. Right-click the lego/gear icon for that body part.
7. Notice that there's a 'remove all behaviours' option in the context menu.
8. Right-click the trigger icon for the same body part.

Notice that there's no corresponding way to remove all triggers from that body part exposed in the menu.

In addition to creating a bit of an asymmetry between one part of the user experience and another, it looks as if there simply isn't a way to remove all triggers from a body part...

In Panels such as the Project Panel and Puppet Panel, Character Animator organizes information via "tree" structure.

It allows a user to drill into detailed information by clicking the expand icon (right arrow while closed) or to hide the detailed information by clicking the same icon again (down arrow while open).

However, these operations only work on a single node in the tree, so it can be time consuming to achieve the desired view.

It would be useful to support a "Collapse All" command, perhaps via a right-click content menu. This would close all selected nodes, but also close all the child nodes recursively.

Likewise, an "Expand All" command would do the inverse and open the selected nodes and all their child nodes recursively.

Would it be very helpful to directly move the puppet from the preview scene without having to do the old way of adjusting position, rotation, and scale from the transform control? Just like in After Effects, a mini version of Photoshop transform mode.

And moreover, I think it's better to have "Space" button work as navigator in Record mode just like in Rig mode, instead of as play button. Maybe "Shift + Space" can be used as the alternative of play button in Record mode.

And lastly, is it just me, or the navigation hand (space button held) sometimes not working? It still a selection tool (V button). I need to click on the puppet box first in order to have it function as navigation hand. I hope we can change that, meaning no need to touch the box of the puppet first. It caused me to move body parts accidentally while holding space, thinking it is navigating (Space button), but still in move (V button) mode.

The information available on how to do this is, at best, incomplete and at worst, wrong.

Referring to the page here: https://helpx.adobe.com/uk/adobe-character-animator/using/export.html#LipSyncTakeexportforAfterEffects
Step #2 says to create a comp with the visemes "matching the order of visemes in Character Animator’s Visemes context menu" and gives an example of the order being Neutral, Aa, D "and so on".
The problem is that in Character Animator (current version 2.11) the viseme order in the context menu is different. See screenshot.

Just to complicate things, the layer order of the visemes in the default head PSD is different again.

So… which is the correct order? For the record, following the order shown in the contextual menu does not produce the correct results.

The actual process of pasting in the keyframe data works fine, it's just that the visemes being displayed in After Effects don't match the ones being displayed in the original Character Animator capture, and short of endless trial and error, I don't know how to fix it.