Cindigo 3.0.15

[fused]

Found the bug that was crashing C4D on exit.

Will release new mac builds soon, if nothing gets in the way.

[ritter]

Sounds good!

[fused]

Added 3.0.15 mac builds. Please let me know if something doesn't work.

[zeitmeister]

Yeah, thank you very much!
Testing ...

[forgeflow]

exit C4D? When does that happen?
I'm curious if it still displays the bug that crops up sometimes where you add a material to an established scene, suddenly Indigo says that "so-and-so material doesn't exist" and you have to try to re-arrange the material library till it works again. I know I'm not describing this bug very well, but I can't seem to come up with a guaranteed way to make it happen to report it properly.

Hey,
that bug is probably still in there
It's a really annoying one. I was able to reproduce it once, never again.
Do you have any steps with which it can be reproduced reliably? I would love to fix it...

OK, I just witnessed this bug.
1. Open a scene with a few objects.
2. Import 3 indigo textures, and apply them to the objects,
3 Render with Indigo.
4. Close Indigo, and back in C4D Import a 4th indigo texture and change the texture on one of your objects.
5. Render with Indigo.

Indigo will halt with a message that one of your textures doesn't exist. I think the reason this happens is that the textures are assigned internal names like "Orange_Juice_mid0" and when you import a new texture, it gets named "Orange_Juice_mid1" but the texture assigned to the objects is stlll referring to the original name. The only way out of this bug that I have found is to delete all texture tags, delete all imported textures, and start over. Pretty annoying.

EDIT: you can also get rid of the error by closing and reopening the C4D document.

[fused]

OK, I just witnessed this bug.
1. Open a scene with a few objects.
2. Import 3 indigo textures, and apply them to the objects,
3 Render with Indigo.
4. Close Indigo, and back in C4D Import a 4th indigo texture and change the texture on one of your objects.
5. Render with Indigo.

Indigo will halt with a message that one of your textures doesn't exist. I think the reason this happens is that the textures are assigned internal names like "Orange_Juice_mid0" and when you import a new texture, it gets named "Orange_Juice_mid1" but the texture assigned to the objects is stlll referring to the original name. The only way out of this bug that I have found is to delete all texture tags, delete all imported textures, and start over. Pretty annoying.

EDIT: you can also get rid of the error by closing and reopening the C4D document.

Hey forgeflow,

thanks for the steps to reproduce this bug!

If I can reproduce it with these steps, it will be fixed for the next release

[fused]

Hey forgeflow,

thanks for the steps to reproduce this bug!

If I can reproduce it with these steps, it will be fixed for the next release

Managed to reproduce. Will fix.