> We haven't seen this problem. There have been a lot of bug fixes from > Java 3D 1.3 to 1.3.1; you may want to try upgrading to see if the > problem is still there in 1.3.1.
Actually, it is 1.3.1 that I'm using. > Where are you performing the call? Attribute changes won't necessarily be > synchronized with rendering unless they are performed from the Behavior > thread. I tried this. Admittedly I was originally making the calls from the Swing event thread (I have a Jtree that is providing a representation of the Scene Graph - I allow multiple selections in the Jtree, and want to highlight all of the selected shapes in the scene). When I though about it, I changed the code so that the call from the Swing event thread now just puts the selected object references in a queue, which is then processed from a Behaviour's processStimulus method. The problem manifests EXACTLY as before. This is an exceptionally annoying problem, and at the moment I have resorted to only allowing single selections. I am loathe to have to go live with such a lame work-around. I thought about having a switch node to switch between different versions of the shapes, with different materials. This seems ridiculously expensive, though, so I haven't done it. Anything to help would be VERY MUCH appreciated. Thanks, Lewis Walker =========================================================================== 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".
