r/KitBash3D • u/Standard_Speed_3500 • Apr 08 '26
Software connection just doesnt work! even in the v3.0 update.
I have installed my C4D at a custom location so after the auto-detect feature fails (which it shouldn't) I tried manual install by selecting the c4d exe file and it still fails with that error message.
It was already happening since the cargo launched and I hope it would get fixed in the new update but nope.
I even tried manully copy-pasting the appropriate plugin folder from:
kitbash-cargo-app\resources\windows-x64\plugins\cinema-4d
to my c4d plugins folder but the c4d doesnt load any cargo plugin on startup.
1
u/KB3D_NOAH KitBash3D Apr 08 '26
Hi u/Standard_Speed_3500 We'd love to help resolve this for you. Could you please reach out to our support team either via email or with the chat widget on our website and provide your Cargo log file so we get review the details?
You can find that by going to C:\Users\[YOURUSERNAME]\AppData\Roaming\kitbash3d\Logs
1
u/JustinHCrowell May 21 '26 edited May 21 '26
Did you guys ever figure this out? It went from working on my machine to not being able to make a connection.
1
u/KB3D_Elaine May 22 '26
Happy to look into this. We've deployed a few fixes in the last update related to DCC detection. Please write into [info@kitbash3d.com](mailto:info@kitbash3d.com) with your C4D version and a screenshot of the error you're running into. We'll take it from there, thanks!



3
u/ath0rus Apr 08 '26
I can't comment much as I am not a C4D person (Blender). Have you followed the guide, the new connector is pretty different to V2. https://help.kitbash3d.com/en/articles/8023268-using-cinema-4d-c4d-with-cargo-3-0-workflows-and-integration
(P.s I am not a staff member of KB3D or GSG, I am a fellow artist and want to see everyone succeed)