next »

[elijah]

As I was going through the xith-tk examples I found some possible inconsistant code. What is the difference between setTexture and setTextureUnit when  setTexture also create a TextureUnit for the given texture. In the xith-tk example TextureCoord3DTest when I tried to replace the code

        a.setTexture( waypointImage );
       
        with

        TextureUnit tu0 = new TextureUnit( waypointImage );
        a.setTextureUnit( 0, tu0);

The results are totally different. The 3 different texture does not rotate ? Can somebody explain this to me ?

[Marvin Fröhlich]

That's strange. Could you please verify the Appearnce code setTexture()? It should be a convenience method for setTextureUnit() and shouldn't make a difference. Maybe I missed something.

Marvin

[elijah]

I have tried may times and came to the conclusion that they are different. You can try by just simply replacing
        a.setTexture( waypointImage );
       
        with

        TextureUnit tu0 = new TextureUnit( waypointImage );
        a.setTextureUnit( 0, tu0);

and compile the xith-tk. The results are very different. The setTextureUnit calls other function and has additional code but I do not understand the code. But the rule I used is when I want Texture3D I used a.setTexture but for Texture2D I used setTextureUnit.