Blender project dependencies
By Superluminal Engineering
Every linked library, texture, UDIM, cache, and font ships with the job. The file check names missing inputs before you pay for a node.
Published 2026-07-29 · Updated 2026-08-06
- File-check timing
- Before upload
- Supported file patterns
- Linked libraries, UDIMs, sequences, fonts, caches, HDRIs
- Upload modes
- ZIP or PROJECT
Missing inputs are named before the job spends paid node time.
The file check follows external files referenced by Blender.
ZIP creates one archive. PROJECT preserves a chosen project root.
Superluminal traces the full dependency graph of a Blender project before upload. Linked libraries, textures, UDIMs, image sequences, caches, fonts, HDRIs, and IES profiles travel with the job.
That trace gave the most complete dependency coverage of any client we tested in our 2026 render farm benchmark. Every missing or unreadable file is named on screen before the job spends paid node time. Nothing is quietly dropped.
The trace follows every supported reference
The add-on reads the project you already have open, so it sees the same paths Blender sees. It also follows references inside supported linked .blend files.
| Input | What Superluminal includes |
|---|---|
| Linked library | Files referenced by supported linked .blend files |
| UDIM set or image sequence | All discovered tiles or sequence frames |
| Video Sequence Editor strip | The referenced video or image files |
| IES or external OSL path | The referenced file |
| Cache directory | Files from supported cache folders |
| Packed data | Data stored inside the .blend file |
The check names every problem path
| Status | Meaning | Response |
|---|---|---|
| Missing | The path does not resolve to a file | Restore, relink, or remove the reference. |
| Unreadable | The file check cannot read the file | Check access rights, cloud placeholders, mounts, and file health. |
| Absolute path outside the root | The file uses a fixed location beyond the selected root | Relink it under the root or use ZIP. |
| Cross-drive | The file is on another drive from the project root | Move it, choose another root, or use ZIP. |
| Packed | Blender stores the data in the .blend | Confirm that the packed copy is current. |
A missing file changes the render silently
Blender renders on without the file, and the defect appears only in the finished frame.
| External input | Result when it is absent |
|---|---|
| Texture, UDIM set, or HDRI | A material turns pink, loses detail, or receives different light. |
Linked .blend library | Objects, collections, materials, or overrides disappear. |
| Alembic, volume, or simulation cache | Motion freezes, geometry changes, or a simulation resets. |
| Font | Text changes shape or line breaks. |
| Image sequence or video strip | A shot freezes, skips media, or has an empty source. |
| IES profile or external OSL script | A light pattern or shader changes. |
Blender resolves each relative path from its .blend
A relative Blender path starts with // and is relative to the .blend that contains it. A linked library can therefore use a different base folder from the main scene. The trace resolves each reference from its own file, the same way Blender does.
Image sequences and caches can fail late in an animation. Test frames from different parts of the range.
Pack with ZIP or PROJECT
ZIP uploads the saved .blend file and all discovered files with every submission.
PROJECT uploads the full project once. Later submissions upload only new or changed files under the project root.
PROJECT requires one root folder. The panel blocks submission and names the problem when a path falls outside it.
| Use ZIP when | Use PROJECT when |
|---|---|
| You are sending the first remote test. | Related shots share one production root. |
| Assets span folders or drives. | Later submissions reuse large assets. |
| You need a fallback after a PROJECT warning. | Project paths stay under one common root. |
If you are unsure, start with ZIP. The upload mode guide shows both controls.
Files that the trace cannot see
The trace cannot see paths that scripts or add-ons create during rendering. Put those files inside the project, then inspect the frame log and downloaded output file.
The add-ons guide covers licenses, compiled components, and online services.
The job leaves with everything it needs
The packed job carries every traced file, so a render node opens the project exactly as your workstation does. Wrong-texture surprises stay local, where the check already named them.
Submit one short test range first and inspect the downloaded frames. The job submission guide shows the packaging controls in place.