CINDIGO 1.0.8
for Indigo 1.0.8 (works with 1.0.9 stable)


(a quick test for low IOR phong with specular_reflectivity_spectrum and Oren Nayar)

download exporter:
PC Version
(or below)

Have a look at my Cindigo Blog! (about cindigo, and one or two other smaller plugins, which will come soon)

The file contains PC versions for R10 and R9. (R10 users will have to rename the "cindigo1.0.8.cdl_R10" to "cindigo1.0.8.cdl")
Make sure you have the newest version of quicktime installed!


Good beginner tutorials can be found here (german and english)

please tell me if you find bugs or have specific requests. i will try to fix/implement as fast as possible.

new in 1.0.8:

* Support for Oren Nayar Mat
* Support for specular_reflectivity_spectrum in Phong Mat
* Render Settings Tag now is an object!


fixed in 1.0.8:

* will not crash if no UVW tag is applied
* maybe some other small things


known bugs/issues 1.0.8:

* Blend material issues with blend maps
* better not use previews


features to come in the future: (for preventing double and tripple requests)

* Better .obj export (still needs optimization)
* Region rendering

Super!

not a single day pasted since the Indigo update and we C4D guys already can play with the new features.... niiiiiiccceeee!!!

Thank you very much, fused!
unfortunately i don't have time at the moment to use c4d and Cindigo

Ciao!!

That was really fast. Thank you !

greetz

Thanks fused, really nice.

Thank you

nothing new here. i should put in more bugs...

REQ: Would it be possible to take the layers name into consideration? Whereas sometimes one might use the same name for different materials they would distinguished by their layer name.

Thank you fused it's great.

I guess that is a new feature in C4D10.5 ? I´m still running 9.1 here, so I´d be happy if "special features" such as the one mentioned aren´t supported. Downwards compatible is the key to success I´m still p.o.éd that Maxon didn´t care about data exchange between 9 and 10 versions

Michael

Well.. it's on 10, it's a bit selfish of you not wanting features because you don't have those, namely because at least this one wouldn't have impact on cindigo UI, just on export process, it's something that if present (and not forgetting there's a 10 compile already) it could acknowledge it. Then perhaps we should not use any of 9 features for the sake of C4d 8 users.

@pixie and micha:

actually i dont like to implement stuff thats not in R9, since having two different versions is pretty complicated.
the changes in the R10 build are minor (two functions i use changed their name in R10).

cant you just use unique names?

if not

maybe i can implement it, ill have a look in the docs and if its easy to find out in wich layer the material actually is... ill do it.

It's just so one doesn't keep materials with the same starting name once and again, having dozens of materials, having layers and not using them or using them as if they did not exist is a bit cumbersome.

Added:
Putting a more though on the matter perhaps layers aren't really needed, just like Cinema can use the same name for materials it might use an akin system for naming the materials, namely when one has to work always with the original and exporting it, the names doesn't really matter as long as they aren't mixed up. This way those who layers could use them without fear, and those who doesn't have that feature available might as take advantage of the fact of having a 'self-aware' material.

Reading pixie´s last post makes my head hurt

At the moment it seems there´s not so much missing in the exporter when it comes to implementing C4D-stuff.

So what´s the next logical step ? What´s missing that Indigo has and C4D doesn´t need to export from a model ?

Michael

P.S.: Dang, I still haven´t figured out how to set up that Indigo cam for 9.1 which was provided by Wlad