Find your tools again, then check what they produce.

Describe a setup that can be verified

Start from the result: a product image with its passes, a poster search or an animation to assemble. Note the main software, the engine, the version used and the format you need to deliver. Add the operations that happen after rendering: decoding, denoising, upscaling, compositing or encoding. A tool can succeed at generation and fail at the next step.

The configurator lets you specify an Ubuntu, PyTorch, Blender or custom setup. Back that choice with a short spec sheet. Avoid "latest version" if you are resuming an existing project: that phrase will change meaning. Write down the exact known version and mark the other items "to be confirmed." You choose your software and processes; their licenses, dependencies and requirements remain to be examined.

Prepare the Blender spec sheet with the scene

Note the Blender version, the render engine, the essential extensions and the scene settings. In Cycles, choosing GPU rendering involves device preferences and project settings. Check hardware support against the planned version and driver; the card name alone does not describe that compatibility.

Also gather textures, linked libraries, fonts and caches. Opening without any error message does not guarantee that every image in the animation finds its resources. The 3D workshop sets up a representative render case; the Pli folder details the transfer. Finally, keep the settings needed to get consistent colors back in the next application.

Set up ComfyUI beyond the JSON file

Keep the ComfyUI revision, that of its interface when you know it, the JSON workflow and the model references. For each weight, note the exact name, the source, the version or revision and its expected location. A hash helps tell apart two files renamed identically. The graph describes the steps; it does not carry the weights for them.

Separate core nodes from extensions. An extension can bring code and Python dependencies: those must belong to the environment that launches ComfyUI. After an installation, review load errors before starting a batch. The Ceramic folder offers an example with no custom nodes, along with a manifest and rebuild instructions; it does not guarantee that another graph will work.

Identify the environment that actually runs the work

Note the system, Python, PyTorch and the compute variant used. ComfyUI runs in a separate Python environment, so its portable install may use a different interpreter than a terminal opened alongside it. If a library appears to be present but remains missing, check this discrepancy first before reinstalling the package over and over.

A CUDA chain does not transpose automatically to ROCm. Examine the requirements of your extensions and operations, not just those of the main software. To compare configurations from the catalog, keep the nominal memory per card separate from the observed need and from the CPU, RAM or storage resources to be specified. Do not replace an unknown reference with a value assumed to be "standard".

Building a test that covers the entire chain

Choose a short but representative input: a framing that contains the difficult material, a workflow that includes its final decoding, or a few images crossing a scene change. Open the inputs, verify the device actually being used, run the processing, save the output and open it in the software that will receive the result. Note the name of the resulting file, not just "OK".

A low-resolution output validates part of the path. Before production, also test the dimensions, steps and final formats that could change the load. Record the exact error, the step concerned and the change you tried. If you change a version or a model, repeat this check: the success of the old combination does not validate the new one.

Hypothetical example: resuming a bottle campaign

Let's imagine a campaign comprising a Blender image and three light searches in ComfyUI. The brief calls for Blender 4.5.x for the Pli generator and the references listed in the Céramique manifest. These versions are documented starting points, not software claimed to be installed. The two recipes remain separate: an image from Blender does not become a ComfyUI generation just by copying the folder.

The team plans two chain checks: a saved Blender image and a full run of Céramique producing its three outputs. That represents four expected images, with no duration forecast. It then plans to open a copy of each output in its layout tool. In this example, the results remain to be filled in after running; no box is filled in advance.

The evidence already available for Pli and Céramique concerns the files and structure. No Blender render or ComfyUI generation has been produced for these packs. Their value here is to make the dependencies and the check concrete, with a known limitation.

Diagnose before changing the whole configuration

Handle one failure at a time and keep the starting brief. If you change model, software, driver and resolution simultaneously, a final success no longer explains what solved the problem. Keep the initial message, then compare a single relevant change. An update may be necessary; it must form a new identifiable version of your environment.

The seed of a generation is worth keeping, but it does not guarantee identical results across versions and platforms. For a creative resumption, define what you require: a strictly identical file, a comparable composition or an accepted look. These criteria do not call for the same checks.

Keeping a usable base after the first session

File the environment sheet next to the project, with a date, the result of the check and the elements that are still uncertain. Keep an independent copy of the authorized files, along with their licenses or references. For an extension or a model, documenting the source does not mean you may redistribute its content.

Reserve the preparation and this initial reception within your 3-, 7- or 30-day window, then keep time for recovery. The project notebook stores your notes and settings; it does not replace an archive of scenes and images. Before finishing, follow the export check to also retrieve the creations produced with this environment.