Indigo 0.7 test 7

[manitwo]

It looks like multible blends + Alphamap, to me...

normal people would use a simple feature called texture

[ludoman]

thks for the reply,

well i can't use texture, as the object is exported from a specific molecular modeling tools.
The object export as vertex and face colored according material definition. The mtl file have several material like :
newmtl ad0000FF
Ka 0.000000 0.000000 1.000000
Kd 0.000000 0.000000 1.000000
Ks 1.000000 1.000000 1.000000

that i call in indigo as :
<material>
<name>ad0000FF</name>
<diffuse>
<colour>0.0 0.0 1.0</colour>
</diffuse>
</material>
When there is only one material things are working well, but if the number exceed 2, there is some mistake in the attribution order. Is the problem comes from the wavefront file or from how indigo understand wavefront obj.
I think there is no blend or alpha_map.

any idea?

[StompinTom]

could be an export problem. i know that Blender sometimes has problems with .obj files (ie. i was exporting a model from FormZ in the .obj format and it got all fucked up when i imported into Blender and the materials were all screwed up)
try exporting as a .3ds file. thats been the safest/most consistent way for me, seems to go over well.

[ludoman]

well yes, but .3ds is a binary format, and i don't know how to produce it..i will try with some converter tools.

thanks anyway

[CTZn]

Conversion between obj and ds is often a pain in the *paf*, due to either format being faultly implemented... in your case StompinTom I guess FormZ was in cause...

[ludoman]

i think u have found the problem, because it is the same, with 3ds or obj file. The problem comes from the number of material. I will make test to identify the maximum number indigo can handle, i know that blender is only 16...perhpase indigo have the same limitation!