Product versions: Character Creator Trial 5.13.2031; Python API 0.8.4.
We are testing avatar.GetAvatarShapingComponent().SetShapingMorphWeight for one Head Width morph.
Entering native Modify UI value 10 produces API getter value approximately 0.1 and a visibly wider head. Setting the same morph to raw 0.1 through Python produces the same visible deformation and matching aggregate geometry measurements—2,147 changed vertices—but the native Modify field and slider remain displayed at 0.
After the setter, we call RGlobal.ObjectModified for the avatar with RLPy.EObjectModifiedType_Attribute | RLPy.EObjectModifiedType_Transform, then RGlobal.ForceViewportUpdate. The getter returns approximately 0.1. Restoring raw 0 returns the geometry and getter exactly to baseline. Toggling Modify visibility did not synchronize the displayed value.
What is the supported API sequence in CC5.13/API0.8.4 for refreshing or rebinding the native Modify morph field and slider after SetShapingMorphWeight? If no supported refresh exists, is this a known limitation or defect, and what workaround is recommended?
Separately, what is the supported non-mutating way to obtain authoritative per-morph minimum and maximum values before the first write? Reallusion staff has described initially lazy-loaded/placeholder slider data and a same-value setter workaround. Should pre-write GetShapingMorphMinMax results be treated as unverified until initialization? Is there a supported alternative that avoids writing thousands of morphs?
We are developing a connector that must constrain edits safely and keep API state and native UI visibly consistent.