CLO3D Guide

The following workflow visualizes the steps needed in CLO3D to ensure the exported files adhere to our Content Service input specifications. There are two paths with similar steps to produce the necessary data. In the sections below, the steps for the two paths (2D Output, 3D Output) are explained in detail.

Avatars

All CLO3D garments need to be fitted and simulated on an appropriate avatar, that is known to Reactive Reality, and that is stored within the .zprj file of each garment. Within these files, the avatars should be standing in a-pose. The avatar must have the same size as the garment size, which should be the base size, the garment was designed in.

RR Avatars

In case you don’t have appropriate avatars, we can provide you with male and female “RR Mannequin” avatars, that you can import into your .zprj files to fit and simulate your CAD garments on within CLO3D, to get the best possible output for downstream processing according to our specifications, including appropriate output for our 2D Virtual Photography use case.

The RR mannequins have average body proportions and are posed in a neutral and slight A-pose to provide a neutral shape for the resulting fitted and simulated garment. Use the below links to download the RR mannequins.

The expandable section below describes how to import the RR Avatars into your .zprj files

Custom Avatars

Alternatively to using the RR Avatars, you can choose to provide us your .zprj garment files and generated output based on the avatar files you have used in the design process of your garments.

In this case, please provide the avatar or avatars you are intending to use for your selection of garments beforehand in an .zprj file (single avatar per file) and in addition in either .avt or .obj format prior to the garment datasets. Please note that we need charge per avatar import.

Color and fabric variants

If your garment has different color or fabric variants, RR will create separate assets of each color and fabric variants.

Color variants of the same garment need to be defined within the garment’s .zprj file using CLO3D's Colorways feature.

Fabric variants of the same garment need to be reflected in separate .zprj files for each variant, since each pattern piece within one .zprj file can only have one type of fabric assigned at a time, and different fabrics need to be saved, simulated and exported individually.

2D Output

1. Check fit on avatar and simulate on avatar

→ position the pattern pieces around the shape of the avatar
→ simulate and check the result for self-intersections or intersections with other patterns like buttons and trims or hard edges and fix them with new iterations of simulation using the appropriate toolset (mesh tool (lasso, box, brush), pins, tack, freeze, solidify, ..., etc) until everything looks sound.

2. Render out Frontal + Back Images

→ use the RR HDRi file to match the light conditions of the RR Avatars. Don’t forget to check and adapt the Light Intensity (1 for bright garments, up to 1,5 for dark garments)

→ please zoom in as much as possible while keeping the whole garment still visible. (hotkey “2” & “8”)
→ use these settings in the Image/Video Properties for rendering out the frontal and back view of the garment named accordingly (_frontal & _back):

3D Output

1. Check fit on avatar and simulate on avatar

→ position the pattern pieces around the shape of the avatar
→ simulate and check the result for self-intersections or intersections with other patterns like buttons and trims or hard edges and fix them with new iterations of simulation using the appropriate toolset (mesh tool (lasso, box, brush), pins, tack, freeze, solidify, ... etc) until everything looks sound.

2. Optimize Mesh

→ adjust the Particle Distance, Collision Thickness and Skin Offset to achieve a lower, but still good looking mesh density

3. Simulate on avatar and check mesh quality

→ simulate and check the result for self-intersections or intersections with other patterns like buttons and trims or hard edges and fix them with new iterations of simulation using the appropriate toolset (mesh tool (lasso, box, brush), pins, tack, move tool, etc.) until everything looks sound.

If necessary, modify the adjustments done in step 2, simulate and check again and repeat this process until you are satisfied with the results.

5. Nest UV + Export UVs + Save .zprj

→ the pattern pieces in the UV should be nested in a space-saving and sensible manner in only 1 tile with a bleeding of 64px. Make sure there are no overlaps.

→ bake the textures with the following settings using the Bake Textures Functionality of the UV Editor:

Troubleshooting

If this description is insufficient, you need further explanation or you run into problems, please reach out to your contact at Reactive Reality.