Cindigo 2.0.9

[zeitmeister]

Hm, the "GhostGlass.pigm" in the material db is being renamed to *.igm now...
and other *.pigm work well.

Strange... maybe that was a test?

[zeitmeister]

Very, very strange...

if I download this material from the DB here at home, I get "ghostglass.pigm".
C4D/Cindigo isn't able to interprete it on this machine.
If I rename it to "ghostglass.igm", open the file with a text editor, delete all the stuff and paste the source code from the DB, it's working.

Once again: If I download this material at my work, I get "ghostglass.igm". If I download it at home, I get "ghostglass.pigm".

Same browser, same C4D version, same Mac OS version with all same updates, same Cindigo.

????????????

[fused]

If I rename it to "ghostglass.igm", open the file with a text editor, delete all the stuff and paste the source code from the DB, it's working.

hehe, of course its working then.... you made an igm file out of it
its maybe a bug in the matdb that offers a pigm file with the igm extension for download.

now, that you say you're on a mac (i forgot that you are ):

added the mac version.

pigm export, import and linking wont work because the indigo console app doesnt work yet.

[pixie]

Make sure you have the newest version of quicktime installed! Previews will not work with the 64 bit version bacause of the lack of 64 bit quicktime.

Wouldn't it be solved if you wrote jpg instead of png? I don't know if indigo console saves in jpg but I expect it to since the gui already has that option...

[zeitmeister]

pigm export, import and linking wont work because the indigo console app doesnt work yet.

I overread this by luck.
But what has this *.pigm-format got to do with the console? Is it because of converting ASCII to plain text, or decompiling in a certain way or what?

[fused]

indigo can be used to pack/unpack igm/pigm files. i chose to use it because its the easy way. this solution is a little flawed, tho. i have to freeze c4d for a couple of seconds to make sure the file was successfully extracted when importing or linking pigms.

There is another possibility: The C4D api allows to create and unpack zip files (which pigms are), but im not a 100% sure if C4D R9 supports that. will find that out now.

[zeitmeister]

This would be a nice solution.
R9 users will have to solve PIGMs with Indigo itself, all users above could use C4D (if possible)... I think this is a rather handsome workflow.
The actual Version of C4D is 11, so supporting old versions is very nice indeed, but everyone would have to accept that there are compromises to be made when using a version 2 levels below the actual.

[fused]

R9 does not. there is still the possibility to use zlib (which the c4d api of r10+ uses), but meh

i just looked it up and R9.5 supports it. so, i will move from R9 to R9.5. I'd need a R9.5 demo to do that, tho. Anyone has one lying around? (the real demo.... no warez please...)

edit: im not sure if ill use it for packing igms. probably not.

[tungee]

Sorry fused no 9.6 demo here....

[fused]

Wouldn't it be solved if you wrote jpg instead of png? I don't know if indigo console saves in jpg but I expect it to since the gui already has that option...

Hey pixie,

i already requested that a while ago. Not possible, might happen - but not too soon.

[fused]

Hey all...

looks like the last two CIndigo versions are forcing you to use the BVH instead of the KD tree (when you have more than 800 tris for an object). It will be fixed in the next cindigo version. You can fix it by setting the bih_threshold in the render settings (i think advanced settings must be activated) to 100000 (stupid C4D UI wont allow you to set a higher number) or by editing the igs file and change the <bih_threshold> in <render_settings> to a high number (millions ).

This is not that bad and should not render that much slower than KD, but it seems the BVH is broken in the mac version of indigo.