Piotr Janowski: I'd recommend checking out this video tutorial for steps on how to link your textures using C4D + Octane: https://www.youtube.com/watch?v=l19hLJ79v0g&t=56s

If you're still having trouble, send us a video of the issue you're running into and we'll do our best to help troubleshoot.

Damon Milstead: Something to try troubleshooting when relinking textures is to make sure your c4d file and the Tex folder reside in the same root folder. Let me know if that helps!

Shelby: the c4d file in the folder from KB3D? It always is.

I always unzip to the textures into the new 4K folder that has need set up recently.

Damon Milstead: Would you mind uploading a screenshot of your file structure?

Shelby:

THe biggest issue is when you copy and paste any KB3D object into another scene, all of the material links break

Damon Milstead: Apologies for not addressing this earlier, but this issue you're running into is something our Engineering team is working on finding a solution for. With our Kits, texture paths in C4D + Octane behave differently from all other render engines we support, and the Tex/4k

have to appear in your project folder or the textures will be missing on render.

Make sure you have the Tex folder and within that, the 4k folder, like the original scene. You'll also want to copy the textures used for the asset you're using into the 4k folder. It's not ideal, but it's something we're working on smoothing out. Let me know if you're still having issues with it.

Shelby: it doesn't matter which kit i use. I've been re-downloading the 5.0 kits and setting them up as instructed but i still have to relink everything if i copy assets into new file.

Damon Milstead: Got it. Appreciate the continued insight! We're going to try and recreate the issue you're running into on our end and will follow up with you here. Thanks for being patience with this one.

Shelby: copy that

Let me know if there's anything else i can do to help.

Damon Milstead: Wanted to send this your way in case you haven't seen it. Check out this tutorial for linking textures with C4d + Octane. https://youtu.be/l19hLJ79v0g?t=56

If covers a helpful folder structure tip that you might be useful.

Shelby: This video is the importing method that everyone is already using and it doesn't work. It recreates the same problem we're already seeing. The textures are still breaking.

Jazmin Truesdale: Thanks for flagging! We're working on putting together some updated content to help make this issue easier to navigate. When we process our Kits, we intentionally process them to link up automatically, and C4D + Octane is a bit of a special case compared to the rest of our supported software—which we know is causing some frustration. Our Engineering team is working on a long-term fix to make this easier.

We've tested this out and textures do work successfully with C4D + Octane, you just have to make sure the file path is set up correctly and that the structure stays the same. Within the unzipped Kit file, you'll need to copy and paste all your textures (2k or 4k) into the 4k folder that lives inside the Tex folder (see attached image). You'll want to make sure that those files always stick together in that structure, otherwise, your textures may break. In other words, if you keep the textures in the 4k folder and the file lives next to the Tex folder, your textures should link up automatically and you shouldn't experience any texture linking issues.

Let me know if that helps!

Shelby: I'm experiencing this same issue for several of the recent kits. I can get the textures linked up for the master kitbash scene by structuring the file path like you say, but as soon as I actually want to use one of the models and copy/paste it into a different project, all the textures unlink, which makes the models functionally unusable since I'd need to do that every time I want one of the models. I was able to get this working in the past, has something changed with the new kits?

Tom Coben: With C4D + Octane, that file structure has to remain as is and copy/pasting will, as you experienced, unlink those textures. This is only specific to C4D + Octane so you won't run into this with other supported renderers. We're working on figuring out an engineering solution to improve this process in our next big update.

Shelby: Any update on this?