Hmm I think I've found an interesting behaviour in J3D 1.3beta1 which looks like a bug to me. Here a small description:
I've got two objects and 6 textures in my scene. The objects consist of a sphere (using J3D Util class) and a box (using my own generation routine). The sphere is using a CubeEnvironmentMap with 6 textures. The 6 textures are defined as ImageComponent2D and all use a BufferedImage. The sphere mapping coordinates are done with TextureGen (NORMAL_MAP). The texture and the mapping coordinates are put together with a TextureUnitState and set to the Appearance of the sphere. Now the second cube is using one of the same Texture which are used for the CubeEnvironment mapping. The texture coordinates are set explicit for each vertics. Now the interesting thing starts, when the TextureUnitState is activated for the sphere in it's Appearance node the texturemapping for the cube is totaly screwed up. When I deactivate the TextureUnitState for the sphere again, the mapping for the cube is correct! I'm using the OGL implementation of J3D1.3beta1 for Win32. I think this behaviour could be the result of not clearing some GL states. EOF, J.D. -- Realtime Raytracer in JAVA (http://www.antiflash.net/raytrace) =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
