Hi Dr. Sassi,
Yeah, any other file format seems to crash it in 2026. As for RS redshift, it seems to work fine in the nodes. It's mostly with the Native C4D shader where the problem is.
Though, I really appreciate the effort! You are always helpful!
All the best,
Thats very interesting. I'm on a PC. I opened up the Photoshop file, and it's already in RGB mode. I thought maybe it got messed up when using layer comps to files export. So I export manually, and it still crashes on me.
Is there a chance my C4D is trying to read it wrong?
And I just got this from Tech support
"Looks like this is actually a bug with the hair system. I haven't found a workaround for it in 2026.1, so your best bet for now is probably to use an older version until a fix can be implemented for this."
All the best,
Hey Dr. Sassi,
Thanks for replying. I never had an issue before, but now it's been such a headache.
I had looked it up before asking the forum and was given a checklist.
I submitted a ticket to the support center, and I hope they can help.
https://drive.google.com/file/d/1vmwK7JKm_yeZzIv46nfSv5Lvc0D1-VTe/view?usp=sharing
All the best,
I've been using C4D hair and it works just fine, but every time I open up the Native C4D hair material to add an image, it crashes. Idk what the problem is and how to fix this, and even after updating to 2026.1.1, it still crashes. Any help will be greatful.
Also, are we ever going to get a C4D hair update? it could really use a boost.
@Dr-Sassi Ah, I see that now. Thank you for your explanation, and I will keep this in mind for future rigs that require mocap animation.
@Fettness Did you find a workaround for this? I'm trying to do the same, but I'm running into similar issues. Every example/tutorial I have seen so far is using a Mixamo rig. Even when using the mocap data from the content browser.
I find it absurd that this has not been streamlined yet.