CC5.2: Eye protrusion on blink after official Ryan Head/Eyes presets (native RLPy workflow)
Suspected bug: the eyeballs/iris protrude through closed eyelids after applying the purchased official Ultra Head Ryan content. The issue can be reproduced on untouched official HD Neutral carriers, without Headshot, AI meshes, custom morph creation, or imported geometry.
Environment: Character Creator 5.20.2310.1; Windows 11 Pro build 26200; Intel i7-12700; 64 GB RAM; NVIDIA GeForce RTX 3080, Windows driver version 32.0.16.1060.
Important scope: the confirmed workflow below uses in-process RLPy/RLPy2 and native CC rendering. A separate Content Manager + Edit Facial UI-only reproduction has NOT yet been completed. Please help distinguish an asset/profile issue from an SDK/content-loading requirement. This is not a confirmed version regression; I have not compared the same Ryan assets on an earlier build.
Confirmed reproduction A (Head Morph & Skin): 1. Start with an empty scene and load the official Mixer Ready Base / _HD Neutral M.ccAvatar using RLPy.RFileIO.LoadFile(path, False). 2. Select the avatar and apply the installed Avatar Preset / Head Morph Skin / Ultra Head / Male Asian / Age21-Ryan.ccAvatarPreset through the same native LoadFile API. 3. Use mesh subdivision level 2 and pose mode. Set non-corrective expressions and gaze to neutral; allow the C_ corrective controls to evaluate normally. 4. Sample Eye_Blink_L and Eye_Blink_R at 0.0, 0.5 and 1.0 using FaceComponent.BeginKeyEditing(), AddExpressionKeys() and EndKeyEditing(). Update the actor/viewport and inspect native renders. 5. At 1.0 on both sides, parts of the iris/eye visibly protrude through the upper eyelid. The attached original-material image shows this directly. 6. Save/reopen the neutral project and repeat. The result persists. Neutral state/local geometry and the evaluated blink phases were checked after reopening.
Control: repeat the same sampling on the untouched official _HD Neutral M and _HD Neutral F carriers. Neither has the large eye protrusions. Strong diagnostic exposure was zero in three closed-eye views for both controls; the male control had 6 weak pixels in one oblique view, recorded separately rather than described as perfect closure.
Confirmed reproduction B (Eyes part): Load untouched _HD Neutral F, start ActorMIXER with Current, select Eyes, load Age21-Ryan_Eyes.ccMixerPreset and move to 100% Ryan. Blend Facial Profile is enabled; Conform Cloth disabled; Conform Hair enabled. The source Eyes/Eyelash weights become 0, the three Ryan Eyes/Eyeball/Eyelash weights become 1. Materials are unchanged. After native FixEyeElement(), the blink protrusions also occur. This only applies existing purchased content; Create Mixer Assets is not called.
Additional isolation: - The defect is visible with original materials in native CC rendering, so it is not just a Blender preview or a changed normal-map appearance. - Making the cornea opaque exaggerates the area. With cornea explicitly hidden and only the actual eye surface marked cyan, substantial exposure remains (Head Morph & Skin: front/negative35/positive35 = 10099/12508/4943 strong pixels in a fixed 2000-square view). Cornea-only visibility does not explain the issue. - Repeating the same Eyes mix with Blend Facial Profile disabled gives identical neutral shaping/materials/local geometry and no meaningful closure improvement. - No Correct Eyeblink command or Eyeball Depth adjustment was applied to the attached official-asset cases.
Expected: applying the complete official Ryan head preset, or the official Eyes preset with facial-profile blending, should provide compatible eye positioning and blink deformation without the iris penetrating closed eyelids.
Could you confirm whether this is a known content/CC5.2/SDK issue, or whether a documented profile/eye setup step is required? In particular, should LoadFile(ccAvatarPreset) and the native ActorMIXER result match normal Content Manager application? Please provide the supported reproduction/workaround if a different profile application or initialization step is necessary.
Attachments contain only official carrier/Ryan renders. They contain no custom likeness, reference photographs, project files, account credentials, or personal filesystem paths. An official-assets-only saved project and more detailed API trace can be supplied privately if needed.