next »

[Marvin Fröhlich]

I hate the Java3D-inherited Multitexturing API. You have to handle the textures in a completely different way when you want to achieve multi texturing. I would want to change that, so that Appearance.setTexture( Texture ) is simply a shortcut to Appearance.setTexture( 0, Texture ) and the same for the TextureAttributes, etc.
this would make it a whole lot easier to handle and to undertand especially for new users.

What do you think?

Marvin

['n ddrylliog]

I hate the Java3D-inherited Multitexturing API. You have to handle the textures in a completely different way when you want to achieve multi texturing. I would want to change that, so that Appearance.setTexture( Texture ) is simply a shortcut to Appearance.setTexture( 0, Texture ) and the same for the TextureAttributes, etc.
this would make it a whole lot easier to handle and to undertand especially for new users.

What do you think?

I don't see any incentive to stay very Java3D-like, if there is a better, easier design.

+1.

[Mathias 'cylab' Henze]

Go ahead.

Maybe we could also add a

Code:

Appearance.setTexture(int unit, String samplerName, Texture tex)

that calls

Code:

shaderProg.setUniformVar(samplerName, new int[]{unit});

if a shaderProgram is set on the appearance. Furthermore the info have to be stored, if the shaderProgram is assigned or changed later.

This way it would be dead simple to pass textures to a Shader.