Indigo Renderer Forum

Hi guys,
I've updated the spec in the first post.
I've removed the restriction that the IGM must contain a material with the same name as the IGM, and that the PIGM file must contain an IGM file with the same name.

This will make things a little more difficult for plugin writers etc.., but at least people can rename their files now

I've also added a requirement that PIGMs must contain a preview image.

Sounds better, Ono.

I was wondering if PIGM packing is supposed to work with indigo 1.0.5. I just tested it and Indigo created the PIGM file but it had no data in it.

Thanks.

I've only tested IGS packing, I guess IGM packing doesn't work.

hey Big O I think 500x500 is unnecessary for a preview how about 250x250?

removed requirement to have PNG preview render in PIGM archive, as it was a bit of a hassle.

OnoSendai wrote:

dougal2 wrote:I have a question about sharing textured materials....

.. what should be given in the <uv_set> tag ?

Users will need to edit this for their models. This makes the whole sharing of materials a little less trivial than simply including a file and launching the render.

Also, if I were to be providing a web materials generator/database what should I put in there as a default?

Just use "default" as the default

Ono,

You should probably add to this to the official spec. i ran into this issue when trying to <include> an IGM file.

+1 on that!

... with indigo 1.0.5...

Did I miss something?

Ono,

I still don't think the question about nkdata IGMs has ever been officially answered so i wll ask it yet again.

Are custom nkdata files allowed in the official IGM specification? Are we supposed to export nkdata files when we export the IGM?

My feeling is that the answer to both of these questions should be 'no'. Custom nkdata files are probably pretty useless now that we can use specular reflectivity spectrum.

Please, update the spec with your answer to this question. Thanks!

Yeah, I'd like to know the same thing actually.
Would be good to get some kind of a final agreement going on of what should be supported in igm and how.
Maxigo currently exports nk's with the material and expects it from the other igm's too.
Also i think there is a situation where some of the exporter writers (like me and whaat) have some kind of agreement of the whole igm format and others have no clue about it. That creates a kind of a random situation on that "market". Very hard to get the exporters to be compatible that way.
So we really need to mark down the basics of igm format once and for all.
I don't feel like re-doing the thing over and over again anymore.
Thoughts?

Are those specs in the first post of this thread the most current one and valid?

Yes, they're current.
As for custom NK's, well, just avoid them.

What should we export, when nk file is used?
Only the name of the nk? No path? Indigo picks the nk itself from the nk dir? Or how this should work?
In the past we agreed, that nk files are threated like textures.

You want to export the path to the nk data file, relative to the base indigo directory, so some thing like "nkdata/Ag.nk"

Updated IGM spec to include the use of the uv_set 'default',
also to forbid custom nk data files.

Could someone be so kind to explain how to use these material files (Indigo Material Database)? I am using Blender and Blendigo but cannot solve how to use Indigo Material Database.

Thank you very much in advance.

Buba