I created a simple scene is which I have 2 torus shapes. I added a behavior to wake up every so many milliseconds and move the 2 objects around. I get *very* nice motion and frame rate, about 17 to 20 fps.
Then I added a single sphere and a texture mapping for the sphere (the world which is in the demos folder that comes with Java 3D.)
As soon as I add this to my scene my performance goes *way* down. I am only getting a couple of frames per second (5 or 6).
Is this an indication of a graphics card problem? (I have a TNT card, but I don't know what model.)
Could there be a coding problem on my part? Is there a "right" way to do texture mappings and a "wrong" way which is known to impact performance?
If I go out and buy another graphics card, what feature of the card should I make sure is on the card to solve this problem?
I am a little surprised that adding one texture map would cause such a performance hit.
I now recall that I have run other Java 3D programs with texture maps and the performance didn't look too bad on my system. For example, the coneworld demo seems to have good performance and it has several texture maps. So I am not sure what's going on...
I can make the scene more complicated (more objects) and I get real good performance. But as soon as I add the one texture map onto the sphere, performance goes out the window....
Bob Gray
