Task Relay

Task Relay guides · Research / Model / Present

Keep Blender assets and textures together

Prepare a portable candidate from selected mesh assets and image files, then check that it reopens after relocation.

The problem

How to move a Blender project between computers without losing its textures or having to locate missing files again? Keep the selected assets and supported image dependencies together, then check that the candidate reopens after relocation.

Choose a small, supported asset set

You provide: a selected target .blend, a source .blend library with the exact mesh names to append, and the required PNG/JPEG images. Identify the destination collection and image-node bindings. Keep source URLs and licenses with supplied assets.

You get: a candidate .blend, preview, retained source bundle, manifest and relocation/reopen checks. Use an installed Blender host and a worker to prepare and review the import choices.

Give Relay this request

Inspect my selected target .blend and source .blend library.
Prepare an asset import manifest to append [mesh names] into [collection]
and bind the supplied [PNG/JPEG files] to [existing image nodes].
Preserve source provenance and relative file layout. Report missing files
or unsupported dependencies before execution; do not substitute assets.
Stop for review of the exact manifest and selected source files.
Then propose the Blender import/packing operation. Return a candidate
.blend, preview and source bundle with relocation/reopen checks.

Check the handoff

  1. Read the scene inventory and confirm the intended mesh and material names.
  2. Review every selected library and image in the manifest. Missing files must be supplied before packing.
  3. Approve the import operation. Relay appends the selected meshes, packs supported images and checks the candidate after relocation.
  4. Open the candidate and inspect the preview before choosing it for handoff.

This is a selected-asset import and packing workflow. It does not reconstruct lost image bytes or collect arbitrary dependencies from your computer. Linked libraries, simulations, add-ons, HDR/EXR environments and other unsupported dependencies need separate handling. The current packing route covers PNG/JPEG images and explicit mesh imports.

For a self-contained model that needs a dimension change instead, Relay also has a separate inspect → exact-script review → Blender edit route. New primitive or numeric-mesh study models have their own creation operations. Keep those changes separate from the asset handoff.

Capability check: blender.inspect and blender.import_asset are present in the audited app bundle. See the operation documentation for implementation scope and recorded checks. This article is a workflow recipe; its exact prompt has not been qualified through a complete live Relay run. Forum reports establish a problem, not measured time savings.