ummary CC5 is intermittently baking active morph sliders into the base mesh without user intent or notification. The behavior is inconsistent and appears to be dependent on the character's internal state rather than a specific action.
Expected Behavior Morph sliders should remain editable unless the user explicitly invokes Character → Bake Morph Slider, or CC5 should clearly warn the user before any operation that permanently bakes morph data.
Actual Behavior While building characters, active morph sliders will occasionally become permanently baked without any confirmation or warning.
Once this occurs: The morph values return to zero. The character visually retains its appearance because the geometry has been baked.
The original editable morph stack is permanently lost unless the user notices immediately and uses Undo. If the user does not detect the bake before saving, the editable morph data is effectively unrecoverable.
Characteristics of the Issue The trigger is not deterministic.
Examples observed: Applying eyelashes has, at times, baked every active morph slider. The exact same eyelashes later no longer caused baking. Adding clothing has sometimes preceded a bake. Applying poses has sometimes preceded a bake. Saving and reloading has sometimes revealed baked morphs that appeared intact before saving.
Other times, the exact same workflow produces no issue. Because the trigger changes over time, it is difficult to isolate a single reproducible action.
Workflow Impact This is particularly damaging for creators who intentionally keep morph sliders editable. Many professional workflows rely on preserving live morphs so characters can be: - revised later, - used as the basis for related characters, - reused as genetic foundations for character families, or iterated into future designs.
Unexpected baking permanently destroys that flexibility.
Additional Observations This issue appears alongside other morph-system inconsistencies, including: characters occasionally changing scale when poses are applied, morphs occasionally losing stored shape data, inconsistent behavior depending on the current state of the character. While these may or may not share the same root cause, they all involve the morph system behaving inconsistently.
Requested Improvement Even if the underlying bug cannot be immediately reproduced, CC5 should notify the user whenever an operation is about to bake active morph sliders.
A confirmation dialog such as: "The following operation will permanently bake active morph sliders into the character. Continue?"
would prevent accidental loss of editable work.
Or Alternatively, the implementation of a debug panel in CC5 i.e:
"Character State Morph Stack ✔ Valid HD Morph Cache ✔ Valid Subdivision State ✔ Valid Metadata ⚠ Validation Warning Pending Operations • Conform Hair • Rebuild Mesh"
So at the very least we can better troubleshoot these issues ourselves without having to consult support.
Any operation that automatically bakes morph sliders should provide a warning before performing an irreversible action.
