USD Integration: High-performance data handling for massive scenes.

Source/Instance Hierarchy: Professional-grade organization that separates master data from viewport instances.

Memory Efficiency: Drastically reduced RAM usage by referencing geometry rather than duplicating it.

Global Propagated Edits: Edit a "Source" asset once to update every instance in your scene instantly.

Native Asset Browser Support: Drag-and-drop your Cargo library directly from Blender’s built-in editors.

Import as Real (New): Toggle between optimized Collection Instances and fully editable meshes while maintaining lightweight mesh data instancing.

The Architecture: Blender references an external structural collection data block and displays it as an empty object capsule in your viewport.

The Benefit: Incredible performance and overhead safety. This is ideal for sprawling set-dressing, massive environment creation, and repetitive layout blocking.

The Friction Point: Because the object capsule is an empty reference container, you cannot jump into Edit Mode (Tab) to manipulate individual faces, vertices, or edge loops right out of the gate.

How to Enable:

The Performance Matrix (MeshData Instancing): Unlike breaking collection instances manually via Blender's standard operations, Cargo's automated engine ensures that underlying structural data sharing is preserved.

"I enabled 'Import as Real' but my scene file size skyrocketed"

"I cannot find the Cargo Settings panel inside Blender."

In the lower-left corner of Cargo, click the Connector icon 🔗 or click the gear ⚙️ icon for full Software Settings page. You can remove and connect DCCs from either section.

Review your connected software

Ensure Blender is not running in the background.

In Cargo, click Connect New Software ⟶ Blender ⟶ Your supported version.

Note: Choose "Select Manually" only if Cargo can't auto-locate your Blender .exe.
​

Open Blender ⟶ Edit > Preferences > Add-ons > Search "KitBash."

Check the box for KitBash3D Cargo Plugin.

Visual Note: It may take ~20 seconds to activate; save preferences once done.
​

Critical Step: You must save your .blend file.

Verify: The chain link icon in Cargo will turn Glowing Green.

Skip Existing Assets/Materials
Keep these checked. Cargo 3 utilizes an advanced referencing system.
If you attempt to re-import an asset or material that already exists in your scene, Cargo will simply add a new instance rather than duplicating the heavy geometry or texture data in your RAM.

Import as Real (New Feature)
By default, multi-object assets import as highly optimized Collection Instances. If you know your pipeline requires immediate kitbashing, structural modifications, or mesh alterations upon asset entry, use this setting.

Import Path
Point this to your designated Cargo download folder. You only need to use this path setting if you are performing an offline, manual import of specific USD variants (see the "Manual USD Import" section below).

Inspector Download: Select your asset > Choose 2K PNG (or preferred variant) > Click Download > Import.

Visual Check: The asset appears in the viewport and creates a specialized hierarchy in your Outliner.

Action: In Cargo, navigate to the Material Kits (e.g., Concrete Pavers).

Step: Select your material, choose your resolution, and click Download, then Send.

Visual: Switch to Blender. Note that no new object appears in the viewport; the material has been added to Blender’s internal Material Library.

Step: Select the object/surface in your Blender scene you wish to texture.

Action: In the Material Properties tab (or via your preferred material add-on), search for the Cargo material name and click Apply.

Result: The material is now mapped to your object with all PBR maps (Albedo, Normal, Roughness, etc.) automatically connected.

You must have previously downloaded the asset through Cargo.

The asset must be Version 7.0 or higher.

Note: Older assets (pre-7.0) use an outdated USD schema and will not work with the manual importer; these must be re-downloaded to update them to the 7.0 standard.

Action: In the Blender N-Panel, locate the Manual Import section.

Step 1 (Set Path): Point the "Import Path" to your designated Cargo Kits folder.

Step 2 (Select Variant): Ensure the Texture Variant (e.g., 2K PNG) in the Blender panel matches the specific version you downloaded in Cargo. If they don't match, the model will import without textures.

