Have you tried downloading the models as opposed to using Cargo? I recently purchased Wreckage and download the C4D Redshift models/texture and upon loading into R2024.4 using Redshift 3.6, you will get this message shown below.

So the latest Kitbash3D models will still work in the latest version of RS and C4D if they are downloaded as external C4D files (xxx.c4d file with tex directory) and then opened natively by C4D. They will NOT work if imported directly into C4D with Cargo.

With that said: Given that Cargo's import capability is renderer dependent, that is a great deal of work to maintain Cargo across all formats and render engines. So, it can impact production if NOT kept current. Therefore, for those who use Cargo, then you need two options "IMPORT" and "DOWNLOAD". Ideally, there should be some check on whether or not Cargo is supporting the latest render engine in the host application and if it is NOT supported, then only give the "DOWNLOAD" option.

Until that change is made and for those who don't subscribe to Cargo but rather purchase the kits individually and download them, then consider this when Cargo is NOT up to date and importing no longer works:

In the case of Wreckage, any thought to NOT providing just one massive 1.4 Gb C4D file that has ALL the Kitbash3D models loaded into it but rather one ZIP file that has a series of individual C4D files for each model similar to how Cargo works today?

Loading a 1.4Gb file and waiting for C4D to convert ALL the materials on ALL the models to the current render engine does take a bit of time.

Hi Thomas DeCarlo , I appreciate the detail you've shared in your message. I noticed that you listed Redshift 3.6 as your Render Engine & version. Cargo doesn't yet support Redshift 3.6 so you'll have to use Redshift 3.5 with C4D when using Cargo.