Yeah, the R11 is for both platforms, but I don't want to be limited for 42 days at the moment.
So I have to wait until fused can compile Cindigo for the Mac.

C4D11 file type is compatible to the C4D10 file system... so your files created/saved with the C4D11 Demo will be still usable for your C4D10.5 on the Mac...

So you really only win by trying it.... much better than waiting, or even use a very very old cindigo mac build that is also limited to a very very old Indigo build...

Think about it!

Just a small suggestion for the exporter:

Would it make sense if every Material Helper Tag contains a text area, where you can paste hardcode from the material database by hand?
With a checker box at the top/side, wich says that this code overrides all other material settings?

I think this could be very comfortable instead of editing the *.igs-file in a text editor.
This way, all settings would remain where they have to be, in the origin scene.

I personally looked at the ghostglass-material, and because of that this idea came up my mind.

What do you think?


Cheers, David

Just try "PlugIns>Cindigo 1.1.11>Import igm" to import such materials...

Yes, but how do I assign this material to a specific object?
I didn't try it yet …

If you import an igm material you get exact that material as a null tag as if you would have created it by yourself, then just assign then according C4D-mat to your object

btw: igm import reads old style mats only.

edit:
zeitmeister, about your idea:
i thought about this a few times in the past. it brings a few problems, like finding out the material name (or the user has to name the c4d exactly like the mat in the igm).

of course i could do this with the xml parser i use, but then theres the problem of finding the root material (which i actually solved, but only for the igm export, what would mean id have to generalize the function further or write a new one...)

or i put it in and just dont care about people complaining

Hm.
Therefor, my hardcode text box in the material helper tag wouldn't make such little sense, I suppose.

i might put it in see edit.

Yes,
putting in the correct material name might not being automated … but let's be honest: Therefor, it's hardcoded!

i think ill put it in right now. ill also add a question if a material should be imported as a "custom mat" or with the igm parser.

One last thing:
Can you give me a hint which material functions ar being supported by the old mac exporter?
I tried to simulate a wood floor, and therefor I need color maps, bump map and specular/reflection/whatever map. What is being regarded by te old exporter and what not?
I used phong for the material, but the reflections are too sharp, the bumpmap too weak and a specular map doesn't semm to be regarded.
Can you give me a few hints about that?

Thanks very much in advance!

frankly, i have no idea
sorry

xcode is a pain in the ass.

This looks great already!
Is XCode really that complicated? Hope you keep your nerves, and now I'm very excited again for the things that are coming!