Step 3 (Select File): Navigate to the kit folder $\rightarrow$ 7.0 $\rightarrow$ Models -> [Asset Name].

Step 4 (The Root File): Select the main USD file named after the asset (e.g., SniperTower.usd).

Visual Note: You will see other files like Geo, Material, and Payload. Always select the main Asset Name file, as it acts as the "container" that calls the geometry and materials together.

Action: Click Import USD.

Portability: If you need to "collect all and save" or send your project to a render farm/colleague, the textures are already linked locally to that specific scene.

Speed: Your DCC (Blender, Maya, etc.) accesses the textures sitting right next to the file, which is industry-standard practice for avoiding broken paths.

Organization: You can see exactly which textures are active in your specific project without digging through the entire KitBash3D library.

7.0/ Folder: This is the root for all Cargo 3 assets.

Models/: Contains the USD files.

Materials/: Contains the USD shading definitions.

Textures/: Contains your downloaded variants (1K, 2K, 4K).

All imported Cargo assets are automatically marked as Assets in Blender.

Usage: Open the Asset Browser editor in Blender. You can now drag and drop your Cargo library directly into the scene as instances, making set dressing much faster.

Clean Node Graphs: Instead of a "spaghetti" mess of nodes, Cargo imports a collapsed, clean node setup.

Customizing the Look:

Speed: Because the materials are global to the scene, you can apply the same Cargo material to multiple objects instantly without re-downloading.

Collection Instances (Default): Highly optimized for layout; hard to edit instantly.

Import as Real (New Feature): Fully editable out-of-the-gate; retains Mesh Data instancing.

The Architecture: Blender references an external structural collection data block and displays it as an empty object capsule in your viewport.

The Benefit: Incredible performance and overhead safety. This is ideal for sprawling set-dressing, massive environment creation, and repetitive layout blocking.

The Friction Point: Because the object capsule is an empty reference container, you cannot jump into Edit Mode (Tab) to manipulate individual faces, vertices, or edge loops right out of the gate.

The Performance Matrix (Mesh Data Instancing): Unlike breaking collection instances manually via Blender's standard operations, Cargo's automated engine ensures that underlying structural data sharing is preserved.

If you select a repeated asset (like an architectural barrel set) and enter Edit Mode, altering the edge loop of one mesh will still propagate globally to the other matching assets in the scene.

Blender's object data block counts this safely as synchronized duplicate instances, maintaining lightweight file storage metrics and stable RAM performance overhead.

Shortcut Method: Use Ctrl + A > Instance Empty to Collection. This allows you to break up an instance for localized editing.

Workflow Tip: Edits made to a source asset will propagate to every instance in your scene that uses that asset (e.g., editing one grenade in an assembly updates all grenades in the scene).

Use Alt + D to create a new instance of an assembly. This is high-efficiency duplication that keeps your scene "light" while you set-dress.

How it Works: This breaks apart the specific grouping of an assembly into its individual instance objects.

Benefit: You can now move, rotate, or delete specific parts of the assembly (like a single barrel or crate) without making the geometry unique. It remains an instance, keeping memory usage low.

When to use: Only at the end of your project for final, unique touches. If you know you want to edit kitbash pieces from the start, use Cargo's "Import as Real" checkbox during import to save memory instead of relying on Blender's native post-import tool.

Action: Search for "Make Instances Real" (Ctrl + A menu).

Result: This converts every instance into a unique, editable object.

The "Copy Path" Trick: Download multiple HDRIs in Cargo. You can cycle through them by simply copying the path of a new sky and pasting it into the Environment Texture node in Blender. This allows you to test "Dusk" vs. "Midday" lighting in seconds.

Scale & Transformation: Use the Mapping node to adjust the Scale and Location of your Gobo. This allows you to "resize" window shadows or position a palm tree shadow exactly where it’s needed.

Invert & Multiply: You can add an Invert Color node to switch between light/shadow dominance or a Math (Multiply) node to control the intensity of the light pattern.

