Hi,
I am doing a java port of Assimp as you already may know
I am dealing now with the material and so on..
My main concern is the int pNumValues
It seems that all the materialKey use only one value except for AI_MATKEY_UVTRANSFORM
E.g: 3DSConverter.cpp, L216
// Setup texture UV transformations mat.AddProperty<float>(&texture.mOffsetU,5,AI_MATKEY_UVTRANSFORM(type,0));
Is it correct?
Moreover, do you have any suggestion which could be the best structure of AiMaterial and AiMaterialProperty for Java?
I was thinking extending AiMaterialProperty with AiMaterialPropertyString/Int/Float/boolean/Vec3 for each kind of different value
Problem is the enumerators, for example SHADING_MODEL, that can be many..
What do you think?
Log in to post a comment.
Hi,
I am doing a java port of Assimp as you already may know
I am dealing now with the material and so on..
My main concern is the int pNumValues
It seems that all the materialKey use only one value except for AI_MATKEY_UVTRANSFORM
E.g: 3DSConverter.cpp, L216
// Setup texture UV transformations
mat.AddProperty<float>(&texture.mOffsetU,5,AI_MATKEY_UVTRANSFORM(type,0));
Is it correct?
Moreover, do you have any suggestion which could be the best structure of AiMaterial and AiMaterialProperty for Java?
I was thinking extending AiMaterialProperty with AiMaterialPropertyString/Int/Float/boolean/Vec3 for each kind of different value
Problem is the enumerators, for example SHADING_MODEL, that can be many..
What do you think?