Skip to main content
All CollectionsCargo by KitBash3DErrors & Troubleshooting
Error 101: Could not locate your 3D Software
Error 101: Could not locate your 3D Software
Maxx Burman avatar
Written by Maxx Burman
Updated over a month ago

What it means.

Cargo requires a connection to your 3D software in order to Install Plugins (see Basic Software Setup) and to Import Assets (see Download / Import).

Error 101 occurs when Cargo cannot find a selected 3D software installed on your computer.

As a first step, please ensure the 3D software you're using is supported by Cargo by reviewing this guide: Cargo Supported 3D Software and Render Engines


How to fix it

If you're receiving this message during Import:

Step 1:

Go to your Account Settings and make sure you have the correct 3D Software and Version number set as your target software.

Step 2:

Sign out and completely exit Cargo then restart your computer.

Step 3:

  1. Keeping your 3D software shut down, log back into Cargo and navigate to Account > Software Settings > Add New Software.

  2. Select your software and version from the dropdown menus

  3. Allow Cargo to install the plugin into your 3D software

  4. Open your 3D software and activate the Cargo plugin in all locations applicable to your 3D software.
    Software such as Unreal and Blender have multiple checkpoints where the Cargo plugin must be activated/enabled in order to successfully import assets.

    1. See our collection of guides for each software Cargo supports: https://help.kitbash3d.com/en/collections/3931321-connecting-your-3d-software

Step 4: If you're still experiencing errors when importing assets after taking the steps above, verify that the download location has proper permissions. In order for Cargo to import assets into your 3D software, the proper permissions must be set in your download folder.

How to verify download location permissions

  1. In the Windows File Explorer, navigate to your chosen download location for Cargo.
    If you don't remember, or would like to change the download location, you can do so by logging into Cargo and clicking Account and viewing Software Settings.

  2. Open Properties: Right-click on the folder and select "Properties" from the context menu.

  3. Access the Security Tab: In the Properties window, go to the "Security" tab. This tab will show you the list of user accounts and groups that have permissions for the folder.

  4. Check Permissions:

    • Look at the list under "Group or user names:" to see which users and groups have access to the folder.

    • Click on a user or group to see the specific permissions granted to them in the box below labeled "Permissions for [User/Group]". This box shows permissions like Read, Write, Modify, etc.

  5. Modify Permissions (if necessary):

    • If you need to change permissions, you can click the "Edit" button. This will open another window where you can modify permissions.

    • Select the user or group whose permissions you want to change.

    • Check or uncheck the boxes under "Allow" or "Deny" to set the desired permissions.

    • Click "Apply" and then "OK" to save the changes.

  6. Check Cargo Permissions: Ensure that the user account under which Cargo runs is listed and has appropriate permissions.

  7. Apply Changes and Test: After setting the permissions, it's a good idea to test access by downloading and importing an asset from Cargo to see if it can now read from or write to the folder as expected.

If you're receiving this message during Software Setup:

Step 1: Check which 3D software, version and render engine you're using.

Step 2: Review the Supported 3D Software / Render Engine guide to make sure Cargo supports your current version.

Step 3: If your software version and render engine is supported, and you cannot connect to it during Basic setup, continue by using Advanced Software Setup.
Always ensure your 3D software is completely shut down before starting software setup.


If you are still having issues after trying these steps, contact us at info@kitbash3d.com and we’ll get you up and running in no time.

Did this answer your question?