Softness: Adjust the Radius of the Spotlight in the Light Properties tab. A larger radius will blur the Gobo shadows (simulating a soft light source), while a small radius will make the pattern sharp and crisp.

Problem: Cargo shows a "Not Connected" status even though Blender is open.

Fix: You must click the "Connect" button in the Blender N-panel (KitBash3D tab) after Cargo is already running. This initializes the bridge.

Problem: You can't find "Cargo" in Blender’s Add-on list.

Check: Ensure you used the Software Settings in Cargo to "Install Connector" first.

Fix: If it still won't appear, use the Advanced Setup in Cargo to manually point to your blender.exe.

Problem: Blender hangs or shows a "missing plugins" warning when enabling the add-on for the first time.

Fix: This is normal for the initial activation. Wait approximately 20 seconds for the process to complete, then Save Preferences.

Problem: "Send Failed" error when trying to import an asset.

Reason: Cargo 3 creates a local texture folder next to your scene. If the .blend file isn't saved, Cargo has no directory to target.

Fix: Save your Blender file to a permanent location and click Retry in Cargo.

Problem: Asset imports with missing (pink) textures.

Check: The Texture Variant (e.g., 2K PNG) in the Blender N-panel must match the exact variant you downloaded in Cargo.

Fix: Match the settings and re-import the Root USD file.

Problem: Manual import fails or the folder structure looks "old."

Fix: Cargo 3 requires USD Version 7.0. Assets downloaded in previous versions of Cargo must be re-downloaded to update their file schema to the new standard.

Problem: Model is missing geometry or shading.

Fix: Always select the Root USD (e.g., Chair.usd) in the Models folder. Do not import Geo.usd, Material.usd, or Payload.usd directly; these are sub-components called by the Root file.

Problem: Material appears in the list but not on the object.

Fix: Materials import directly to the scene data. You must manually apply the material to your mesh from the Material Properties tab or use the search function in the Shader Editor.

Fix: Ensure you are using the Cycles render engine. Check that your mesh has sufficient geometry (subdivisions) and that the Displacement Scale in the Cargo node graph is set above 0.

Cause: If you manually duplicate these objects around your scene afterward using standard duplicate (Shift + D), you create unique users.

Fix: To populate your scene further while maintaining performance, duplicate using Linked Duplicates (Alt + D). This preserves Cargo’s underlying memory-saving framework.

Fix: Ensure you have the N-panel visible by pressing N on your keyboard while focusing inside the 3D Viewport. If the tab is missing, re-verify that the addon is enabled under Edit > Preferences > Add-ons > Cargo Importer.

Problem: You moved your .blend file and now all Cargo assets are pink.

Reason: Cargo 3 uses relative paths to the local texture folder.

Fix: Always move the entire project folder (the .blend file AND its accompanying texture/USD folders) together. If paths are broken, use Blender’s File > External Data > Find Missing Files.

Cause: The Environment Texture node is looking for a file that isn't there or hasn't been selected yet.

Fix: Click "Open" on the node and ensure you have pasted the path to a valid .exr or .hdr file from Cargo.

Cause: You may be looking at the viewport in "Material Preview" mode rather than "Rendered" mode.

Fix: Download the 4K variant in Cargo for crisp background details and ensure your viewport shading is set to Rendered (Cycles/Eevee).

Tip: If you have a manual Sun Light in your scene, use the Mapping node (Z Rotation) to align the sun in the HDRI with your 3D light source for consistent shadows.

Cause: The Texture Coordinate is likely set to Generated or UV.

Fix: Connect the Normal output of the Texture Coordinate node to the Vector input of your Mapping node. This projects the image along the light's beam.

Fix: Increase the Radius of your light. Also, ensure your Spotlight's Power is high enough (e.g., 1000W+) to compete with other lights in your scene.

Fix: Use the Mapping node (Z Rotation) to spin the pattern until it aligns with your windows or floor.