Redshift 3.6 + Cargo support
A
Angus Turner
Any update on this? Thanks
S
Sam Hodgkiss
Morning, I have read the other comments and I am having the same issues. I followed the advice from another comment about downgrading to Redshift 3.5 and still no luck when importing Materials using both 'Redshift Legacy' and 'Redshift Standard Material'
C4D: 2024.4.0
Redshift: 3.5.24
Cargo: 1.1.7
Toàn Hậu Trần
Sam Hodgkiss Use the C4D 2023 version it works well
Toàn Hậu Trần
Can you tell me why Cinema 4D 2023 with Redshift 3.6 works, but Cinema 4D 2024.4 doesn't work?
Elaine Deveney
Merged in a post:
Redshift Materials fail in C4D
T
Thomas DeCarlo
I upgraded from Cargo 1.1.3 to 1.1.6 and now "Redshift standard" and "Redshift legacy" materials do not import into C4D with the models. Only a single material object gets created (with no texture maps in it). I can confirm that "native" materials import with the model just fine. I have recently updated C4D - probably more than once - since my last Cargo import.
Elaine Deveney
Merged in a post:
Materials not importing
l
l
Materials are not imported. Model gets imported in with a single default Material
Elaine Deveney
Hi l. Our team is working on an update in order for Cargo to support Redshift 3.6. Please use an earlier version of Redshift with C4D 2024.4 in order to successfully import materials with Redshift.
D
David Angelini
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.
Elaine Deveney
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.
s
sharon palkowetz
Elaine Deveney
Is that on the map for a soon update? I use Cargo now in production, and am dismayed to learn that it's not updated for the latest redshift. Thanks a ton!
Sharon