Cargo Feedback

Many of us VFX guys use Linux. Please make a Linux version! Bridge has had a Linux version since the beginning!

Cargo has become unusable after the latest update. It is broken in every version of c4d I have installed. Very frustrating to be paying for this.

Is there a setting in Cargo when importing assets into UE it will categorize by kit? It looks like meshes not a blueprint goes into the geometry folder. This folder will get cluttered quickly. Hopefully I'm missing a setting somewhere,

It's not difficult to just click over and open Cargo but it would be a nice if I were already working in Unreal and wanted to jump over to Cargo and have it load or swap to ir from within Unreal. Just would be a tad more convenient for workflow and feel more integrated.

I cannot login into cargo pro. The button turns grey.

Hello, Great to see Houdini supported by Cargo. At this time when you import an asset this is created under a geo node with the name of the kit, so if you import different assets from the same kit they will live under the same geo node, and this can become a mess very quickly. Is possibile to add an option to import with the name of the specific asset instead of the kit? Would be also great having an attribute name for each parts of an asset because at the moment is very time consuming manually assign this basic attribute. Please note that shaders don't work with karma XPU and there are also some issue with glass shader karma CPU.. Thank you very much Mike

A 3D tumble view like you can do with FBX would be nice when clicking on an asset (or even locked ones). The Cargo layout is great and better than viewing with Unreal for sure but this additional function would make it even better.

Hi, I have an 101 error when i try to import asset from cargo, and at the same time i have a python error on blender. I tried everything, nothing works, no matter the version (3.5 - 3.6.4 - 3.6.5). It's not the first time that happen. This error message appears in blender : Python : Traceback (most recent call last): File "C:\Users\Tour\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\Kitbash3D_Cargo\cargo.py", line 807, in modal converter = DeserializedDataConverter(deserialized_data) File "C:\Users\Tour\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\Kitbash3D_Cargo\cargo.py", line 164, in __init__ self._build_materials() File "C:\Users\Tour\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\Kitbash3D_Cargo\cargo.py", line 179, in _build_materials mat_output = new_mat.node_tree.nodes["Material Output"] KeyError: 'bpy_prop_collection[key]: key "Material Output" not found'

I'm running Win 10 – unreal 5.3 – 3dsmax 2024. – nitrous direct 3d 11 – nvidia gf rtx 3090 Following datasmith docs. No matter the texture size when Crago is setup to integrate with 3dsmax, textures do not show up in the viewport. Regardless of settings, however, they render ok.

I seem to always run into an issue with all kits where I need to re-apply every single normal map with a different setting. I'm using 3D Studio Max with the Arnold renderer, and out of the box the normals don't render properly. When using normals maps in 3D Studio Max I usually always change the "Gamma" settings for the normals maps into "Override 1,0", which makes the normal maps render properly in Max. Right now I am adding every single normal map manually, using this setting, which takes ages and I was wondering if you've perhaps got a better solution for this issue?