What is in scope?
For Luma Genie output, define the asset, destination, and release condition before editing. Keep a clean source copy and state why joint-area topology is relevant to rig readiness.
Plan rig readiness for Luma Genie output. Review the source, test the destination export, and document settings, evidence, and open risks.
For Luma Genie output, define the asset, destination, and release condition before editing. Keep a clean source copy and state why joint-area topology is relevant to rig readiness.
For rig readiness in Luma Genie output, treat unresolved neutral pose as blocking. Decide whether it needs a technical fix, additional evidence, or a qualified reviewer.
For rig readiness, require a representative result in Luma Genie output, the accepted export settings, and a clear outcome for rigid-part separation. Record who approved the final package.
The practical approach is straightforward: for Luma Genie output, begin with joint-area topology, then test neutral pose and rigid-part separation in the actual destination. Keep the accepted export settings and any unresolved rig readiness risks with the source file.
Open the original file before making changes. For Luma Genie output, record its format, units, dependencies, and current joint-area topology so the rig readiness pass has a reliable baseline.
During rig readiness for Luma Genie output, establish the expected state of joint-area topology. Resolve or document any gap before moving on to neutral pose.
Do not rely on the authoring viewport alone. For rig readiness, load a representative export in Luma Genie output and verify neutral pose together with rigid-part separation.
For Luma Genie output, keep the accepted export, its settings, and a short note about unresolved risks. Name the person responsible for the final review of rig readiness.
| rig readiness check for Luma Genie output | Luma Genie output pass condition for rig readiness | Evidence to keep for Luma Genie output rig readiness |
|---|---|---|
| joint-area topology during rig readiness for Luma Genie output | For Luma Genie output rig readiness, the source and revised asset use an agreed value for joint-area topology. | Keep Luma Genie output rig readiness before-and-after values and the setting that changed. |
| neutral pose during rig readiness for Luma Genie output | The rig readiness result for neutral pose matches the expected behavior in Luma Genie output, not only in the editor. | Keep target-side evidence for Luma Genie output rig readiness, such as an import log or captured test. |
| rigid-part separation during rig readiness for Luma Genie output | The recorded result for rigid-part separation meets the Luma Genie output release requirement for this rig readiness job. | Keep the accepted Luma Genie output result and the reviewer name for rig readiness. |
| naming readiness after rig readiness for Luma Genie output | The rig readiness handoff for Luma Genie output contains only the files needed downstream. | Keep the Luma Genie output export preset, fallback, dependencies, and open risks from rig readiness. |
Luma Genie output is a starting point, not proof that an asset is production-ready. A rig readiness pass should distinguish generation artifacts from deliberate form before anyone spends time polishing the result.
For Luma Genie output, use a short representative clip to verify joint names, rest pose, frame range, root motion, and deformation. Preserve the source rig until rigid-part separation passes review.
Check edge flow around joints, neutral pose, separate rigid parts, naming, and expected deformation before rigging begins. Apply this rig readiness guidance to the actual Luma Genie output delivery path.
During rig readiness, compare the source and destination values for joint-area topology. Do not continue until the difference is explained and assigned to the asset or the Luma Genie output pipeline.
For rig readiness, capture the Luma Genie output result and isolate the responsible layer. A clean authoring preview is not proof when the exported neutral pose result no longer matches the baseline.
Define an observable rig readiness result or move the decision to a qualified Luma Genie output reviewer. Do not hide an unresolved rigid-part separation risk behind a general “ready” status.
For Luma Genie output, start with joint-area topology on the untouched source file. It gives you a baseline before the rig readiness pass changes geometry, materials, metadata, or export settings.
During rig readiness for Luma Genie output, record the source format, units, texture locations, material slots, exporter, destination version, and observed neutral pose behavior.
The rig readiness pass is complete when joint-area topology, neutral pose, and rigid-part separation have been tested in Luma Genie output, the export opens correctly, and remaining review has an owner.
For Luma Genie output, use a qualified reviewer during rig readiness when rigid-part separation cannot be verified automatically or when licensing, device, marketplace, or domain rules affect approval.